views:

7052

answers:

5

Hi

I was testing my app on the simulator when it crashed on clicking a button of a UIAlertView. I stopped debugging there, made some changes to the code and built the app again. Now when I run the application, I get this error in the console

Couldn't register com.myApp.debug with the bootstrap server. Error: unknown error code. This generally means that another instance of this process was already running or is hung in the debugger.Program received signal: “SIGABRT”.

I tried removing the app from the simulator, doing a clean build but I still get this error when I try to run the app.

Can someone please let me know what I should do to be able to run the app on my simulator again.

Thanks.

+3  A: 

Try quitting and restarting the simulator? If "worse comes to worst" you can always try restarting: in my experience this should fix it.

Elliot Kroo
Ended up restarting the system! Still don't know what caused the issue though!
lostInTransit
Had this happen to me yesterday...the Simulator had quit, but there must have been some GUI-less process left hanging because nothing short of a restart helped. (Well, logging out and back in might have...I didn't try it.)
clozach
As comment below says, you can usually see the hung process in Activity Monitor and kill it there.
Max Howell
+3  A: 

I'm having this problem very often recently. What would prevent this from occurring? Logging out and in fixes the problem but.. it's annoying to do so every so often.

EDIT:

I just found the cause. I had a bug in ApplicationWillTerminate method. So when i click stop button on Xcode window, app couldn't properly terminate and started to hang.

check Activity Monitor to see if your app is on the list. force quit if possible.

sang
This fixed it for me! ps aux | grep Simulator
Jason Prado
A: 

...from my end every time I get this-message, it means there is a bug in my code-somewhere. After fixing any issues with my code it disappears.

Argyris
A: 

Qutting & restarting the Simulator seemed to do it on this end.

rondoagogo
A: 

I just had this happen to me: I was getting the error only on my device and the simulator was working fine. I ended up having to reset my device and the error went away.

deoryp