09-02-2012 11:23 AM - edited 09-02-2012 11:29 AM
Can someone explain what these error are exactly, and how I can fix them?
It happens really often when Im trying to debug.
This is on an actual device and not a simulator
Unable to start due to Error 12
Error in final launch sequence
Cannot prepare and download the binary
Unable to determine returned PID from launch.
09-04-2012 01:09 PM
Does this occur after your program crashes/ shuts down improperly?
I only ask because I sometimes get "Unable to determine returned PID from launch." on my dev alpha when the program crashed or I end the program while debugging.
Also, when I get this error, the icon on the dev alpha is see through meaning the program it still running/closing
A simple restart of the device always clears it up for me.
09-04-2012 01:40 PM
Yes it is similar but this is playbook not dev alpha device. Also the error occurs just after the app launches e.g. A few milliseconds. And yes i find that reboot device fixes it temporarily but its still annoying. Also yes the app doesnt close properly since the app icon is still transparent
09-04-2012 01:50 PM
09-04-2012 02:04 PM
Its defo not a problem with my code. The error occurs before the code in main() starts. It happens when debugging when the app is launched after being uploaded
09-04-2012 03:11 PM
Guessing "No Memory"?
Doesnt make sense, I checked RAM usage and checked flash storage space and all is fine.
I noticed that it may be something to do with assets last time I tried to tackle this problem.
My directories arnt deep, not too many files/folder etc.
09-04-2012 03:33 PM
If you see an icon semi-transparent then your app is still running and in Debug perspective you should see these hung thread and you should be able to terminate your app from there. It's true - new instance of your app will never be started if the old one is still 'running'.
09-10-2012 03:20 PM
This error occurs if the permissions screen shown when your application first launches is not dismissed before a timeout period. It doesn't indicate an error in your application and is something we'll be fixing in a future release.