The Xcode 16.0.0 image has been released and can be selected as follows:
macos:
xcode: 16.0.0
Apple Silicon VM Image Info
Xcode 16.0 Beta 3 Build version 16A5202i is installed at /Applications/Xcode-16.app
The full manifest of installed software can be found here
Is there a problem with the available simulators for 17.5? My workflow for iOS 17 is failing with the following:
xcodebuild: error: Unable to find a device matching the provided destination specifier:
{ platform:iOS Simulator, OS:17.5, name:iPhone 15 }
The requested device could not be found because no available devices matched the request.
Available destinations for the "[redacted]" scheme:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
The available simulators on the link above seems to show two 17.5 SDKs, one with the simulator I want and one with no simulators:
======= Simulators =======
-- iOS 17.5 --
-- iOS 17.5 --
iPhone SE (3rd generation) (55CDB5EC-7452-4B9D-A042-ABA9FAFFD0CF) (Shutdown)
iPhone 15 (1C9A724E-0120-4AAC-A9B8-936D232133B6) (Shutdown)
iPhone 15 Plus (2C24A2C4-F913-443D-801A-3F6AB592CC71) (Shutdown)
iPhone 15 Pro (F5F755C6-9CE9-4A95-8A3A-A724D5896727) (Shutdown)
iPhone 15 Pro Max (48399F9D-6B59-4C87-84D8-C15EA1C1AC34) (Shutdown)
iPad (10th generation) (AAE6080D-19CF-4C94-A538-6D5922B6A12C) (Shutdown)
iPad mini (6th generation) (FD84E3A7-2447-4BFB-B072-DD4485C2802D) (Shutdown)
iPad Air 11-inch (M2) (311F05D8-7CF4-4768-BE46-1F3EB33794C1) (Shutdown)
iPad Air 13-inch (M2) (CAFEFB10-DD81-4C93-B7A8-49D719134F63) (Shutdown)
iPad Pro 11-inch (M4) (CFA35A94-AD79-4C9C-B0BE-43ABF68FA0ED) (Shutdown)
iPad Pro 13-inch (M4) (F09CF782-8645-4F6E-8F30-730E2386EC2B) (Shutdown)
Hi @lukeredpath,
Thanks for pointing out that detail in the manifest!
At first glance it’s not clear how/why Xcode downloaded two different simulator runtimes for iOS 17.5, but it could be breaking device selection with xcodebuild.
As an immediate workaround, you can try xcrun simctl runtime delete 21F79 which will remove the runtime that has no devices. However this command takes some time (30 seconds on a large executor), so I’m going to look into re-releasing the image with a permanent fix for this.
Update: We have identified the issue causing these two runtimes to be present in the image, and are working on fixing and re-release.
It also appears that the runtime which has the devices associated with it is actually the Xcode 17.5 beta 2 runtime, rather than the release version. This means my previously provided workaround to delete the runtime with the ID 21F79 would actually remove the release version.
Until a fixed image is released, a more correct workaround would be to execute xcrun simctl runtime delete 21F5058d and then create a new device using the correct iOS 17.5 runtime, i.e. xcrun simctl create "TestPhone" "iPhone 15" "21F79"
Thanks for the update - I’m not in a rush as I’m just working off the branch and with beta 4 just released I can hopefully wait for the new image to be released.
I have been working on running our jobs with this image and also noticed that simctl and communication from xcodebuild to the simulators are having issues.
The main symptom is that xcodebuild only reports generic runtimes rather than the installed simulators which simctl list lists.
Surprisingly the best workaround I found so far was to use the large resource class and disable simulator preboot.
Relying on xcodebuild to launch the desired simulator seems to work most of the time.
I learned of the new Beta release shortly after my last post yesterday. The simulator runtime fix has been applied to a newly built image with the latest Xcode 16 Beta installed, and we have confirmed that it has the correct simulator runtimes installed.
We’re distributing the new image for release later today 
The Xcode 16 Beta 4 image is now available!
The Xcode 16 Beta 4 image seems to be performing a lot better. I was able to revert to using the medium resource class again.