Hello here ! I’m encountering a bug when launching an app on the simulator which is: The request was denied by service delegate (SBMainWorkspace). I know that there are some topic about this error, but any solution works for me. 
This is what I have already try: Clean Derived data + project Reset simulator Check empty environment variables (for all target + pod) Update Xcode Reinstall Xcode Restart the Mac (multiple time) Check for Mach-O Type build settings is set to executable Try on different simulators (iPhone 15, 15 Pro & 15 Plus) Try on different iOS versions (16, 17 & 17.0.1) Desintegrate + reinstall pod Kill simulators, restart Xcode Clear Xcode cache from storage settings Try on different Xcode versions (15, 15.0.1, 14.3.1) Many of the things mentioned above at the same time Note that this bug only occurs on one specific project. I can run any other project on simulator normally. The same project run also normally on other Mac. Here’s my configuration: Xcode 15.0.1 (15A507) MacOS Sonoma 14.0 (23A344) Here’s the full error log: Simulator device returned an error for the requested operation. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x9ca3; IDERunOperationFailingWorker = IDELaunchiPhoneSimulatorLauncher; SimCallingSelector = "launchApplicationWithID:options:pid:error:"; } -- The request to open "com.abc.xyz" failed. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x9ca3; } -- The operation couldn’t be completed. The process failed to launch. Domain: FBProcessExit Code: 64 Failure Reason: The process failed to launch. User Info: { BSErrorCodeDescription = "launch-failed"; } -- The operation couldn’t be completed. Launch failed. Domain: RBSRequestErrorDomain Code: 5 Failure Reason: Launch failed. -- Launchd job spawn failed Domain: NSPOSIXErrorDomain Code: 111 -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_model" = "iPhone16,1"; "device_osBuild" = "17.0.1 (21A342)"; "device_platform" = "com.apple.platform.iphonesimulator"; "dvt_coredevice_version" = "348.1"; "dvt_mobiledevice_version" = "1643.2.4"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 11035; "operation_errorCode" = 1; "operation_errorDomain" = FBSOpenApplicationServiceErrorDomain; "operation_errorWorker" = IDELaunchiPhoneSimulatorLauncher; "operation_name" = IDERunOperationWorkerGroup; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphonesimulator"; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 0; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 0; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphonesimulator17.0"; "sdk_osVersion" = "17.0"; "sdk_variant" = iphonesimulator; } -- I have a different error when running on iOS 16: Application launch for 'com.abc.xyz' did not return a process handle nor launch error. Domain: NSPOSIXErrorDomain Code: 3 Failure Reason: No such process Thanks in advance !

I am running the most up to date version of Xcode (v10.1 (10B61)) on a High Sierra system (10.13.6 (17G10021)) and find that compiling for macOS will work, but not visually display in the sumulator. I get the LLDB message: "unable to attach". Advice online suggested submitting new security certificates, which I have done, but still the simulator will not show up, even though the code compiles.

Hello Apple Developer Community, I'm encountering a crash issue while running my iOS application in the iOS Simulator. The crash is accompanied by the following error message: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$sSo24OS_dispatch_queue_serialC8DispatchE10AttributesVMa Referenced from: /Users/USER/Library/Developer/CoreSimulator/Devices/635DF164-98FC-48BB-81FD-BDAF562695EB/data/Containers/Bundle/Application/93882CE2-9B8E-4665-BCF2-5B4E0E557734/myapp.app/myapp Expected in: /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftDispatch.dylib (terminated at launch; ignore backtrace) I'm currently using Xcode 15.0.1 and running the application on the iOS Simulator version 15.5.

Every time when I open the simulator and SwiftUI preview I get an error. How to solve this?

Running Xcode 15.0.1 on Sonoma 14.1. I would like to run my app in an iPhone 14* simulator running iOS 16.* to verify something has changed between 16.* and 17.*. I clicked on the Run Destination dropdown and clicked manage run destinations to open that dialogue. I then added the + on the simulators tab to add a new Simulator, clicked on the OS version, and clicked on the download more simulators to open the platforms tab in Xcode settings. Clicked the plus sign there and downloaded iOS 16.4 Now back in the run destinations dialogue I have all the iPhone 14 models with iOS 16.4 available. However, Back in the main Xcode windows when I click on the Run Destinations dropdown I still only see iPhone 15 models. I checked my target minimum deployments setting and made sure it was at iOS 16.4. I've cleaned and rebuilt my app, deleted the app out of the derived data folder and rebuilt. Restarted Xcode. I'm sure I'm missing something, but I'm not really sure what it is at this point. Any thoughts?

Hi, after upgrading to new SDKs I can no longer run the app on the simulator. I insert the debugger result here. Showing Recent Issues Cycle inside Runner; building could produce unreliable results. Cycle details: → Target 'Runner': ExtractAppIntentsMetadata ○ Target 'Runner' has copy command from '/Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex' to '/Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex' ○ That command depends on command in Target 'Runner': script phase “Thin Binary” ○ Target 'Runner' has process command with output '/Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/Info.plist' ○ Target 'Runner' has copy command from '/Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex' to '/Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex' Raw dependency cycle trace: target: -> node: <all> -> command: <all> -> node: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Objects-normal/arm64/ExtractedAppShortcutsMetadata.stringsdata -> command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ExtractAppIntentsMetadata -> node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks> -> command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks -> node: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/InputFileList-1EF15891FDC30E5AB246A27A-Pods-Runner-frameworks-Debug-input-files-f84ae2d16402feb0918249beabe0354e-resolved.xcfilelist -> command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:WriteAuxiliaryFile /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/InputFileList-1EF15891FDC30E5AB246A27A-Pods-Runner-frameworks-Debug-input-files-f84ae2d16402feb0918249beabe0354e-resolved.xcfilelist -> node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-copy-files> -> command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-copy-files -> node: <Copy /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex> -> CYCLE POINT -> command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex -> node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase3-thin-binary> -> command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase3-thin-binary -> node: <execute-shell-script-18c1723432283e0cc55f10a6dcfd9e02f1eee2015e8ff5ebcd27678f788c2826-target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-> -> command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:PhaseScriptExecution Thin Binary /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Script-3B06AD1E1E4923F5004D2608.sh -> node: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/Info.plist/ -> directoryTreeSignature: � -> directoryContents: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/Info.plist -> node: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/Info.plist -> command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ProcessInfoPlistFile /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/Info.plist /Users/MACPC/Desktop/MYAPP/ios/Runner/Info.plist -> node: /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex -> command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/Runner.app/PlugIns/OneSignalNotificationServiceExtension.appex /Users/MACPC/Library/Developer/Xcode/DerivedData/Runner-fjykmfstetqpxeegotevlnbgnqtk/Build/Products/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex I cannot understand what's the problem. Thank you all.

After Xcode 15 update, to update my older iOS apps, Xcode says I must install the iOS 17.0 something. When I choose to install, the iOS 17.0.1 Simulator (21A342) downloads completely (~7gb) but even after 10-15 minutes the dialog Verifying "iOS 17.0.simruntime"... never progresses even once. I am unable to do anything with Xcode Because of this I am unable to build my updated iOS apps because it keeps cycles in this same loop with the same results, now 2 or 3 times. Does this verify take hours? How can I get this to verify and get back to updating/building my iOS apps?

Using iOS 17 I notice when I compose an MSMessage and insert it into the active conversation and send it in the simulator the message does not appear in the the message thread. The didStartSending(_ message: MSMessage, conversation: MSConversation) function is called when the message is sent, but there are no errors. I'm expecting there is an error with iOS 17 Simulator and sending messages. Also, being able to debug sending a message and going to the receiver to open the message still crashes. I hope this gets solved as well as it makes it very hard to test iMessage apps.

I'm using Xcode 15.0 (15A240d) and I need to test some code on iOS 15. I'm unable to create a new iOS 15 simulator. If I select the "Download more" option I'm presented with the "Platforms" tab in settings. There's no option to actually select a platform here (which as you can see Xcode itself indicates I have on disk). Neither double-click nor secondary-click do anything for me either. Am I doing something wrong or is this just bad design?

I'm running the latest Xcode 15.0.1 installed manually (not from App Store). Tried installing the iOS 17.0 runtime directly from Xcode. It usually gets corrupted mid installation, or when it finally installs, the simulators are still not available. Afterwards I tried installing simulators directly through .img files, it worked in the past, but now it tells me there are duplicates. I've tried reinstalling Xcode with deleting all of it's caches, but I still have this problem.

I may have found a bug within Xcode 15.0.1. I am working with CoreLocation in order to access a user's location. I have all the code working and the permissions needed within the info.plist. Below is a checklist of everything that I have. Info.plist I don't need to but I added all 3 keys into my project's info.plist to explain the reason why I need access to the user's location: NSLocationAlwaysAndWhenInUseUsageDescription NSLocationWhenInUseUsageDescription NSLocationAlwaysUsageDescription This was just to cover all basis. Requesting Permission After doing that I have a simple class that requests access to the users location. @Observable class LocationPermissionManager: NSObject { private let manager = CLLocationManager() override init() { super.init() manager.delegate = self } func requestAuthorisation() { manager.requestWhenInUseAuthorization() } } Nothing too wild just a simple class to ask for authorisation permission. When I create an instance of this class and call the function to request authorisation. I get the system dialogue to ask for permission and I'm able to select an option. The Problem The issue starts to happen after. When I go to the settings on the simulator the app doesn't show up or appear. But if I go to the settings on my actual iPhone the app does show up and appear and i'm able to change the different permissions you want to give the app. Requesting Permission Something weird I did find is a work around to make your app appear in the settings. And it involves you requesting permission for another API i.e ATT (App Tracking Transparency) this does work and you're able to see your app appear in the settings on the simulator and you'll see both the ATT & Location permission options as well. It's worth nothing that I'm using SwiftUI for this and this possible bug might be a big one since if someone doesn't have a physical iPhone they're not able to change the permissions for their location on the simulator. Could someone in Apple please investigate this issue?

I can use the option key to bring up the two dots and I can add the shift key to move around the dots, but when I untouch the shift key, one dot moves across the map instead of the dots staying together. Is this even a feature that should work on the visionOS simulator?

I am trying to implement Hand Tracking in a visionOS application I am developing. Initially, I encountered errors such as "Cannot find type 'ARAnchor' in scope." Upon investigation, I realized the error arose because "import ARKit" is required, which was already in the code. Digging a bit deeper, I discovered that ARKit is not compatible with the simulator, or at least that's what I believe. My ultimate understanding is: "ARKit requires the specific hardware of an actual iOS device to operate, as it relies on features like the device's camera and motion sensors." Having reached this point, I noticed in the "HappyBeam" application documentation for visionOS there was a function "#if !targetEnvironment(simulator)". Upon researching, it turns out that this compilation conditional is used so that the application can compile in the simulator (without ARKit functionality) and on a real device. After applying "#if !targetEnvironment(simulator)" it allowed me to compile, but now when I run the application in Simulator, I receive a message on the main window stating: "AR not supported in Simulator." My current question is: Can I simulate Hand Tracking in any way without using ARKit, or is it essential to run the application on a physical device? And if Hand Tracking can be simulated in "Simulator", how is it done? I haven't been able to find a way to do it.

Setting up my MacBook Pro 2018 has been quite a struggle. When I attempted to install Xcode, it prompted an update from Ventura to Sonoma, a process that turned out to be painstakingly slow. What's worse, if the download failed due to a poor network, there was no retry option, necessitating a complete reinstallation. After investing time and money to update my Mac, I finally managed to install Xcode. However, the next step was to download iOS 17 simulators. Unfortunately, the download failed at the 7GB mark, and to my dismay, there was no option to retry. This endeavor has been financially taxing due to the expenses on data. To compound matters, upon further attempts, I discovered that the simulator app I managed to download isn't functioning properly. It's disheartening to have devoted so much time and resources to this, only to encounter roadblocks at every turn. Any advice or assistance to resolve these issues would be immensely appreciated.

I ran into issues submitting to the appstore related to the AppStore requirement to have screenshots for 5.5" screen size. As stated, the dimensions required are: 1242 x 2208 pixels (portrait): I tried the iPhone 8+ simulator on my machine, with iOS 17. The output dimensions taking a screenshot are: 1125 × 2436. Therefore the appstore does not accept it. And they are the incorrect aspect ratio to edit also. I had some testing done and it seems that iOS16 is fine and meets the requirement. Also did try choosing one of the other phone models, 7+, 6s+, but I cannot even create a simulator, as they do not accept iOS17. See video: Please advise

When testing the simulator for CarPlay the screen remains black. It was working fine now the screen remains black even after restarting my computer. I have an M1 MacBook Air with Xcode 15.0.1.

As per the title, as soon as I try to open iCloud settings on the Simulator, a black screen appears and the Preferences app crashes (and a crash report shows up shortly thereafter). This is an issue in all of Xcode 17.0.0, XCode 17.0.1 and the Xcode 17.1 beta. I've tried all the simulator models from the SE to the 15. I think this may be something to do with the following two pop-ups that keep showing up on the Simulator but don't actually do anything when tapped: one says to accept new iCloud T&Cs. When I tap on it, nothing happens (and I can't find new T&Cs to accept in the web browser); and one that prompts me to re-enter the Apple ID password. When I input the password and confirm, nothing happens. This is causing major issues for testing a couple of my apps because Simulator sometimes radomly thinks that the user isn't signed into iCloud when they, in fact, are. For example, I've been getting the following error from GameKit: 'The requested operation could not be completed because you are not signed in to iCloud..' (the same function that throws the error does confim that the user is signed in just before throwing). I'd be very grateful for any thoughts. Been stuck on this for well over a week now...I've found various threads about the wider Preferences app crashing (and this being fixed in the latest beta) but nothing on the specific issue I'm having.

Problem: iOS 16.4 runtime targets are not available for selection, however the 16.4 simulator shows as installed under "Manage run destinations" Config: Xcode 15.0, Sonoma 14.0, M1 Mac-Mini Background: I write and maintain apps for my business unit. A co-worker dropped a phone on my desk and said 'The app doesn't work anymore, can you fix it'. Well, it turns out the phone is running iOS 16.6. The OS had been upgraded. This sent me down the path of upgrading Xcode on a development Mac, which also forced a MacOs upgrade on me. The end result is I now have XCode 15 on Sonoma, but have an iOS 16.6 device that I'm trying to target. Since I don't have any iOS 17 devices I didn't install the 17.0 runtime. To install the "16.6 runtime" I went to: "Xcode - Settings - Platforms" and hit the + in the lower left and under "Previously released simulators" I selected iOS. I selected iOS 16.4 as it was the closest I could see to 16.6 so I'm assuming it still works with 16.6. It took a few attempts to download correctly, but it now shows up in my platforms as "iOS 16.4 Simulator 6.18 GB on disk". If I select "Product - Destination - Manage Run Destinations" I can see simulators for 10 different iOS devices (from iPad 10th gen to iPhone SE) all running iOS 16.4. Great! I must be ready to develop and test for 16.6. Right? Nope. In the dropdown beside my App name the only option that is shown to me is "iOS 17" and the "Get" button beside it. I was expecting to my iOS 16.4 simulators as available target destinations, but there's nothing other than "iOS 17 - Get". This is an old App that I'm maintaining so its deployment target is not new. Selecting a different iOS Deployment target doesn't have an effect. I tried going into Manage Run Destinations and selected my iPhone 14 simulator on iOS 16.4 as "show run destination always". - no change Older iOS version do not show as destinations. Anyone else encounter this? Did you figure it out? Help? Thx

Previously I was able to change the sound output for the simulator from "I/O > Audio Output" and then select a different output device. After updating to the iOS 17, although it's showing that I've selected a different device for sound output, sound is always coming from the device that was selected as default in the system (from global system settings Sound option).

Simulator device returned an error for the requested operation. Appex bundle at /Users/macosventura/Library/Developer/CoreSimulator/Devices/92380DFA-6A40-46D9-BB59-AC5454F68E34/data/Library/Caches/com.apple.mobile.installd.staging/temp.Ku4bKV/extracted/TestFlight.app/PlugIns/TestFlightServiceExtension.appex with id com.apple.TestFlight.ServiceExtension specifies a value (com.apple.appstored-services.testflight) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point.