Post not yet marked as solved
$ plutil -convert json -o - /Applications/Xcode-beta.app/Contents/Info.plist | jq -r .LSMinimumSystemVersion
14.0
Yep. Apple Dev is deceiving us now. Now my team gotta update over 100 CI macs to Sonoma just to install Xcode 15.3 beta all of the sudden. Great.
Post not yet marked as solved
I filed FB12403764 but they said it is 'Works as currently designed' with "Please know this is behaving correctly. Both Xcode14.1 and 14.2 are matched with the watchOS 20S71 simulator runtime." comment.
For CI maintainers, this is quite an issue because it frequently fails the build with 'watchOS 9.1 simulator not installed' errors.
(See what happened to Bazel CI in https://github.com/bazelbuild/continuous-integration/issues/1431)
Issue related to this behavior has initially been publicized by Xcodereleases of which I was unnoticed. (https://github.com/xcodereleases/xcodereleases.com/issues/32)
So if you still have 20S71 on your CI build machine macs, beware not to delete those, keep it with care for Xcode 14.2 builds.
If the problem related to watchOS 9.1/tvOS 16.1 simulator persists, check xcrun simctl runtime match help to see how xcrun simctl runtime match set works.
For details, check my gist. https://gist.github.com/dokimyj/9a77cca9fb627a0ae51264a1fe329733
Post not yet marked as solved
Actually, you wouldn't need to download dmg files.
Here is the thing you can do via command line while getting away from ginormous dmg file downloads:
Open Terminal.app.
Execute sudo xcode-select --switch /path/to/Xcode-beta.app
Execute xcodebuild -runFirstLaunch.
Execute xcodebuild -downloadAllPlatforms and wait till it shows Downloading visionOS 1.0 Simulator (21N5165g): Done.
If Terminal/Xcode 15 beta requires Full Disk Access or Developer Tools authority, allow it.
If you only need xrOS, fix the command in 3 for xcodebuild -downloadPlatform xrOS. (or any other than xrOS like: iOS, watchOS, tvOS)
If the command gets stuck on Finding content..., stop the command with Ctrl+c and delete xcodebuild cache by sudo rm -rf ~/Library/Caches/com.apple.dt.Xcode.
Post not yet marked as solved
Never mind. I found what happened. Using sudo occurred xcodebuild -downloadAllPlatforms hang problem. Removing sudo from the command solved the problem.
Post not yet marked as solved
https://feedbackassistant.apple.com/feedback/11968889
My comments doesn't seem to be approved after submission. Here's my FBA with crashlogs, sysdiagnose. I filed it a while ago but never revised yet.
Post not yet marked as solved
This bug persists on MacOS Ventura 13.2.1 on mac mini late 2018 Intel i7 6core.
$ /usr/libexec/ApplicationFirewall/socketfilterfw --listapps
ALF: total number of apps = 5
1 : /System/Library/CoreServices/RemoteManagement/ARDAgent.app
( Allow incoming connections )
2 : /opt/exporter_proxy/exporter_proxy
( Block incoming connections )
3 : /opt/node_exporter/node_exporter
( Allow incoming connections )
4 : /opt/script_exporter/script_exporter
( Block incoming connections )
5 : /System/Library/CoreServices/ControlCenter.app
( Allow incoming connections )
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock '/opt/exporter_proxy/exporter_proxy'
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --remove " /opt/exporter_proxy/exporter_proxy"
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock "2 : /opt/exporter_proxy/exporter_proxy"
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock /opt/exporter_proxy/exporter_proxy
The file path you specified does not exist
Post not yet marked as solved
Updates on the problem(Already reported additionally on Feedback Assistant):
xcodebuild: error: Unable to find a destination matching the provided destination specifier:
{ platform:watchOS Simulator, id:DAC71A8E-D8DC-4FC4-B67F-8462296F9F9E }
but Available destinations for the "Swinject-watchOS" scheme: has:
...
{ platform:watchOS Simulator, id:DAC71A8E-D8DC-4FC4-B67F-8462296F9F9E, OS:9.1, name:Apple Watch Series 5 (40mm) }
...
so the solution BibinAlex and many others suggested would be the key... but what CI engineer gotta do is to make builds of users faster and stable.
Hope this puzzling mess cleared up soon.
Post not yet marked as solved
Thanks for the reply.
I tried stopping killing simulator jobs and services before starting the build, but it has got worse:
failed on every build trial (where it fails was doing carthage bootstrap for Swinject-watchOS/tvOS).
18:55:30 $ carthage bootstrap --derived-data path/to/.derived_data --log-path path/to/logs/carthage.log
18:55:31 ▸ *** Checking out Swinject at "2.6.0"
18:55:31 ▸ *** Cloning Swinject
18:55:32 ▸ *** xcodebuild output can be found in path/to/logs/carthage.log
18:55:32 ▸ *** Skipped downloading Swinject binary due to the error:
18:55:32 ▸ "API rate limit exceeded for 211.14.8.247. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"
18:55:44 ▸ *** Building scheme "Swinject-iOS" in Swinject.xcodeproj
18:56:14 ▸ *** Building scheme "Swinject-OSX" in Swinject.xcodeproj
18:56:33 ▸ *** Building scheme "Swinject-tvOS" in Swinject.xcodeproj
18:56:40 ▸ Could not find any available simulators for tvOS
I will report the bug with sysdiagnose (probably sysdiagnose.log only for reporting, right?)
Post not yet marked as solved
I forgot to let you know: the tested machine is Mac Mini Late 2014 with OS X 10.15.2 Catalina (19C57)
