How to permanently fix Xcode 5 SpringBoard failed to launch application with error: -3 [duplicate]
Asked Answered
U

7

64

Launching apps from Xcode 5 to the iOS simulator (multiple OS versions) fails with SpringBoard failed to launch application with error: -3. I can get around the problem by 'turning it off and back on again' (quitting the simulator and relaunching, uninstalling and redeploying the app, etc.), but it seems to come back again later and in other projects.

Can someone help me understand what the real problem here is and if there is a permanent fix?

Uke answered 18/9, 2013 at 23:22 Comment(7)
I also get this error quite frequently even after resetting the content and settings of the simulatorDisavow
Most of the answerers below seem to have neglected to read your question, since you said you have tried quitting/resetting but it keeps happening later. This is a recurring problem for me too, seems to happen more with XCode 5.Arteriosclerosis
@Arteriosclerosis - yes, that's why I haven't chosen an answer yet. I know how to workaround it, but I would really like to understand what's causing it and how to resolve it altogether.Uke
Interesting that Bill the Lizard points to an old link dealing with an unrelated error code and says there is already an answer. As Kyle says, he knows the workaround! He (and I and probably loads of others) would like to know the cause and/or the fix for this issue.Quinine
Agreed, I think this question needs to be re-opened. The duplicate message even says "If those answers do not fully address your question, please ask a new question". The new question is: How to fix the issue permanently.Harrington
@KyleClegg I don't have privileges to vote for reopen, but I've flagged it for moderator attention.Harrington
Check out this link : #19855722Prefigure
W
12

I don't know why, but on my end deleting the app from simulator solved this.

Weep answered 19/9, 2013 at 11:0 Comment(6)
I had to change the simulated device once also.Tipple
many different answers to the same issue .. but none is giving the 'reason' why it happens... all answers are just one way to bypass the issue tip next time...Granophyre
@erwin I think that's just a bug Apple should fix.Weep
Again, a temporary solution only. I get this problem even when starting a fresh new project.Harrington
@JosephHumfrey Do you use latest Xcode?Weep
@Weep Yep, using version 5.0.2 (5A3005).Harrington
P
11

Quitting simulator seems to help.

Phototelegraphy answered 22/9, 2013 at 5:3 Comment(0)
J
4

Run Activity Monitor and force Kill the simulator process. Then Run you app again and simulator will launch automatically and problem goes away.

Jone answered 5/10, 2013 at 18:18 Comment(1)
active simulator window, then press Command + Q is more convenient.Corrugate
E
3

I think this may be because you have installed (run) it on 64bit iOS7 simulator and now you are trying to use same install/files on 32bit simulation.

Engrossing answered 19/9, 2013 at 11:19 Comment(2)
I believe this is the answer. I've switched between 64 bit and regular iOS Simulator and when I try to run 32 bit, it throws the Spring Board -3 error. If I run in 64 bit, it loads without a problem.Whereupon
Perhaps some truth in there something (related to new 64 bit simulator), but this isn't the entire answer. I've started a fresh new project without switching, and I still get the error.Harrington
H
3

1) Press stop button from Xcode

2) Exit Simulator

3) Press run button again from Xcode

This is the quickest workaround that I have tried, did not have to delete the app or do anything like that.

Horn answered 2/10, 2013 at 23:34 Comment(0)
E
3

Restart simulator, if it wont solve your problem and then delete all content. It worked for me.

English answered 4/10, 2013 at 14:1 Comment(0)
G
0

I noticed I started getting this error when manually editing files that are in the Emulator's disk space.

With "the Emulator's disk space" I mean a path similar to this one: ~/Library/Application Support/iPhone Simulator/7.0/Applications//.app/

Having the build process re-run solved my problems too so I feel like it has something to do with file permissions or some sort of checksum failure.

Gunderson answered 23/10, 2013 at 12:52 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.