dmitryame
dmitryame

Reputation: 478

SpringBoard failed to launch application with error: 5

My iPhone application suddenly stopped launching in dev mode. When I launch in simulator it pops up a dialog: SpringBoard failed to launch application with error: 5 There are tons of references on the web about error 3 and 7, but not the 5. I tried to follow the suggestions for the 3 and the 7, clean up the app, remove it from the simulator, restart the xcode etc... -- does not help. Can anybody shed some light about this mysterious error 5 and how to overcome it?

Upvotes: 1

Views: 1245

Answers (5)

cohen72
cohen72

Reputation: 2988

Adding to dmitryame's answer, solving this issue for me was only accomplished by unchecking "Launch due to a background fetch event"only by Under Edit Scheme / Run Configuration.

Below is an image of the culprit causing the error message in my case:

enter image description here

Upvotes: 2

Jayprakash Dubey
Jayprakash Dubey

Reputation: 36447

Quit Simulator and clean Xcode. The fresh build will not show this Alert again. The possible reason for this might be switching between 64-bit simulator and 32-bit simulator.

Upvotes: 0

dmitryame
dmitryame

Reputation: 478

After a while the issue came back, so digging into it, revealed, that I must have accidentally turned on location simulation option in the Run configuration as well as Background fetch (launch due to background fetch event). I was playing with the background fetch and the location events, but decided not to use it after all. Turning those off in the run scheme brought my app back to live.

Upvotes: 6

dmitryame
dmitryame

Reputation: 478

So, here is the answer. It's got something to do with the background location service. Apparently it was disabled for my application. Once I removed it from the Info.plist -- things started clicking again. Put it back -- the same exact issue. One would hope, the messages I got would be a bit more user friendly. Anyways, thanks for helping me.

Upvotes: 2

user2677746
user2677746

Reputation:

I got the same problem 2 hours ago then I closed the iOS simulator and Xcode then run it again it worked perfectly try it maybe it will work.

Upvotes: 2

Related Questions