08-12-2011 11:13 AM
I had all setup and working. But I had to uninstall Flash Builder and re-install again. Anyhow,
now I can't run the app using flash builder or debug.
I can't debug or run from inside the Flash builder. Debug tokens uploaded, certifgates are setup.
But I can export the final build from Flash Builder and install it using the deploy files in the sdk folder using cmd. That works but when the app runs, its blank.
When I try to run or debug, this is what I get in Flash builder
Deployment Failed: Info: Sending request: Launch
Info: Action: Launch
Info: Debug air: on
Info: Updated debug host to 169.254.0.2
Info: Launching <app info>
And on the device:
Unable to start application AppName-debug -Error code:8
08-15-2011 11:31 AM
Can you paste the contents of your blackberry-tablet.xml file? There could be non conformities there which could result in the FailedInfo: done failture.
Looking forward to your reply.
11-16-2011 09:47 AM
I suggest to start a new thread an post exact output of the launcher, also would be nice to see command line (or steps) of how did you create your bar file
12-17-2012 12:09 PM
01-10-2013 02:16 AM
Please re-check the connection as the steps:
1. open simulator first
2. open QDE
3. open"window"-preference-blackberry-BlackBerry Deployment setup wizard
4. follow the steps and take care of the previous configuration if you had.
5. make sure your project-"run as "- run configuration has add the simulator as a target at the bottom of the first sheet
6. make sure your simulator can be available form QDE(ping ip is the best way)
7. when the simulator is stack, restart it and waiting for the ip available to retry.
01-10-2013 03:58 PM
The XML he mentions is the bar-descriptor.xml. Specifically, name of author which must match the signing key.
The failure to launch simply means that the PlayBook received the file, but was not able to execute it.
This means a signing issue (which can also be checked by hand using the BAR Verification bat file from RIM).
Or it can mean that you lost some packets during transmission, and the BAR was corrupted and needs to be redeployed.
It can also mean a critical packaging error (zipping by hand perhaps?)
And sometimes it happens because one of your two XML files have bad values or non-standard XML tags.