"Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed"

I recently got a new MacBook and I'm trying to get my projects up and running on it. When I run on an iOS 14.2 device, it works fine. But whenever I try 13.7 or lower it won't let me run and this error pops up

Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed

I would like this to work so I can test on older devices on this laptop.

Note: I got the new M1 chip MacBook so if that could be an issue please do let me know.
Post not yet marked as solved Up vote post of sreddy142 Down vote post of sreddy142
11k views
Posted by
sreddy142
Reply
Add a Comment

Replies

Same exact issue and it's killing me. I am using a new Mac Mini with M1 chip. I assume it's the Mac and not Big Sur. It only works with the simulator packaged with Xcode.

Very frustrating


Posted by
MXStudios
Post not yet marked as solved Up vote reply of MXStudios Down vote reply of MXStudios
Add a Comment
Same issue
Posted by
licai
Post not yet marked as solved Up vote reply of licai Down vote reply of licai
Add a Comment
Same here! Did anyone find a workaround?
Posted by
ahzzheng
Post not yet marked as solved Up vote reply of ahzzheng Down vote reply of ahzzheng
Add a Comment
Here's some similar problems:
Posted by
ahzzheng
Post not yet marked as solved Up vote reply of ahzzheng Down vote reply of ahzzheng
Add a Comment
Updating to Big Sur 11.0.1 worked for me!
Posted by
ahzzheng
Post not yet marked as solved Up vote reply of ahzzheng Down vote reply of ahzzheng
Add a Comment
I can confirm that this does work after a system update. I am not sure if it is the update that fixed it or if just a restart was needed.
Posted by
jweigel
Up vote reply of jweigel Down vote reply of jweigel
Add a Comment
I had the same issue after reinstalling Xcode on my MacBook Pro (15-inch, 2018).
I can install apps on actual device iPhone 8...
Posted by
Rice888
Up vote reply of Rice888 Down vote reply of Rice888
Add a Comment
It was solved by executing the following.
Code Block 
sudo chmod 1777 /Volumes/Macintosh\ HD/private/tmp

linkText
Posted by
Rice888
Post not yet marked as solved Up vote reply of Rice888 Down vote reply of Rice888

  • This solved my problem. Thank you!

    —
    markcayofficial

  • This worked for me too, Thank you!

    —
    uenoissei
Add a Comment

This also worked for me. Thank you!

Posted by
iOS_farley
Up vote reply of iOS_farley Down vote reply of iOS_farley
Add a Comment

I am having MacBoo Pro Intel chip, updated my Mac OS Big Sur 11.6.3

Working for me !!

Posted by
mrahib
Post not yet marked as solved Up vote reply of mrahib Down vote reply of mrahib
Add a Comment

I was facing this issue since long time, and finally got the solution by running those two cmds

sudo chown root:admin /tmp; sudo chmod 1777 /tmp

and

sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp
Posted by
mrahib
Post not yet marked as solved Up vote reply of mrahib Down vote reply of mrahib

  • thanks!!

    —
    camilo1014

  • thank you so much - this totally worked here. (MacOS 12.6, Xcode 14.0.1)

    —
    bwet

  • That works. Would be interesting to understand why XCode messed this in the first place.

    —
    juizzi

I have encountered this problem after a fastlane update. Clearing the cache did help!

~/Library/Developer/CoreSimulator/Caches
Posted by
tomkausch
Post not yet marked as solved Up vote reply of tomkausch Down vote reply of tomkausch

  • This works great! Thanks! :)

    —
    anakinx

  • Error started to occur after my computer crashed. Clearing this fixed it for me. Thanks!

    —
    bglazierjr

  • Best answer! Thanks!

    —
    sakuragi1984

Yep, deleted the caches in this folder and it all started working again.

Posted by
benedge
Up vote reply of benedge Down vote reply of benedge
Add a Comment

It's work for me too

Posted by
Dunan
Up vote reply of Dunan Down vote reply of Dunan
Add a Comment

It worked for me too by deleting the cache

Posted by
Gangadharbonda1985
Up vote reply of Gangadharbonda1985 Down vote reply of Gangadharbonda1985
Add a Comment