LiveCode Forums.

I have an app in Google Play and all is well.
I'm getting ready to do a very minor update, but when I try to install it on my connected device for testing the old version still runs.

I've tried delete and install, clear data, restart phone with limited success in that I've got it to update once, but not again.

Strangely, deleting the app from my phone does not seem to delete the apps data as far as I can tell. My app has a first run procedure that does not run even when deleting and reinstalling with the "Test" feature of LiveCode. It does run if I reinstall from Google play.

My questions:
Where is the LC app stored on my phone?
(.android_secure "appears" to be empty but I think this may be a limitation of my file browser. Is there a recommended app for this?)

Does the Version number in the Standalone Settings have a bearing on whether an app is seen as an update.

Am I right that once I have a Signature .keystore I can use the same key for updates of the app or do I need to recreate it for each update?

Any other suggested actions are greatly appreciated.

TIA
Bill Leddy

Deleting the old app should have worked. But anyway, Android will not update an app if the build number is the same as the existing app. In standalone settings, change the build number to something else. It doesn't matter if you increase it or decrease it, as long as it isn't the same as the one that was previously installed.

Deleting an app on the device should also have removed the data, but you can also do that manually in Android settings. Go to the Apps setting, find your app, and use the "clear data" button to remove it.

You should never change your signature key. If you do, the Play Store won't consider it the same app and won't notify users there is an update.

thanks Jacque,

I've had to put this project aside for a bit. It may just be a hardware issue (a stretch, I know) Carrier is replacing my phone soon or another, seemingly unrelated, issue.

Your information about the version number and signature was very helpful was very helpful.

Bill

Note that the version number and the build number are different things. The version can, and probably should, stay the same, the build number has to be a single integer and that's what has to change. It doesn't really sound like a hardware issue to me, but who knows, anything can happen.