02-09-2012 12:59 PM - edited 02-09-2012 01:01 PM
I installed Tablet OS 220.127.116.1111 to test
my application (any application) and when I try to launch it, it exits and shows a notification with the error message, "Unable to start Application due to error 9".
I just rebooted and now all applications are starting normaly except mine. Mine attempts to start but then quickly exits and unfortunately with no error message or any sort of notification.
History of steps
Received a link to this webpage via email https://bdsc.webapps.blackberry.com/native/beta/re
Followed the steps to upgrade to Tablet 2.0 and restarted
Upgrade was successful
Went to my 1.0.0 compatible app and tried to launch it
It opened, showed a white screen for ~5 to 10 seconds then exited. Retested a few times with the same results.
Opened App World and App World showed a notification for an upgrade to the 2.0 compatible version of my app.
Installed the app successfully
On the home screen found my app icon and attempted to launch it.
Solved! Go to Solution.
02-10-2012 12:57 AM
You can add trace() statements to your app, to determine where it is crashing. If you package a version with debug info, those trace statements should appear in the log file, which you can access with the above method. You can also ssh into the device and simply cat the log file.
But why not just set a breakpoint in your app in FlashBuilder, do a debug-on-device, and see how far you get?
02-10-2012 02:51 AM - edited 02-10-2012 02:55 AM
The application is downloaded from App World. I uploaded it and set the minimum required Tablet OS to version 2.0. Now that I've downloaded Tablet 2.0 it showed up as an update and I downloaded it to test it out.
Unfortunately, now I can't debug on it because I'm getting "failure 500 application author does not match debug token author" and or "Please enter your CSK password". Nothing seems to work. I'll create a new post for these.
02-10-2012 02:14 PM - edited 02-10-2012 02:15 PM
It seems the solution to the error 9 and error 3 was a reboot.
The cause of why my app was exiting quickly had to do with setting a StageWebView to a local file in the View initialize event. It could be caused by attempting to access or create a File to early or attempting to load the webview contents too early.
The solution was to wait until the creationComplete of the View.
Note: This worked previously so something must have changed in 2.0. Test your apps.