stuck installing app on target device...

[jim1001]

Using Community Edition 7.1.2 (current latest) on Win.

I'm trying to deploy to a real Android tablet. I've managed to get the app installed on the device a few times. However more often than not it gets stuck on the window "Standalone Builder Progress" saying "Installing app on target device...". There are no error messages about what the problem is either during the installation process or after from what I can see. The only way out is to kill the process with Task Manager.

I've followed help I've found on the forums to delete the app before trying to reinstall and setting the Identifier. Still can't get it to install reliably every time - very frustrating.

Would appreciate some messages / logs from LiveCode to see what the problem is.

Thanks in advance,
Jim

[jacque]

Yes: http://quality.livecode.com/show_bug.cgi?id=16664

I suspect you're running a device with the latest security patch. I have four Android test devices. Each received the update on different days. I was able to transfer my test app to a device via USB on each one until it received the patch, when the transfer immediately failed with the symptoms you describe. Since there is no way to cancel the attempted installation, you have to force-quit LC.

When I entered the bug report, no one on the team had received the patch yet so they couldn't test it. Please add your comments to the bug report, as that will draw attention to it. Right now the report is pending, and sometimes those tend to fall lower in the queue.

[jim1001]

Jacque,

Thanks very much for your help - I will add to the bug report.

As you say, a workaround is to transfer the .apk onto the target device manually, e.g. by USB. Then you can browse to the .apk using a File Manager & click on the .apk - should ask to open with package installer which installs the app. I had to enable “Settings - Lock screen and security - Unknown sources” on the target Android device which is probably not very secure if left that way.

However even with this workaround with some apps I get “Parse error. There was a problem while parsing the package”. No idea what the “problem” is.

ps: do you know if LiveCode writes to any log files to help decipher its many terse often cryptic error messages? Or if there is a definitive list of error messages with a comprehensible explanation? (I’m not talking specifically about this “parse error” message which is occurring on the Android device although it’s still related to LiveCode where the app was created)

Thanks again,
Jim

[jacque]

However even with this workaround with some apps I get “Parse error. There was a problem while parsing the package”. No idea what the “problem” is.

It may be that you didn't set the Signing option in standalone settings to "sign for development only". Unless you have created a signing key, you need to use the default key.

ps: do you know if LiveCode writes to any log files to help decipher its many terse often cryptic error messages? Or if there is a definitive list of error messages with a comprehensible explanation? (I’m not talking specifically about this “parse error” message which is occurring on the Android device although it’s still related to LiveCode where the app was created)

Yes, Richard Gaskin and I created a lookup stack for those: http://revonline2.runrev.com/stack/712/ ... ror-Lookup In the IDE the error codes are translated for you, but in standalones or mobile apps you need to look them up yourself. An explanation of what the numbers mean is in the dictionary under "errorDialog".