Can't Test App on Android Devices

[Gage]

Hello,

I am trying to test an application on an Android Galaxy Tab and a Motorola smartphone. I have made sure all of the drivers are in place and have ensured that the Test Target is selected in the Development tab. However, for both devices, when I click Development>Test, the process gets to the point where it is installing the application on the device, but it fails and gives the following error message:

Installation of app failed: 1024 KB/s
(2368468 bytes in 2.258s)
pkg:
/data/local/tmp/tmp.473.B4GosVut
Failure
[INSTALL_PARSE_FAILED_NO_CERTIFICATES]

I have used LiveCode before to test apps, and I have actually used this specific Galaxy Tab without issue. I used another Motorola smartphone of the exact same model (I just had to get it replaced by my cellular provider, so this specific one is a replacement).

Please let me know how to interpret this error message and let me know what I can do to overcome it!

Thank you, and Happy New Year!
Phil E.

[jacque]

Did you assign a certificate in the Android pane in standalone settings? For testing you can just use the generic one.

[Gage]

Hmm,

I selected the box that says Build for Android, but I don't see anywhere on that pane that mentions the word "certificate," so I really can't be sure. What is the option or setting called?

Thanks for your reply!
Phil E.

[jacque]

Near the middle of the left-hand columm is a popup button labelled "Signing". That's the one you want. If you haven't created a signed certificate, choose Sign for Development Only.

You might want to look at some of the other options in that pane too. Unless you have special requirements, the right-side buttons can usually be ignored. The left side is where you assign the name of your app that the user will see, and the identifier that the OS uses to recognize the app as yours (you need to follow reverse-domain order like the example text.) Once you have uploaded your app to either of the Android stores, you don't want to change that identifier; the stores use it to recognize you as the developer.

You should also assign a version number and a version code. The version code determines whether Android will actually install an updated version on your next test run. If the version code matches the one in the test app you've already installed, it won't install again. There are two ways to get around that: delete the first test app from the device before testing a revised app, or change the version code to a different number before building the next version. If you change the code, the new test app will overwrite the older one on the device.

You can also assign an icon to your app in this pane. If you don't do that you will get the generic bugdroid icon. That won't hurt anything though.

[Gage]

jacque,

Thank you for your responses!

I found exactly what you were talking about, but I am getting the [INSTALL_PARSE_FAILED_NO_CERTIFICATES] error message.

The strange part is that I have not done anything to this app differently than any other app I have tested, and those worked. Furthermore, I have tested this exact app before on this test device, but from my desktop computer instead of my laptop computer.

So I am hoping to understand what causes the above error message, so I can correct that... was hoping you were correct that it was just the Signing Key, but after changing that, the error message has remained the same :/

I really appreciate your time and effort! Hopefully we can get this figured out.

Best,
Phil E.

[jacque]

Hm, odd. I'm almost out of ideas. There was a change to the Android SDK a while back, so the next thing to try is to make sure you have the latest Android tools installed. When you launch /tools/android, let the manager update everything to the latest versions. Then re-launch LiveCode and make sure you have LiveCode's mobile preferences pointed at the main android installation. On my Mac, that folder is called "android-sdk-macosx" and in prefs the full path to that folder is listed.

If that doesn't work, I guess the next step is to contact support.

Edit: one other thought. Make a new virtual device and see if that helps.

[Gage]

Well, sadly, I had to close the book on this one with no conclusion. I was traveling and using my laptop, which never ended up working.

I did get it to work fine without any problems when I got back to my desktop. Curious, but oh well.

Thank you again for your help jacque!

Phil E.