Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message “error: Failed to attach process to id ” is displayed, being different each time. Attempting to ‘Stop’ the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the ‘Home’ button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing ‘Product->Attach to process.’
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn’t help. I reinstalled Xcode, didn’t help. I upgraded to 4.4.1 Aug 7, didn’t help. I deleted all trace of Xcode data, running: find / -name ‘[xX]code‘ and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn’t work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I’ve tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single ‘Label’ object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
- xcode-4-4-ios-5-1-simulator-problems
- crash-of-xcode-4-4-for-mac
- failed-to-attach-to-process-id-xcode
- unit-test-target-doesnt-run-on-xcode-4-5
- xcode-4-4-freezing-on-project-close
- simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I’ve spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I’m not going to specify all the build info, just because it’s whatever comes stock on the fresh install of Xcode.
While this isn’t exactly a solution, after today’s OSX 10.8.1 update from Apple, this issue has been resolved. It’s safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.