LiveCode Forums.

In the Standalone Application Settings under "Android", if you select the "Sign for development only" option and then try saving and installing your apk again.

Peter, think your questions regarding signing are covered in the lessons on the LiveCode site ... http://lessons.runrev.com/s/lessons/m/4069/l/32674-how-do-i-create-a-self-signed-certificate-for-an-android-app http://lessons.runrev.com/s/lessons/m/4069/l/32692-how-do-i-create-an-android-app-for-dist...

George, in your standalone application settings under "Android" if you make sure you choose Signing -> Sign for development only. Then when you "Save as Standalone application ..." this should hopefully build your .apk file. Then you can send this file to your testers via email/Dropbox/upload to a s...

Peter - in the signing options if you try "Sign for development only" does that work? Does it only fail when you try to build an APK and sign it with a key? You mentioned that some of your old projects work ok ... is there something in your stack that's for iOS only that's preventing it from being b...

MaxV, I'm using JDK 1.6 I understand there's a new version of LiveCode (6.5.2) so perhaps the signing issue has been resolved ... ? When using Jarsigner you may wish to include the folder path to your keystore and APK like this for example: jarsigner -verbose -keystore C:\folder\mykey.keystore C:\fo...

MaxV, I'm using LiveCode Commercial 6.5 (rc 7) and also 6.5.1 on Windows - I use Jarsigner rather than LiveCode to sign my APKs (choose "Do not sign" in your standalone application settings) and these install fine on a variety of Android devices. Might be worth trying?

MaxV, yes I think you can sign an app with the community version - but you can't close the source (you'd have to buy a commercial license for that).

What version of JDK are you using? I understand some users have had issues with JDK 1.7 but have had success when downgrading to JDK 1.6.