05-05-2012 03:23 PM - edited 05-06-2012 02:43 AM
CONFIRM. Any app I am trying to run at simulator 2.0 get an error 8! At the same time, running any of those app at simulator 1.0.8 have no problems. Also, running on the real device also have no problems.
05-10-2012 04:40 AM
I'm getting this error on the simulator also. My App works fine on a real PlayBook. On the Simulator it installs the icon but I cannot run it.
Flash Builder also returns errors:
Captive runtime DISABLED:
An internal error occurred during: "Launching Evaluatiemomenten (PlayBook Simulator)".
Captive runtime ENABLED:
Failed to create application process: Exec format error
Again, the App runs fine on a real PlayBook. Also I've even installed a debug key on the simulator. But it will keep saying "debug token issue date missing or in the future". I'm assuming this is not a problem since you don't need a debug token on the simulator.
05-10-2012 04:59 AM
06-07-2012 05:34 PM
I had the same problem using Simulator. Tried removing development app and going again - No Luck. Restored back up of virtual mchine - No Luck. Finally looked for alternatives to Eclipse and found how to build from scratch with a demo that was producing error 8. Going Old School and from command line ... and no error 8.
Finally figured out that Eclipse was not packaging the executable into a xxx.bar file.
Now I use Eclipse to compile and link but I use command line to package and deploy. See these links
To Package ..
To Deploy ...
This also stoped the annoyance of Eclipse failing to connect to the Simulator VM.
Downside can't debug app.
06-07-2012 09:26 PM
06-08-2012 03:58 PM
I am deploying to the simulator (way too early to start deploying to my playbook ) and I thought that you didnt need to use any tokens. Like I said with no tokens set if I use the IDE to build, packakage and deploy I get error 8. If I build and then from the command line package and deploy (with no tokens) it works.
I am guessing but I think error 8 is raised when there is no app to launch on the target. It would be nice if a BB developer could let us know what error 8 meant .
09-01-2012 12:23 AM
I am having a similar issue:
I receive "Error 8" everytime I try to run my application on the real Blackberry Playbook, but I am using the native development environment.
I have tried resetting the Playbook OS (through the desktop application) and I have also tried completely uninstalling and reinstalling the development environment on my PC.
Even the example applications included with the development environment fail with "Error 8".
What led to this situation:
I had my debug token expire, so I was getting "Error 13". I renewed the debug token on the device, and began getting "Error 8". This error has persisted throughout all of my attempts to remedy it. Before the debug token expired, I had not experienced any of these errors.
1) The debug token expiring caused something to break deep within the Playbook OS, which even resetting the OS can't fix.
2) Something randomly changed in my development environment which can persist through uninstallation, manual removal of remaining files, and registry cleanup.
I am leaning towards option #1.
I really want to develop for the Playbook, but this series of events has really put me off.