Xcode 4.4 in iOS 5.1 build successfully exits, but starts freezing on the simulator with the debug message "Could not connect to the process id <pid>"
Symptoms: launching any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator, but will result in a simple black screen. In the Xcode console, the message "error: Failed to attach process to id" is displayed, each time different. Trying to "Stop" the application from Xcode does nothing, and only Force Quit will return Xcode to working condition. Pressing the Home button on the simulator indicates that the application has been successfully installed. Sometimes when you open the application from the simulator, the user interface is displayed, but console messages are not displayed even after manual execution of "Product-> Attach to process."
Attempted solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started with the installation of Xcode 4.4 in early August for a project that worked previously. I got to Mountain Lion, did not help. I reinstalled Xcode, did not help. I upgraded to 4.4.1 on August 7, did not help. I deleted the entire Xcode data trace by doing: find / -name '[xX] code' and deleting all the super folders where it seemed relevant. This (not surprisingly) caused some problems with the OS, since subsequently reinstalling Xcode just didn't work. Then I did it again, reinstalled Mountain Lion (to recover some OS files that I probably killed), and then reinstalled Xcode 4.4.1.
For projects, I usually started new projects with one view each time. Recently, I tried to use this sample project from Apple at link 3 below. I tried all clean builds, etc., but honestly, it can be assumed that opening a new project should just work. Just for the strokes, I put one Shortcut object in the iPhone storyboard from time to time.
After completing some homework, I managed to find the following questions, most similar to mine, but none of them is accurate and none 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 probably spent 15 hours trying to find / implement solutions to a seemingly trivial problem, and I would rather provide all the relevant information than suggest what I did. I will not provide all the build information, simply because that’s all that comes with the new Xcode installation.
I had a similar problem (albeit with a different configuration), and I found an incredibly simple solution by accident. I just used Product-> Stop, then Product-> Run (using keyboard shortcuts, if that matters). Only time! Then the problem disappeared.
: Xcode 4.2, iPhone Simulator 5.0 symptom difference: the installation process do not miss
It seems to me that the problem is related to the communication of Xcode-Simulator, and therefore I shared my experience here, despite the differences.
EDIT. Run did not provide me with a permanent solution. From time to time a problem occurs. However, this is a temporary solution for me.
I got this several times, especially when I continued to run my application and canceled it or interrupted it too often, this is not something you can rely on, but yes, I always managed to get back and start by deleting the application in the simulator, cleaning up the project and building folders, deleting the received data (in the view of the Xcode organizer), restarting the simulator and Xcode.
This also happened several times on the device, and I needed to restart the device, iPhone in my case. I hope this information helps you.
I got this to work by creating and running a simulator using the Xcode 4.5 Developer Preview. Then I closed it and opened Xcode 4.4.1 again, and it was built and worked fine.
Although none of the above solutions worked for me, thank you for putting it all together. I decided that I would answer here, as it was the most complete.
I think I hacked it for my specific case, and I admit that this is a mistake that only beginners should make, but I redefined
viewWillApear:(bool)animated {} in my ViewController without calling back [super viewWillApear:animated]It might be a good idea to search all the life cycles of a view in your project and see if you have a similar problem.