[macOS] Xcodes visionOS platform will be removed from macOS-14 images on September 23, 2024

[erik-bershel]

Breaking changes

visionOS platform will not ship with Xcode pre-installed in macOS-14 based images

Target date

September 23, 2024

The motivation for the changes

The macOS-14 images have grown so large that there is insufficient disk space for running tasks. To address this, we need to temporarily remove one of the components that takes up significant space on the disk. This is part of our broader effort to optimise the image for better performance and flexibility, while minimising disruptions. We will re-evaluate our software support policy in order to free up disk space and slim the images down.

Related issue: #10511

Possible impact

If your builds or tests depend on visionOS SDK or simulator runtimes they can be broken.

Platforms affected

• Azure DevOps
• GitHub Actions

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 12
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• Windows Server 2019
• Windows Server 2022

Mitigation ways

• Run next before accessing the visionOS platform tools on macOS-14 based images:

            sudo xcodebuild -runFirstLaunch
            sudo xcrun simctl list
            sudo xcodebuild -downloadPlatform visionOS
            sudo xcodebuild -runFirstLaunch

• Use macOS-13 based images.

[StephenHodgson]

To be frank, I don't think removing a platform is the right move.
There seems to be too many versions of xcode. I can't believe all 6 versions are necessary. (including 2 betas)

44G	/Applications
 11G	/Applications/Xcode_14.3.1.app
 4.9G	/Applications/Xcode_15.4.app
 4.9G	/Applications/Xcode_15.3.app
 4.8G	/Applications/Xcode_15.2.app
 4.5G	/Applications/Xcode_15.1.app
 4.5G	/Applications/Xcode_15.0.1.app
 4.3G	/Applications/Xcode_16_beta_6.app
 4.3G	/Applications/Xcode_16.1_beta.app

The whole point to use the macOS-14 image for us to do expressly make visionOS builds since no other image supports it.

[Alexdelgadodiaz]

To be frank, I don't think removing a platform is the right move. There seems to be too many versions of xcode. I can't believe all 5 versions are necessary. (including 3 betas) The whole point to use the macOS-14 image for us to do expressly make visionOS builds since no other image supports it.

44G	/Applications
 11G	/Applications/Xcode_14.3.1.app
 4.9G	/Applications/Xcode_15.4.app
 4.9G	/Applications/Xcode_15.3.app
 4.8G	/Applications/Xcode_15.2.app
 4.5G	/Applications/Xcode_15.1.app
 4.5G	/Applications/Xcode_15.0.1.app
 4.3G	/Applications/Xcode_16_beta_6.app
 4.3G	/Applications/Xcode_16.1_beta.app

Hi there, I agree with @StephenHodgson, maybe is better solution to remove old xcode versions rather than removing features that might be necessary.

[workingjubilee]

Many people test against the oldest supported major version of Xcode so it doesn't make sense to remove older versions of just XCode just because they're old.

...oldest supported major is the key there.
I don't think we need all of 15.0, 15.1, 15.2, 15.3, and 15.4? That seems a bit much.

[Saadnajmi]

This will break a lot of workflows we depend on. visionOS support is key for our pipeline.

[fbartho]

Architecturally, I’m a bit surprised that there’s not a combinatoric method of expressing the necessary tool-versions in our workflow files.

[StephenHodgson]

Architecturally, I’m a bit surprised that there’s not a combinatoric method of expressing the necessary tool-versions in our workflow files.

Whole heartedly agree. For example setup-node/setup-dotnet:

      - uses: actions/setup-node@v4
        with:
          node-version: 18
      - uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '8.x'

I suspect that it is bc of some restriction on the way the apple sdks need to be downloaded/provisioned or the bandwidth and size of the binaries.

      - uses: actions/setup-xcode@v1
        with:
          version: 15.0.x