Copy link to clipboard
Copied
Hi there,
yesterday we updated the AIR version to 3.7.
If the app isn't connected to the PC , the debug version of the app won't start on the test device (Samsung Galaxy SII).
Is this intended?
Best
omi
Copy link to clipboard
Copied
Hi,
Could you please share the steps that you had taken to start the application. Also, share the device version, AIR SDK used, AIR version. This will help us investigating the issue.
-Nimit
Copy link to clipboard
Copied
Hi,
1. debug the app with USB-Debugging
2. App starts and everything works fine
3. Disconnect the device (remove USB cable)
4. Close the app and the process on the device
5. Open the app and it crashes
AIR 3.7
Device Samsung Galaxy S2 GT-I9100G
Android Version 4.1.2
Best regards
omi
Copy link to clipboard
Copied
Hi grosssmutttr,
Do you see it crashing or a black screen? We already have a known issue on Android, while doing USB debugging, applications show black screen instead of showing the waiting connection dialog, but if you connect fdb to it, it moves forward.
Thanks for reporting!
-Pahup
Copy link to clipboard
Copied
Hi Pahup,
yes it shows a black screen but only if I am not connected to the PC and open the app.
The waiting connection dialog only shows up if your are connected to the pc and start the debugger.
Best
omi
Copy link to clipboard
Copied
Thanks for the reply. Basically, because of a bug it's showing up a black screen instead of the dialog. If you want to launch the debug app and you're not doing debugging, then please use the following workarounds.
1. Select wifi debugging option (when packaging from Flash Builder, even if you don’t have a wifi, because anyway you don’t want to debug it, you just want to install/launch it on the device)
2. Export a Release APK from Flash Builder.
and if you're on command line.
1. Package apk/apk-captive-runtime
2. Package apk-debug without –listen switch
Thanks once again for reporting, we have an internal already logged for this, which is under investigation at the moment.
-Pahup