Question 411851 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode fails to run a macOS app: NSPOSIXErrorDomain 153

The app was running well few month ago. Suddenly the Xcode Run started to fails. Note, that Build phase is fine, but on the Run phase pop-up window with error appears:

Could not launch “CloudKitCMS”

Runningboard has returned error 5. Please check the system logs for the underlying cause of the error.

I follow the suggestion and open the underlying logs to see the entire error stack (user info removed to save the space):

Could not launch “CloudKitCMS”
Domain: IDELaunchErrorDomain
Code: 20
Recovery Suggestion: Runningboard has returned error 5. Please check the system logs for the underlying cause of the error.
--
Could not launch “CloudKitCMS”
Domain: IDELaunchErrorDomain
Code: 20
Recovery Suggestion: Runningboard has returned error 5. Please check the system logs for the underlying cause of the error.
--
The operation couldn’t be completed. Launch failed.
Domain: RBSRequestErrorDomain
Code: 5
Failure Reason: Launch failed.
--
Launchd job spawn failed
Domain: NSPOSIXErrorDomain
Code: 153
--

I’ve no idea what is RBSRequestErrorDomain code 20 or NSPOSIXErrorDomain code 153 mean.

Some people have similar problem, and recommend to change bundle id, build, then restore it back and build again. This suggestion didn’t work for me.

My Xcode version is 15.3.

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    I noticed that some people with similar problem refer Entitlements (Farquaad, sqpbrooks on dev forums). I inspected the CloudKitCMS.entitlements file and found bunch of irrelevant keys and values there:

    <key>aps-environment</key>
<string>development</string>
<key>com.apple.developer.applesignin</key>
    <array>
        <string></string>
    </array>
<key>com.apple.developer.aps-environment</key>
<string>development</string>

    Those aps- keys are related to Push Notifications, however we don't use them in the project and the certificate is empty. Also, all those capabilities (Sign In with Apple, Push) were disabled in Xcode. Removing those keys resolved the issue.

    The answer for everyone would be: check and update your .entitlements file.


  2. 0

    Just change macOS signing certificate

    sign to run locally
    It works for me

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search