372

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.

What should I do to be able to run the app on my simulator again?

Cœur
  • 37,241
  • 25
  • 195
  • 267
lostInTransit
  • 70,519
  • 61
  • 198
  • 274
  • 2
    Any suggestions about what to do when this happens while testing on the device? I've tried restarting the device, Xcode. – iPadDeveloper2011 Mar 06 '11 at 23:36
  • 1
    I also tried deleting the app on the device, quitting all active apps (double click home, hold finger down on app icon, touch '-' sign) restarting Xcode, logging out and in again. Nothing works so far. – iPadDeveloper2011 Mar 06 '11 at 23:50
  • Try "Empty cache" in the XCode menu. That helps as well. – lostInTransit Mar 07 '11 at 08:14
  • what is the process in activity monitor? –  Jul 14 '11 at 07:57
  • 3
    For everyone facing this issue, later figured out, this happens most of the times due to a bug in the code. Look for some piece of code that either takes a lot of execution time or takes the app into a loop. – lostInTransit Aug 22 '11 at 06:45
  • 4
    When that happens I just kill the SimulatorBridge and quit the simulator. `ps ax | grep SimulatorBridge` – Elland Feb 15 '12 at 05:39

31 Answers31

244

status: this has been seen as recently as Mac OS 10.8 and Xcode 4.4.

tl;dr: This can occur in two contexts: when running on the device and when running on the simulator. When running on the device, disconnecting and reconnecting the device seems to fix things.

Mike Ash suggested

launchctl list|grep UIKitApplication|awk '{print $3}'|xargs launchctl remove

This doesn't work all the time. In fact, it's never worked for me but it clearly works in some cases. Just don't know which cases. So it's worth trying.

Otherwise, the only known way to fix this is to restart the user launchd. Rebooting will do that but there is a less drastic/faster way. You'll need to create another admin user, but you only have to do that once. When things wedge, log out as yourself, log in as that user, and kill the launchd that belongs to your main user, e.g.,

sudo kill -9 `ps aux | egrep 'user_id .*[0-9] /sbin/launchd' | awk '{print $2}'`

substituting your main user name for user_id. Logging in again as your normal user gets you back to a sane state. Kinda painful, but less so than a full reboot.

details:

This has started happening more often with Lion/Xcode 4.2. (Personally, I never saw it before that combination.)

The bug seems to be in launchd, which inherits the app process as a child when the debugger stops debugging it without killing it. This is usually signaled by the app becoming a zombie, having a process status of Z in ps.

The core issue appears to be in the bootstrap name server which is implemented in launchd. This (to the extent I understand it) maps app ids to mach ports. When the bug is triggered, the app dies but doesn't get cleaned out of the bootstrap server's name server map and as result, the bootstrap server refuses to allow another instance of the app to be registered under the same name.

It was hoped (see the comments) that forcing launchd to wait() for the zombie would fix things but it doesn't. It's not the zombie status that's the core problem (which is why some zombies are benign) but the bootstrap name server and there's no known way to clear this short of killing launchd.

It looks like the bug is triggered by something bad between Xcode, gdb, and the user launchd. I just repeated the wedge by running an app in the iphone simulator, having it stopped within gdb, and then doing a build and run to the ipad simulator. It seems to be sensitive to switching simulators (iOS 4.3/iOS 5, iPad/iPhone). It doesn't happen all the time but fairly frequently when I'm switching simulators a lot.

Killing launchd while you're logged in will screw up your session. Logging out and logging back in doesn't kill the user launchd; OS X keeps the existing process around. A reboot will fix things, but that's painful. The instructions above are faster.

I've submitted a bug to Apple, FWIW. rdar://10330930

smparkes
  • 13,807
  • 4
  • 36
  • 61
  • 2
    Thanks for the thorough explanation of the new Lion/XCode4.2 behavior. It seems to happen more often when debugging two separate apps. – samkass Oct 23 '11 at 04:17
  • 2
    It's not just Lion. Still using Snow Leopard here and see this error lots of times since going XCode 4.2. (Used to use XCode 3.x until iOS SDK 5.0 was released.) – Jonny Oct 24 '11 at 16:40
  • 3
    Thanks for the info... This is happening insanely frequently for me recently... Twice in the last 10 minutes. Kinda hard to get a solid workflow going when I have to constantly restart. Well, off to restart my computer again. – Brad G Dec 06 '11 at 13:59
  • In theory, it should be possible to attach via GDB (`gdb /sbin/launchd `) and force a call to wait() (`p (int)wait((int*)0)`, assuming pid_t is the same as an int). Note that you probably want to be logged in as another user when doing this so your session doesn't wedge (oops!). – tc. Dec 22 '11 at 17:33
  • Interesting idea. Worth a try. Doesn't sound like you have? – smparkes Dec 22 '11 at 21:19
  • @smparkes: I attached and then attempted to spawn a terminal to do `man 2 wait` which deadlocked, hence the recommendation to do it as another user. – tc. Feb 13 '12 at 19:33
  • @tc: not clear to me why this should wedge or deadlock. Don't think stopping the user launchd temporarily should bollocks things up. In any case, we probably don't want to do a blocking `wait`. Maybe `waitpid(-1, (void*)0, 1)`? In which case since we should know the PID of the zombie, it could be put in place of -1. – smparkes Feb 14 '12 at 01:09
  • @smparkes: Stopping launchd seems fine until you do something that needs it; creating a new terminal window seems to be one of them. – tc. Feb 15 '12 at 13:21
  • @tc: right: I assumed you'd run `gdb`, `wait`, and then exit `gdb`. You could also just `continue` or `detach` from within `gdb` if you wanted to keep it around in case it happened again. – smparkes Feb 15 '12 at 16:12
  • @smparkes: Merely attaching with e.g. `gdb launchd 140` causes Terminal to hang after about 16 seconds (fortunately, this is recoverable by killing Terminal which causes gdb to die); the workaround is e.g. `echo 'call (int)waitpid(1945,(void*)0,1)' | gdb launchd 140`, but I'm not sure if this actually fixes the "bootstrap server" problem since I'm not experiencing it (I currently have two zombies with parent=launchd that don't stop simulator builds from running). – tc. Feb 16 '12 at 19:48
  • @tc I was wondering if there were away to just run one command from gdb. I tried various forms of attaching that seemed to completely lock things up, even before it got to accepting commands, even when I was sshing in (as the same user). I'll give that version a shot when/if it happens again. I've installed Xcode 4.3 so I'm going to be on the watch for whether it still happens. (Not sure whether any fix would be to Xcode or launchd ...) – smparkes Feb 16 '12 at 19:57
  • @MikeA: thanks (though, ugh). I did suspect that it was more likely to be an OS thing than an Xcode thing. Hopefully we'll be able to confirm tc's latest echo/gdb suggestion which would be pretty painless. – smparkes Feb 17 '12 at 17:21
  • 1
    @smparkes: It actually seems to happen more frequently than before. I just change the bundleID and everything works again, but it's annoying when working with CoreData logic you're trying to debug. Less annoying than rebooting though, I'll admit. – Mike A Feb 18 '12 at 21:43
  • @smparkes: It seems more likely to be a bug in launchd (processes are supposed to clean up their children's zombies, since there's nothing else that can). The weird thing is that I haven't seen the bug recently despite plenty of zombie processes hanging around (two today!). It's also unclear whether it's due to the zombie process, or just something that seems related and is fixed by killing the user launchd (is launchd the bootstrap server?). – tc. Feb 20 '12 at 20:11
  • @tc: It may be interacting bugs. When running normally, the app seems to descend from Xcode. Abnormally, it's been inherited by launchd. It could be something causing gdb do die without reaping/killing the child and then launchd not waiting for it (which could explain Apple not seeing it, if it doesn't happen with lldb). I've observed the bengin zombies, too (which is why the next answer isn't very useful.) Why some zombies are benign and some are malignant, I can't tell. I don't understand the parts of launchd that go beyond init. – smparkes Feb 20 '12 at 21:59
  • Horrible. Happends to me all the time. Filled a bug report too. Thanks for your analysis though. – Henrik P. Hessel Feb 20 '12 at 22:02
  • Super annoying, but so glad this community exists to show me I'm not crazy. – Dan K. Feb 21 '12 at 06:32
  • @tc: confirmed that `wait` doesn't fix things. Updated my answer with a little more research, though the end result is the same. – smparkes Feb 21 '12 at 17:41
  • Just happened again, symptoms: `launchctl bslist` shows e.g. `D com.example.MyApp`, `launchctl list` shows e.g. `25247 - UIKitApplication:com.example.MyApp[0x957c]` though 25247 is an exited process, and `launchctl list UIKitApplication:com.example.MyApp[0x957c]` says `launchctl list returned unknown response`; log lines include `Bug: launchd_core_logic.c:3760 (25247):0` (and `(25247):9`) but those can appear without the wedge. I gave up and updated to 10.7.3; next I'll try spawning processes until I get one with the correct PID and prodding launchd, and failing that, `kill -KILL -1`. – tc. Feb 22 '12 at 17:41
  • Update: Neither of those fix things. The easiest workaround is perhaps to disable the simulators for other OS versions for now... – tc. Feb 22 '12 at 19:08
  • @smparkes can you post your original bug report on http://openradar.appspot.com/? – fearmint Mar 01 '12 at 20:21
  • @JoePasq Sure. I updated it recently with the most recent info (bootstrap name server, not zombies). I also include a link to this SO page. – smparkes Mar 01 '12 at 23:52
  • 2
    4.3.1 and it happened just now ... soooo annoying. For me, restarting the iPhone itself normally solves it, I do not need to restart my Mac. Its tarted happening with XCode 4.2 under Snow Leopard, sometime around September 2011 for me. – TheEye Mar 13 '12 at 14:54
  • Correction: It didn't happen with the Simulator yet, but with my iPhone (5.1) it occurs every 6th time or so now. – TheEye Mar 15 '12 at 11:00
  • It works for me fine on simulator but not on iPhone. This started happening for me after I upgraded to Xcode 4.4. Before that it never happened! I have tried everything. None of these works!!!! Any suggestions please. – Paresh Masani Aug 08 '12 at 16:21
  • Was hoping it might have been fixed in 4.4. Guess not. Sigh. – smparkes Aug 08 '12 at 19:36
  • i'm not interested in the simulator part, as many apps are only testable on the device itself (ie dealing with blutooth etc).. and unfortunately, disconnecting and reconnecting the device doesn't change anything.. all the answers on this page have been heavily skewed towards the simulator.. i have no idea why – abbood Sep 10 '12 at 11:23
  • The bulk of this answer is about restarting the user launchd and that's applicable to the device case. – smparkes Sep 10 '12 at 18:05
162

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
  • 4,463
  • 3
  • 23
  • 15
  • 45
    Ended up restarting the system! Still don't know what caused the issue though! – lostInTransit Apr 25 '09 at 06:18
  • 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 May 21 '10 at 18:58
  • 6
    As comment below says, you can usually see the hung process in Activity Monitor and kill it there. – mxcl Sep 05 '10 at 18:29
  • 14
    I hate restarting :) Quitting the hung process worked for me: ps ax | grep Simulator will show your running apps, in my case it was MyApp.app that was hung. – BadPirate Jan 28 '11 at 00:08
  • Logging out and back in did it for me. – memmons Mar 18 '11 at 01:57
  • All I had to do was do a `kill -9` on the hung process, as found by `ps ax | grep Simulator` (suggested here by BadPirate) – Kyle Wild Apr 26 '11 at 02:50
  • 10
    I often get this in XCode 4.3. Restarting the application or quiting the simulator does not help. I have to restart the computer in order to make it work. – Øystein Nov 14 '11 at 14:20
  • Restarting fixes the problem for me. This gets really annoying and seems to happen more lately. From what I can tell this happens more often on Lion than on Snowleopard. Maybe because Lion sort of restores the previous environment after a reboot. – Besi Dec 09 '11 at 14:54
  • 4
    If you get this while running in debug on device, you'll need to restart the device – wkhatch Feb 06 '12 at 22:34
  • I tried to fix this for hours. I cleared everything, but I ended up restarting my computer. It worked. Really stupid! – Szwedo Feb 20 '12 at 00:42
  • 1
    This should not really be the accepted solution. Correct answer in http://stackoverflow.com/a/8104400/464289 and workaround in http://stackoverflow.com/a/9797116/464289 – JRG Mar 29 '12 at 01:28
  • This error comes when you drag drop break points while debugger attaching with the device. – MadNik Oct 26 '12 at 04:16
  • Great answer! I had created a new app of the same name, but Xcode tried to run it with the old app already on my device. I had to delete the old app to run the new one. –  Jul 28 '13 at 17:29
70

I find I have started having this issue with Lion + Xcode 4.2. I have also experienced the issue in Xcode 4.3.

I have tried all the suggestions but none of them have worked other than a full reboot.

Here is how you determine if you require a reboot quickly.

List out all your Zombie processes:

ps -el | grep 'Z'

If you see your app listed as a Zombie process you will need to reboot your machine. The error message states "This generally means that another instance of this process was already running or is hung in the debugger". Well, Xcode is detecting this Zombie process which you can't kill. The only way you can then fix it is with a system reboot. :(

EDIT, 20120823: I have some better knowledge of Zombie processes so I wanted to update this answer. A Zombie process is created when a parent process does not call wait() (wait for process to change state) on a terminating child process. You can't run 'kill' directly on a Zombie process but if you kill the parent process, the zombie child process will be 'reaped' and removed from the process table.

I haven't seen this issue in a long while so haven't inspected to see what the parent process is in this scenario. The alternative to killing the parent process is to reboot your system. :)

jyap
  • 3,516
  • 2
  • 16
  • 16
  • Thanks, I had 7 instances of 3 programs I was working on running as zombies. – ArtSabintsev Nov 15 '11 at 07:16
  • 1
    Rebooting is sufficient but not necessary, as mentioned above. Also, there are sometimes zombies around that don't cause the problem, so looking for zombies this way isn't really a reliable measure. The only sure sign is the message in Xcode. – smparkes Dec 22 '11 at 21:18
  • Have you tried killing these zombie processes as root? I rebooted before I thought of doing it. – Ryan H. Jan 13 '12 at 16:34
  • 1
    @smparkes, yes, that is obvious based on this question which discusses this error message. – jyap Jan 15 '12 at 09:10
  • 1
    @HZC, yeah, you can't kill zombie processes even as root. – jyap Jan 15 '12 at 09:10
  • I have randomly fixed the simulator with the following: ps -el | grep 'Z' then kill -3 PID (of the parent of a zombie process) and then log out and log in. Simulator now works. – snez Jan 23 '12 at 14:41
  • I killed all weird processes I could see with `ps -ax`. Then I did a full logout and a login. Still no dice. Reboot works. I get this problem to manifest easily by having AppCode and Xcode duke it out for control. – Dan Rosenstark Aug 28 '12 at 05:23
  • @jyap unfortunately haven't been able to replicate recently. Before it was enough to just switch IDEs and hit run a lot... – Dan Rosenstark Aug 30 '12 at 22:06
  • +1 because I learned about Zombie processes. wow. I have 576 Zombie processes of old iPhone simulator runs but the error from the question does not appear. But now I'm running out of PIDs. lol – Matthias Bauch Oct 18 '12 at 17:45
20

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.

n3wscott
  • 409
  • 3
  • 11
15

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
  • 337
  • 3
  • 9
14

If you find your problem is due to zombie processes: 

ps -el | grep 'Z'
(as in the earlier comment https://stackoverflow.com/a/8104400/464289) and just want to fix the problem immediately, you can do so without rebooting or killing anything. Just rename your project target executable:
  1. Click on the project on the left-hand pane
  2. Select Build Settings in the middle pane
  3. Under 'Packaging' change 'Product Name' from $(TARGET_NAME) to $(TARGET_NAME).1

Easy!

Community
  • 1
  • 1
JRG
  • 2,065
  • 2
  • 14
  • 29
  • this didn't work for me, got the same error I get: Provisioning profile 'mataleao2' specifies the Application Identifier 'au.com.mataleao' which doesn't match the current setting 'au.com.mataleao-1' – sapatos Aug 08 '12 at 11:00
  • Are you testing on the simulator or on the iPhone? – JRG Aug 08 '12 at 11:53
  • i'm testing on iphone only, teh functionality i'm testing will only work on the phone – sapatos Aug 10 '12 at 08:32
7

Well, no answers but at least one more test to make. Open Terminal and run this command: "ps-Ael | grep Z". If you get two entries, one "(clang)" and the other your app or company name, you're hosed - reboot.

If you are a developer, enter a short bug and tell Apple how absolutely annoying having to reboot is, and mention they can dup this bug to "rdar://10401934" which I just entered.

David

David H
  • 40,852
  • 12
  • 92
  • 138
5

Resetting the iOS Simulator fixed the error for me. Although this will remove all of the Apps you have in Simulator, it fixes the problem without having to restart the machine.

You can reset your iOS Simulator by doing the following:

1) Go to the "iOS Simulator" menu, next to the Apple () logo on the far left of your main screen.
2) Select "Reset Content and Settings...".
3) Read the pop message and if you agree click "Reset" otherwise, click "Don't Reset".

domthinks
  • 81
  • 1
  • 1
5
  1. Close simulator
  2. Stop the app from running in xCode.
  3. Open Activity Monitor and search for a process running with your App NAME.
  4. Kill this process in Activity Monitor
  5. Rebuild your project and you should be all set
negrelja
  • 422
  • 1
  • 7
  • 17
4

Restarted the Device, Worked! :D

Thanks Everyone for the great suggestions.

Haris Hussain
  • 2,531
  • 3
  • 25
  • 38
4

I had a recursive setter that blew through the stack and killed my app in such a way that I had to power boot my iPad. It was provable with a fix in the code.

mobibob
  • 8,670
  • 20
  • 82
  • 131
4

I had the problem @jyap mentions with zombie processes. The only way to clear them was to reboot. However, I noticed that my friends working on the same project would get the same issue but could kill the simulator without creating a zombie process. I completely uninstalled Xcode and re-installed it, and while I still get the error, it doesn't create zombie processes, so I don't have to reboot.

Before I did that, I was using this really ugly workaround: change your app ID and run again. You end up with junk copies of the app in the simulator, but you can put off rebooting for a while.

Christopher Pickslay
  • 17,523
  • 6
  • 79
  • 92
4

This error happens a lot to me, almost every time I test the app in the Simulator, forcing me to restart.

Here's a workaround if you want to get some work done:

  • Click your project in the Project navigator
  • Go Target -> Info
  • Add a key for Application does not run in background and set to YES.

This will mean that when you press the home button in the simulator or quit the simulator, the app doesn't hang.

Don't forget to change this setting back before distribution! Put it on your release checklist :)

Chris Burt-Brown
  • 2,717
  • 1
  • 16
  • 16
  • 1
    This is dangerous, since it prevents you from testing backgrounded behaviour until you remember to change it back. – tc. Feb 16 '12 at 19:33
  • @tc: Yes, I agree. However, if you are forced to restart every single time you run your iOS app (which was what I was having) then this may still be better than the alternative. – Chris Burt-Brown Feb 16 '12 at 20:58
4

If this happens when testing on the iPhone. Just restart the phone. From what I have been told the phone or simulator still believes there is an instance of the app running, so when it was last run it had not terminated correctly do to either an error in your code or the phone/simulator just wanted to have a moan.

Popeye
  • 11,839
  • 9
  • 58
  • 91
4

I got this error while debugging my app on an iPhone 4. Hard rebooting the iPhone solved my problem. (Powering off the iPhone hung...)

I did not have any zombie process on my mac and rebooting the mac did not solve the problem.

Maybe this bug can manifest itself on both the simulator and actual devices???

craig
  • 201
  • 1
  • 5
3

I just had this error. I tried restarting the simulator and Xcode but my project would only work again after a clean and build. No idea what caused it.

Daniel Wood
  • 4,487
  • 3
  • 38
  • 36
3

I had same problem and solved it by doing the following

  • Deleting the app from the device,
  • Disconnecting the device from Mac,
  • Turning the device off and back on,
  • Quitting and relaunching Xcode,
  • Quitting Instruments,
  • Finally, Clean and Build again.

I also did one more thing, because Xcode is configured to use iOS 5.0 and my project uses iOS 4.3

  • Remove all frameworks and add them again.
Xenph Yan
  • 83,019
  • 16
  • 48
  • 55
Joey
  • 2,912
  • 2
  • 27
  • 32
3

The Cause

Running your app in the Simulator before the previously running app has completely stopped.

The Fix

Wait until you see the Stop button become active again before running again.

(I'm using Xcode 4.2.1. This problem happened very frequently when I upgraded to OS X Lion).

invisible squirrel
  • 2,968
  • 3
  • 25
  • 26
3

Alternate workaround:

  • Give your app a new identifier. If it's called com.foobar.myapp, call it com.foobar.myapp01

You lose all data in the app as it's actually a new app running as far as the iPhone simulator is concerned. This may or may not be more annoying than rebooting - just wanted to add it to the list.

n13
  • 6,843
  • 53
  • 40
2

Happened a lot for me with Xcode 4.2.1 on Lion. Updated to 4.3.2 and it doesnt happen anymore. Glad they fixed it.

tbag
  • 1,268
  • 2
  • 16
  • 34
2

Mike Ash posted a solution (god bless him!) that doesn't require a reboot. Just run:

launchctl list|grep UIKitApplication|awk '{print $3}'|xargs launchctl remove

The above command lists out all launchd jobs, searches for one with UIKitApplication in the name (which will be the job corresponding to your app that's improperly sticking around), extracts the name, and tells launchd to get rid of that job.

Jano
  • 62,815
  • 21
  • 164
  • 192
  • I had many chances to test this (sigh). Sometimes it works, sometimes I have to reboot my iPhone, or even my Mac (the command above says "process not found"). – Jano May 21 '12 at 20:04
2

I think this is caused by force-quitting your app on the iPhone prior to pressing the stop button in Xcode. Sometimes when you press the stop button in Xcode, then it takes extra time to quit the app if it hung. But just be patient, it will eventually quit most of the time.

CommaToast
  • 11,370
  • 7
  • 54
  • 69
2

Fixed by rebooting my phone after deleting the app, then rebuilding it clean and running again. Works fine now.

Weird.

CommaToast
  • 11,370
  • 7
  • 54
  • 69
2

No rebuild or reinstall needed for my issue, and in my case the error appeared when trying to run the app on the iPhone. Simulator worked fine.

Solution: Delete app off phone, do a cold restart of phone and now all is well.

timv
  • 3,346
  • 4
  • 34
  • 43
1

You may alloc variable in function or tab. It will dealloc if your function or tab is quit. So you must declarate it member variable or global variable.

bTagTiger
  • 1,261
  • 5
  • 23
  • 38
1

I was getting this error all the time until I stopped trusting the "Stop" button in the Run dialog box. Now that I always hit stop in the toolbar before trying to run, I have yet to encounter any zombie processes.

Angela
  • 3,050
  • 2
  • 30
  • 37
0

In most worst condition Reset content and setting of iOS Simulater, and most of the time in my case, quitting XCode along with simulator, always work works for me with XCode4.6 (that frequently get hanged)

rptwsthi
  • 10,094
  • 10
  • 68
  • 109
0

I faced this kind of issue once in my case here's what i did

  1. Delete the app from simulator.
  2. Delete the derived data folder.
  3. Perform a clean action in the project by selecting the product menu - clean
  4. Reset the simulator.
  5. Quit Xcode.
  6. Try running the project now if its working fine else go to step 7
  7. Repeat all steps from 1 to 5 and then restart your machine.

In most of the cases i got it running at step 6 extreme cases i had to restart my machine.

user2538944
  • 305
  • 4
  • 12
0

This error used to occur in older versions of the iOS Simulator because older instances of a job in another device that was shutting down could collide with the new instance.

iOS 6.0 and later should not experience issues like this because iOS 6.0 introduced the usage of bootstrap subsets, and iOS 7.0 introduced the usage of a dedicated bootstrap server (launchd_sim) which is completely isolated from the host's bootstrap server.

Jeremy Huddleston Sequoia
  • 22,938
  • 5
  • 78
  • 86
0

If you are running tests from the command line, (using xcodebuild test), make sure that the running simulator matches the device you are expecting to run the tests on.

You might be running command line tests that use iPhone 5. If you have been running iPhone 6 in XCode ad then run the command line tests, sometimes the iPhone 6 will stay running and you need to manually select the iPhone 5 device, and then run the tests again.

Rose Perrone
  • 61,572
  • 58
  • 208
  • 243
0

Oh my - I tried EVERYTHING listed above and in other posts. Re-installed Xcode, rebooted my machine, copied all the missing files into the right folders... Eventually I backed-up my iphone, wiped it and restored it, and it worked!

I think what may have been the cause from reading in and around this was disconnecting my iphone white it was running with performance tools catching leaks. Or some such thing.

Aaaah, big sigh of relief.

Smikey
  • 8,106
  • 3
  • 46
  • 74