The request was denied by service delegate (SFBSystemService).

Question

bubblefish OP

Created Jun ’23

Replies 5

Boosts 2

Views 3k

Participants 6

I'm attempting to run my iPhone app on the visionOS simulator, but I'm met with this error:

Domain: FBSOpenApplicationServiceErrorDomain
Code: 1
Failure Reason: The request was denied by service delegate (SFBSystemService).
User Info: {
    BSErrorCodeDescription = RequestDenied;
    DVTErrorCreationDateKey = "2023-06-23 10:16:55 +0000";
    FBSOpenApplicationRequestID = 0xeb18;
    IDERunOperationFailingWorker = IDELaunchiPhoneSimulatorLauncher;
    SimCallingSelector = "launchApplicationWithID:options:pid:error:";
}
--
The request to open "xxxxxxxx" failed.
Domain: FBSOpenApplicationServiceErrorDomain
Code: 1
Failure Reason: The request was denied by service delegate (SFBSystemService).
User Info: {
    BSErrorCodeDescription = RequestDenied;
    FBSOpenApplicationRequestID = 0xeb18;
}
--
The request cannot be completed as the system is locked.
Domain: SFBSurfBoardErrorDomain
Code: 110
User Info: {
    NSDebugDescription = "The request cannot be completed as the system is locked.";
}
--

Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
    "device_model" = "RealityDevice14,1";
    "device_osBuild" = "1.0 (21N5165g)";
    "device_platform" = "com.apple.platform.xrsimulator";
    "dvt_coredevice_version" = "325.3";
    "dvt_mobiledevice_version" = "1643.0.15.100.1";
    "launchSession_schemeCommand" = Run;
    "launchSession_state" = 1;
    "launchSession_targetArch" = arm64;
    "operation_duration_ms" = 6606;
    "operation_errorCode" = 1;
    "operation_errorDomain" = FBSOpenApplicationServiceErrorDomain;
    "operation_errorWorker" = IDELaunchiPhoneSimulatorLauncher;
    "operation_name" = IDERunOperationWorkerGroup;
    "param_consoleMode" = 0;
    "param_debugger_attachToExtensions" = 0;
    "param_debugger_attachToXPC" = 0;
    "param_debugger_type" = 3;
    "param_destination_isProxy" = 0;
    "param_destination_platform" = "com.apple.platform.xrsimulator";
    "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" = 1;
    "param_diag_memoryGraphOnResourceException" = 0;
    "param_diag_queueDebugging_enable" = 0;
    "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_testing_launchedForTesting" = 0;
    "param_testing_suppressSimulatorApp" = 0;
    "param_testing_usingCLI" = 0;
    "sdk_canonicalName" = "iphonesimulator17.0";
    "sdk_osVersion" = "17.0";
    "sdk_variant" = iphonesimulator;
}
--


System Information

macOS Version 13.4 (Build 22F66)
Xcode 15.0 (22181.22) (Build 15A5161b)
Timestamp: 2023-06-23T12:16:55+02:00

Any ideas?

Boost

Answer 1

Graphics and Games Engineer OP

Apple

Jun ’23

I’ve seen this too if you deploy your app before the simulator has finished booting. Can you try deploying your app again once you see the home screen? Normally that has worked for me. If it persists, please file a bug on Feedback Assistant.

0

Answer 2

masayuki77777 OP

Jun ’23

I was also experiencing the same error. In my case, I had specified Multi-Output Device for audio output in the sound settings, which caused visionOS Simulator not to start. When I returned to the default settings, the error was resolved and visionOS Simulator was able to start.

0

Answer 3

redlime9 OP

Jul ’23

I am seeing this same issue as well. I have tried completely reinistall XCode (Version 15 beta 3) and the issue still persists. I am unable to build to simulator at all and continue to see this error each time I try to build: Screenshot 2023-07-06 at 6.13.02 PM.png

And then the app within the simulator crashes and just goes back to the vision OS home screen. I appreciate any and all help!

0

Answer 4

Developer Tools Engineer OP

Apple

Jul ’23

This error indicates that the target device is locked. Please unlock the device and try again.

Are you accidentally locking your sim? If not, how are you getting into a state where the device is locked? Can you please provide instructions? As reported, this seems to be behaving correctly. We're surfacing the error from the system (The request cannot be completed as the system is locked) when we try to launch the app.

If the system is locked, this is behaving correctly. If the system is NOT locked, then that represents an issue that needs to be investigated. If that is the case, please file a bug report at bugreport.apple.com indicating that you're getting this error even though the device is not locked and provide tarballs from the following, created in-state:

xcrun simctcl diagnose sudo sysdiagnose

0

Answer 5

gabriel_valu OP

Jul ’23

Loading an excessive number of 'test apps' in the beta version of Xcode may at times result in the mentioned error. However, this issue is usually temporary and should rectify itself over time. You need not worry excessively about this problem; instead, continue to experiment and learn.

Even if you try deleting the problematic folder, please note that it will persist in your system's memory and will likely reload when you reopen the Xcode 15 beta. Nonetheless, this behavior is typical of the beta version and does not represent a persistent problem. As you continue to use the software, the loading of your content should gradually improve.

0