31

I keep getting this error when launching my app on the iOS Simulator:

Couldn't register com.mycompany.MyApp 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.

I've read other reports of this error and it seems there is no obvious fix for it (restarting the iOS Simulator, restarting Xcode etc..)

At this point here's a list of things I've tried:

  • Restarting the Simulator
  • Restarting Xcode
  • Rebooting my machine
  • Deleting my app's Derived Data, and Cleaning
  • Deleting the iOS Simulator App Support directory
  • Reverting to a 2 weeks old version of the app (which was working 2 weeks ago)
  • Deleting the application in the Simulator (by clicking-holding on it and hitting the X button)
  • Upgrading Xcode form 4.1 to 4.2, and running the app both in iOS Simulator 4.3 and 5.0

Nothing worked, I still get the same bootstrap error.. Any (and at this point I really do mean ANY) suggestion would be appreciated.

Edit: Just wanted to add that the app runs fine on a device. I only get this error on the simulator...

Siguza
  • 21,155
  • 6
  • 52
  • 89
jeannicolas
  • 3,139
  • 4
  • 24
  • 25

8 Answers8

13

As the GDB said:

This generally means that another instance of this process was already running or is hung in the debugger

So find out it and kill it. ;)
I restarted the mac, and it run successfully.

Tip: Well, this may be not work sometimes, so I strongly suggest that you press cmd+. to make sure that you do have stopped the simulator (or device). I find that in most cases the simulator (or device) will not stop exactly when it crashes. I rarely met this issue again with pressing the cmd+. every time it crashes or even just normal exit. Hope this will be helpful. :)

Kjuly
  • 34,476
  • 22
  • 104
  • 118
  • 6
    or just reset your iphone if you are deploying the app on the device – xus Nov 04 '11 at 17:35
  • 1
    Ya! I met this situation & reboot it. – Kjuly Nov 05 '11 at 05:28
  • 4
    By the way, to avoid it, just make sure you turned off the simulator(cmd+.), whenever you want to rebuild the code. ;) – Kjuly Nov 05 '11 at 05:32
  • 2
    Restarting the mac is not really a useful solution :P – Javier Soto Nov 08 '11 at 15:07
  • It seems @silvertab had tried it already. But anyway, I solved my issue in this way finally. :D – Kjuly Nov 08 '11 at 16:04
  • 3
    @Sarah keep in mind to use `cmd`+`.` to stop the task first every time ;) – Kjuly Apr 20 '12 at 05:00
  • I've had this quite a few times, the only thing that works for me is restarting my Mac - which is annoying but works everytime. – TheBestBigAl May 14 '12 at 11:34
  • @TheBestBigAl you can try to press `cmd`+`.` to make sure that you do have stopped the simulator. I find that in most cases the simulator will not stop exactly when it crashes. I rarely met this issue again with pressing the `cmd`+`.` every time it crashes or even just normal exit. :) – Kjuly May 14 '12 at 12:31
  • It works well on my simulator but throws the error everytime I run on the device. Restarting mac didnt help! – Dexter May 29 '12 at 20:15
  • Hi @Dexter, please have a look at the edited answer, hope that will be helpful to you. At least I solved this issue by this way. ;) – Kjuly May 30 '12 at 02:57
  • Thanks @Kjuly.. My problem was solved by restarting iPad and restarting xcode. Next time, will try the new solution :) – Dexter May 30 '12 at 13:41
11

I just closed my xcode & restart my device(ipad2) and it works for me :) You can try this :: Couldn't register with the bootstrap Server

Community
  • 1
  • 1
Saiful
  • 1,891
  • 1
  • 15
  • 39
2

Another solution, go to clear the memory of the iphone simulator Simulator > recovery content and setting then run the program again.

Atwood Wong
  • 51
  • 1
  • 2
1

I had to change my bundle identifier finally

No matter you reboot all devices and cleanup all , it gets stuck hard in the debugger..

don't know how to clear it..

R K
  • 81
  • 3
1

As I experienced, device (or simulator) restart does solve the issue, BUT it would be better not to couse it.

Also my experience is that: You can find the place of crash by cousing it. In such time developers usually press "STOP the running scheme" this could cause zombie process stuck in device. BUT if you press "COUNTINUE program execution", debugger will terminate the process, it will not become a zombie.

stom
  • 29
  • 3
1

i just change the identifier and the app can work again.

Chelsea Wang
  • 599
  • 2
  • 5
  • 19
1

I had this error too and I noticed that it works for me if you close the simulator and stop the program and then change your company name.

I don't know why but it works for me.

Kevin Pope
  • 2,964
  • 5
  • 32
  • 47
Simon Nilsson
  • 11
  • 1
0

I opened Activity Monitor and searched for my app name, and found another instance of it listed. I used Activity Monitor to quit that instance, and the problem went away for me.

Belle B. Cooper
  • 375
  • 5
  • 13