unable to boot the simulator launchd failed to respond

After I updated to Mac OS Catalina I'm no more able to run the simulator. I always get this: "Unable to boot the Simulator - launchd failed to respond".
I'm running

Mac OS 10.15 Catalina

Xcode 10.3


I can't update to Xcode 11 (anyway my collegue installed Xcode 11 and he's getting the same error too)


I already try these:

- Simulator/Hardware/Erase all contents and services... (the result was a black screen on simulator and nothing happened)

- Delete all simulators and download them again

- /private/tmp directory

sudo mkdir /private/tmp 
sudo chmod 1777 /private/tmp


- I tried this

xcrun simctl shutdown all  
xcrun simctl delete $(xcrun simctl list | grep -o '[0-9A-F]\{8\}-[0-9A-F]\{4\}-[0-9A-F]\{4\}-[0-9A-F]\{4\}-[0-9A-F]\{12\}' | xargs)
xcrun simctl delete unavailable


Nothing seems working...

The simulator looks working in the morning, than after few builds it stop working.


Ideas?

Post not yet marked as solved Up vote post of luca.davi Down vote post of luca.davi
47k views
Posted by
luca.davi
Reply
Add a Comment

Replies

A first simple solution may be to reboot the Mac. Just try it.

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

Add new Simulator in Manage Devices then try again.

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

Easiest method without restarting your mac would be to just clear the derived data for your project. Go to Xcode -> Preferences -> Locations -> Derived Data (Click the little arrow) -> Delete the folder for your project.

Posted by
chris@imagin8.co.za
Post not yet marked as solved Up vote reply of chris@imagin8.co.za Down vote reply of chris@imagin8.co.za

  • That solves the issue for me. Thanks :)

    —
    Fontalland

  • This worked

    —
    tungdoxuan

  • This is the way

    —
    ianios

Thanks marcmlynarczyk but this doesn't solve the problem.

Posted by
luca.davi
Up vote reply of luca.davi Down vote reply of luca.davi
Add a Comment

Thanks Chris. This sometimes solves the problem. The problem randomly cames out again..... I'm having a lot of problem after updating to Catalina.. It looks Windows Vista......

Posted by
luca.davi
Up vote reply of luca.davi Down vote reply of luca.davi
Add a Comment

I am facing the same issue and the error detail message I am getting is


Unable to boot the Simulator.Domain: NSPOSIXErrorDomainCode: 60Failure Reason: launchd failed to respond


Tried deleting derived data and also restarting both mac and xcode.


Please help me out if anyone got a solution

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

If that may help, so here had to restart its wifi router…


https://stackoverflow.com/questions/53079949/unable-to-boot-the-simulator-launchd-failed-to-respond-xcode-10-0

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

The company I'm working for has locked some apple service from firewall. I think this is the problem. I don't know which is the service that cause this problem but if you disconnect the Mac from any network everything should work.
I think that Xcode call some apple service for verifing something (or for saving some usage data 👿) and the call to that service go in timeout

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

In my own case i move mine to the trash bin and i try relaunching the simulator and it worked

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

🇬🇧🇺🇸 Remove node_modules with sudo rm -r node_modules and run yarn

🇧🇷🇵🇹 Remova o node_modules com o comando sudo rm -r node_modules e rode o yarn

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

I had the same issue and tried every solution proposed in this article until now. For me it worked to reset all my simulators. I did it with fastlane, which I installed with homebrew. After installation I ran:

fastlane snapshot reset_simulators

The tool deleted all my existing devices and created new ones. It solved the issue for me.

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

Thanks @henry_g, i had the same issue, and fastlane snapshot reset_simulators did the job !

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

  • this one worked for me.

    —
    prgg
Add a Comment

This worked for me: https://www.youtube.com/watch?v=38MIOYZOcHg

Posted by
stefan_kuehn@gmx.net
Post not yet marked as solved Up vote reply of stefan_kuehn@gmx.net Down vote reply of stefan_kuehn@gmx.net

The best and easy way to solve this issue is to open a simulator in the top you will get an option file and then click on the open simulator option and select the device which you want to start your development

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

Fixed by deleting xcode cache

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