This is a bit messed up since macos-15 is not available in Azure DevOps Pipelines. Will they be available in time for this change?

This is a bit messed up since macos-15 is not available in Azure DevOps Pipelines. Will they be available in time for this change?

Can we get a response on this?

Hey @Cheesebaron and @LotskiAndrej!

We are working on adding macOS-15 to ADO, but no ETA or promises are available now. I'll publish info in #10686 once available.

Is there any way to use Xcode 16 currently using macOS-14 ? I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16
Xcode.app
Xcode_14.3.1.app
Xcode_14.3.app
Xcode_15.0.1.app
Xcode_15.0.app
Xcode_15.1.0.app
Xcode_15.1.app
Xcode_15.2.0.app
Xcode_15.2.app
Xcode_15.3.0.app
Xcode_15.3.app
Xcode_15.4.0.app
Xcode_15.4.app
Xcode_16.0.0.app
Xcode_16.0.app
Xcode_16.1.0.app
Xcode_16.1.app
Xcode_16.1_beta_2.app
Xcode_16.app

Is there any way to use Xcode 16 currently using macOS-14 ?

Yes, we have not removed Xcode 16 from macOS-14. It will be done on October 28.

I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16

Recommended task: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/xcode?view=azure-devops

Thanks for the response, but since I'm using MAUI, I cannot add xcWorkspacePath, and ADO crashes if I don't enter anything.
I tried like this also

- task: Bash@3
  displayName: 'Set Xcode Version to 16'
  inputs:
    targetType: 'inline'
    script: |
      sudo xcode-select -s /Applications/Xcode_16.0.app/Contents/Developer

But it cannot locate the file

@mjosipovic-tgr, I am currently using the same command line command you are using with macOS-14 to set it to use Xcode 16 and it works fine.

sudo xcode-select -s /Applications/Xcode_16.app/Contents/Developer

I'm using the classic pipeline editor:

I tried it few times, changed the order of the tasks in yaml, and managed to get it to work, tnx for the responses.

Heads up! ⏰

To provide immediate mitigation, we have decided to roll back the current macos-14 images in production to the previous stable version from October 22. This should take about 24 hours, but may take up to 48 hours for some specific cases that can be worked around with a restart.

@yeftha For this you can check th solution provided by mjosipovic-tgr in #10703 (comment)

@MerSpyro This fix is working fine . Thank you

XCode 16 still does not seem available in the macOS-14 image?
When will this be available again?

ILLINK : warning MT0079: The recommended Xcode version for Microsoft.iOS 18.0.8314 is Xcode 16.0 or later. The current Xcode version (found in /Applications/Xcode_15.4.app/Contents/Developer) is 15.4. [/Users/runner/work/1/s/src/RmoniWeb.Maui/RmoniWeb.Maui.csproj::TargetFramework=net8.0-ios]

@woutermeuwis please switch to Xcode 16 before running your workflow. Issue states that the current Xcode version is set to 15.4, but it does not mean that there is no Xcode 16 at all.
Example action: https://github.com/maxim-lobanov/setup-xcode

👋

For those tracking these changes or encountering issues for the first time, here’s some context and clarification.

As you may know, we recently faced significant challenges where many users began running out of disk space during tests and builds on macOS-based runners. 😞 This issue was triggered by the inclusion of visionOS simulators in the latest Xcode builds. The root cause, however, lies in our policy of providing nearly all supported minor versions of Xcode on each macOS image, leading to steadily increasing disk usage as Apple’s ecosystem grows.

Here’s how we’ve approached resolving the issue so far:

• Immediate action: We temporarily stopped pre-installing visionOS platform tools in Xcode on macOS-14 images.
• Strategic adjustment: We introduced a policy to limit the number of major Xcode versions installed per macOS image, alongside reinstating visionOS tools for supported Xcode versions. This aimed to free up significant disk space. [doc] Update Xcode support policy #10876

However, we’ve discovered that some projects rely on multiple major versions of Xcode simultaneously, making these strict measures overly restrictive. This prompted us to refine our strategy, prioritising functionality alongside disk space optimisation.

Current Strategy 📏

Our updated approach balances reducing installed Xcode versions with maintaining runner usability:

1. macOS-14 images:

• Will include all minor releases of Xcode 15 with the full platform tools suite (as before).
• Will now also include two minor releases of Xcode 16 (excluding visionOS tools). These will follow a “last two” principle, with the oldest replaced by the newest as updates are released. Beta versions will not be included. [macOS] Add Xcode16 back to macOS14 images #10962

2. macOS-15 images:

• Will include all minor releases of Xcode 16 with the full platform tools suite (as before).
• Will also include the latest available release of Xcode 15 with the full platform tools suite. [macOS] Add Xcode 15.4 to macOS-15 #11023

3. Disk Space and Future Adjustments:

• Currently, macOS-14 images have approximately 60 GB of free space. However, this is not a guaranteed figure and may decrease over time.
• When free space approaches 30 GB, we will reassess our policies and toolsets to ensure compliance with our promised minimum of 14 GB of free space.
• macOS-15 images are not currently impacted by this issue. However, with future Xcode updates, policies may need to be revisited. 🤷‍♂️

Recommendations 🦮

• If your workflows depend on visionOS, we recommend switching to macOS-15 images.
• If your tasks require significant disk space, consider preparing the runner by removing unnecessary large components before starting your workflows.