Update password problems

[SusanB]

I’m updating a three year old app, and may have gotten mixed up when first entering the alias and passwords when saving for this release. Do you get shut out after a couple of wrong password entries? Is there a way to get a fresh start? I’m quite sure I have the correct ones now, but I keep getting “There was an error while saving the standalone application. Signing failed - keystore load: Keystore was tampered with, or password was incorrect.” I am grateful for any help!

[bogs]

Are you using the indy or community editions? Community doesn't allow for passwords.

[SusanB]

Indy. And I have successfully uploaded to the store, but it's been three years.

[bogs]

Hum. Not sure where to point you then, I've only had to deal with a password issue once, and I am pretty sure I didn't go about it in a good way Hopefully someone who knows will step in shortly

[sphere]

If i'm correct SusanB is referring to the password when the package gets signed.
This has nothing to do with Community or Indie version of LC. It works with all versions of LC.

You can create an new Keystore with new passwords via the command line.
Then when signing the package in LC while exporting to Standalone, you can use the new password

[SusanB]

From what I've read, I think creating a new Keystore and passwords makes it so people who already have the app can no longer upgrade. I'd have to remove the old one and reintroduce it under the same name. I plan to change it to a paid app, so those who already have it would not be able to upgrade for free. I want to avoid that and keep all the current users.

[sphere]

I don't know if that's true. But you could test it.
Create a new keystore and password then sign your app and install it to your test device.
Then do it again with a new keystore and password and install it again.

If you save the APK to your device and install it from there, then normally your device will ask if you want to update the existing app.

This way you can check if what you say is true.

[jacque]

Google has started cross checking keystore signatures recently to verify the developer. I'm not sure if this would also affect an update if the signature isn't the same as the old one.

BTW, the dialogs that ask for the keystore info are wonky. I get that error every time if I enter the credentials too fast. You have to type each letter VERY slowly and wait in between for a bit. Usually I count to three in between keystrokes. That seems to work. I suspect something is going on behind the scenes to do some kind of processing before it's ready to accept the next letter.

[SusanB]

Thank you, Jacque. I tried that slow entering, but got the same message.

[jacque]

I'm not sure what to tell you then. But if you are absolutely positively 100% sure you are using the correct credentials then you might want to ask the LC team what's going on. I haven't had to sign any Android apps recently but maybe something broke in the latest LC releases.

[SusanB]

I'm going to try some of the suggestions above first. Maybe I'll try building in v 8 instead of v 9 of LC.....