iPhone Simulator - SpringBoard Quit Unexpectedly
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I just installed the latest beta (9A2151) of the iPhone SDK (in /Developer) and now I can't launch the iPhone Simulator. I get "The application SpringBoard quit unexpectedly." This happens when I try to run an app through Xcode and if I start the simulator directly.
I had the original version of the SDK installed before and the Aspen Simulator worked fine - I was able to run the sample apps etc.
Has anyone else come across this one? Is there a way to reset the simulator?
Thanks in advance.
15 replies
Sign in or join Beachball Help to reply.
- 0
gregbern ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have had that happen several times since installing Beta 2, and logging in and out for me has fixed it. I keep getting an error, failing to launch the simulator, then error -10810 when I try to launch any application.
- 0
mrkung ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can confirm this anomaly. I can only run the simulator once or twice before it starts failing. At that point I cannot run any new applications on my machine. I get the -10810 error you mentioned. I found that this process will be running when this happens:
502 405 0.0 0.3 97484 5524 ?? SNs 12:03PM 0:00.38 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker MDSImporterWorker com.apple.Spotlight.ImporterWorker.502
You'll notice it doesn't have a username, just a user id of 502. Usually, it has my username, so I don't know why at this point it does not. Anyway, if I kill this process, it is quickly replaced by another similar process (but with a different pid obviously.)
So, let me jump back a second. Before I ever get caught in that endless loop of new-pid->kill-pid->new-pid->kill-pid, I'll do this:
ps aux | grep mdworker
That will result in two instances of the above process, one running under my username, the other under "nobody." If I kill the one running under my username, I'll regain control of my machine. However, when it gets to the point where it is no longer running under my username, I cannot recover.
I'm glad to hear someone else is having this problem. Now I know something is definitely wrong with the new SDK and not just my machine (or my iphone app.) Consider this a bump.
- 0
mrkung ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hey guys, I experimented further, and I seem to be able to prevent the problem from occurring by disabling Spotlight. I followed the instructions here:
http://osxdaily.com/2007/03/22/how-to-completely-disable-spotlight/
I've been working for quite a while since without an issue. See if that works for you.
- 0
g.difalco ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have the same behaviour with an aplication i am developing; everything was fine before the installation of the latest beta version; now a simple call to the AudioQueueStart method (of the Audio Toolbox) always crashes; after that, i get code -10810 to all attempts of executing almost any program, the spotlight disappears and finally the system makes an automatic restart.
(sigh! it looks like Windows)
- 0
askmehow1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had this 10 8 10 negative error but I revolved it:
I uninstalled xcode 3.1 with
sudo ./uninstall-devtools --mode=allInstalled again iphone
sdk9a2151.dmgAnd Now I couldn't reproduce the 10 8 10 negative error
The AudioQueueStart Works fine.
My NSLog normally appeared in gdb but now they don't.
best regards, askmehow
- 0
askmehow1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
The old SDK disapeard from the iphone dev center.
I need it because the sample applications do not compile with this new one.And I need to work.
I'm peassed off. this new versions of iphone *****, Quality assurance sucked.
The sample applications do not work... 😟
- 0
luzluz ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This happens to me as well, usually after a few compile/run iterations with the new Beta 2 SDK (but no Audio Queue involved).
I found that I can ssh from another computer, and from that shell I can still open some applications (e.g. the Activity Monitor)
$ open /Applications/Utilities/Activity Monitor.app
while opening via the Finder always returns the -10810 error.
Most discussions around the -10810 error which suggest that too many processes are the problem, but using "ps auxM" shows that there are not abnormally many processes or threads running.
I tried to find a responsible process I could kill to fix the situation, but found none so far.
For me, just logging out does not always cure the problem, because sometimes the login window does not appear after logging out, but the machine hangs in a loop apparently trying to show it, visibly re-displaying the screen background about every 2 seconds.
- 0
chippydip ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had the -10810 error and seem to have fixed it doing the following:
1) Create a second account (with Admin permissions) if you don't have one already.
2) Switch to that second account.
3) Delete the /Library/Caches/com.apple.LaunchServices-023XXX.csstore files
4) Reboot
5) Login to your normal account. Things should be fixed.There should be a .csstore file for each user of the system. The last three digits (the XXX above) seem to be the User ID of the user that file is for. You probably only need to remove the .csstore file for the problem account (if you have multiple accounts).
Trying to remove the .csstore file while logged into your own account doesn't seem to work (the file reappears almost immediately). Logging out and using ssh from another system to remove the file might work as well.
Before doing this, my .csstore file was about 1.6MB. After the restart, it was back down to a couple hundred KB and has remained that way since. No more -10810 errors and no feeling like I'm running a Windowz machine again :-P
- 0
Brendan Duddridge ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have this same problem. Very frustrating. In fact, it's happening right now. I was thinking of wiping out my entire system and reinstalling everything from scratch, but I've got so much stuff on this machine, I'd hate to have to waste all that time doing that.
- 0
askmehow1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Don't reinstall your machine because of this.
This is a problem of the SDK reinstall will not change nothing.
We have to wait for another update. This is beta and this like this are normal.
In june the final version of the SDK should not contain any of this problems.askmehow
- 0
Brendan Duddridge ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, in light of finding this discussion, I will not re-install my whole system. However, it sure makes developing for the iPhone treacherous and overly time consuming as you can only get in a few launches of the simulator before you need to reboot.
- 0
luzluz ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
From my development activity it seems to me that the -10810 hang probably happens only when terminating the application in the simulator abnormally, e.g. by using the red stop button in XCode. I'm now trying to avoid this and always exit the app by pressing the home button in the simulator, and I haven't had a -10810 since (while having done many compile/debug cycles).
- 0
chippydip ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Update: Apparently deleting the LaunchServices cache was only a temporary fix. The problem happened to me again last night after a day or two of working properly.
I typically just quit the simulator with apple+Q. I wonder if using the home button first to end the application would help? Of course, that only works if I'm not currently debugging a crash in my app, but it might extend the length of time before I get the -10810 errors again.
Would be nice if this was fixed soon, though.
- 0
nielsbot ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can confirm this.. The simulator seems to be leaking some kind of system resource (files? mach ports?) on abnormal exit. I'm surprised whatever it is isn't being cleaned up by the kernel.. Maybe it's not a kernel resource being leaked.
- 0
Alex Stapleton ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can get my system usable again without having to do a hard reboot.
SSH in remotely and killlall Dock and Finder then start them up again using open /System/Library/CoreServices/...
This gets the dock and finder able to start new processes again, unfortunately QuickSilver and XCode have issues still so you have to restart those as well to get things working properly. At this point I usually just log out and in again.
It's definitely todo with the big red STOP button in xcode (iow, hard shutdown of simulator sub processes.) Try and avoid clicking it at all costs.