Xcode 4.2. gets stuck “Attaching to myapp” when running

Question

In xcode 4.2, sometimes when you\'re going to run your ios proj on simulator, the status windows says \"Attaching to myapp\", and just gets stuck there... until you cancel. Now,

Answer 1

Tried all the solutions but none applied to my case. XCode 4.2, OS X 10.6.8 Found that the Info.plist bundle identifier had been accidentally deleted when adding a custom app icon. Adding that back fixed the problem. Anyway that's my fix, hope it helps someone.

Also before figuring out that, found I could start the simulator from another app and then use the app icon on the simulator for the app that would not attach, and start it up that way.

Answer 2

Upgrading to XCode 4.6.2 resolved this issue for me

Answer 3

Even if the app is not attaching after cleaning the project, changing the app name, restart the by resetting the simulator, and if you are using LLDB compiler, it is because the LLDB compiler is not able to connect to the local debug server in order to solve this, take a look at this

Why does the LLDB Debugger constantly fail to attach?

This really solves your problem!

Answer 4

I have noted in Lion that when the iOS sim locks up or hangs the app, that if I go to a shell, and do ps -ef |grep SDK, I will see many, many processes running associated with the simulator.

I tried to kill off these processes but they rapidly respawn and the only solution then is to reboot. Also, in the ps output, you will also see instances of your app running as well.

So the Simulator issue is caused by previously running processes that appear to block the correct running of the latest one. I guess Apple will have a fix for this eventually, as it is quite onerous.

Answer 5

I also tried all solutions in that topic but all failed. But finally it was found out that what was went wrong.

What made this issue occurred is that some settings in Target->Build Settings was got modified by me for including C headers. And after I added all C headers and make it built. This issue occurred.

It might be only works on the situation I described before.

I just created an empty project and check all items in Target->Build Settings between the attaching-stuck app and the empty one. It was found that some items in the attaching-stuck one was different from the empty one.

So I deleted it and make it attached successfully.

Answer 6

Rebooting works for me, too, but this shouldn't be necessary. I'd recommend filing a bug at bugreport.apple.com. You can duplicate the one I created - the more it's duplicated, the more likely Apple is to fix the problem.