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

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.

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?)

can the settings for Transporter when set in the Xcode remain in any points of source code? If so, where can it be?