AMDeviceInstallApplication failed: -402653114 [NME bug]

Testgame with Xcode 4.5 runs fine on device.
But upon setting up a new Game I get "Build succeeded", and then:
...
[LOG] [ 85%] PostflightingApplication
[LOG] [ 90%] SandboxingApplication
[LOG] AMDeviceInstallApplication failed: -402653114

Testgame is the only game i can run on the device, simulator also fails...

Try running it a few times on the device - that's a 3rd party issue nobody is able to figure out but goes away after a 2nd or 3rd run.

Simulator shouldn't be failing to run at this point. Logs please. The only thing that comes to mind is that you need to explicitly update your simulator from within Xcode.

This is just a variation on this bug:
http://www.haxenme.org/community/forums/bugs/fruitstrap-randomly-fails/

I found out this happens when the bundle identifier is the same as in any app that is already on the device. -> change bundle identifier -> clean project -> build again. -> works.

That doesn't make sense, since that would imply that constantly re-testing the same app would continually trigger the error?

I wonder what happens if you explicitly delete the app with said bundle ID and then run - that might also do the trick, no?

For me it always happens when i make a new stencyl game, and forget to change the bundle id to something new.

so i figured that on my device there is already a build where i used:  com.yourname.gamename
Might even be a stencyl 2 build with that bundle id. Maybe it wouldnt know how to overwrite a stencyl 2 build?

Unlikely since the device doesn't care whether a game was made with Stencyl or not. They're all IPA's as far as the device is  concerned.

This same issue is happening to me after updating my 4S to iOS 6 and my Xcode to 4.5.2

Exact same "AMDeviceInstallApplication failed: -402653114" until I changed the identifier. And even now that I've gotten it to work on my phone, the game will only go to the splash screen before closing. When this happens the log prints:

Code: [Select]

Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.
0x2fe490cc in __dyld__ZN13dyldbootstrap5startEPK12mach_headeriPPKclS2_

I then have to open it by clicking on its icon.