There are a few different issues that are at play here, so I'll try to untangle it a bit. Firstly to highlight what I send back to all reports of this symptom. This is what you probably saw in email already, but sharing here for everyone else's benefit: This symptom (Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding) occurs when launchd_sim (the principal process that kicks off the simulator) doesn't respond to an initial checkin message within a set time window. It is known to be caused by a variety of issues. Incorrect permissions on system temporary directories: Some users inadvertently change the permissions on system temporary directories, which can lead to this issue as well as problems in other software. If this is the issue, it can be fixed by running sudo chmod 1777 /private/var/tmp /private/tmp. 3rd Party Security Software: Some 3rd party security software can cause significant performance delays loading processes from the simulator runtime disk
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: