Can you post the exact error message shown on the tablet when running the app?
Also, can you check if updating to AIR SDK 2.7 helps?
1. Get the AIR SDK: http://www.adobe.com/products/air/sdk/.
2. Make a backup your existing 4.5.1 SDK, it is usually found here: C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1.
3. Unzip the new AIR SDK over the 4.5.1 SDK at the above path.
(If you're on a mac, you'll have to merge the new AIR sdk over 4.5.1 SDK via the command line)
Updating the SDK fixed the problem, and introduced another....
When I "run on device", the build & install process runs. Flash Builder then pops up an alert telling me:
The problem is I just updated AIR on the tablet (8/17/2011, 9am Central time) and the latest version available is 184.108.40.2061 (Amazon App Store - no Google Marketplace access with the tablet)...
If I select "Yes", the program compiles, installs and runs correctly on the tablet. If I select "No", then I get this error on the tablet: "The application Adobe AIR (process com.adobe.air) has stopped unexpectedly. Please try again." with a "Force Close" button as the only option. Clicking the FC button brings the same error message up again. After the second click on the FC button, the screen goes black. I then can hit the Home button to get back to my main screen.
Then, like I originally posted, if I try to run the "xxxx-debug" file I get the same error messages and force closures. But, if I reboot the tablet and then run the "xxxxx-debug" file which was installed, it works just fine. No errors, no force closures. AND it still only has AIR V220.127.116.111 installed on the tablet.
IF - the lack of upgrade process is because of lack of access to the Google Marketplace, then where can I get the V18.104.22.168 version of the AIR.apk to install on my tablet? Next - if this is the case with all tablets without marketplace access, how do I include that with my project? Or do I have to since it works just fine with the 22.214.171.1241 version????????
Thank you for the detailed write-up.
We're going to check this at our end, but to me it seems like that AIR version is unhappy with debug builds.
Meanwhile, as a workaround, you may want to try uninstalling AIR and depending only on the one that gets installed from AIR 2.7 SDK (Till we figure things out).