I have signed my app and the Keystore is in a safe location. When I want to release an update and I build an Android app, it asks me to enter the Key alias password to continue. I don’t know if I initially entered it wrong or I forgot what I set the password to but I get it wrong every time when I try entering the password BUT the build still succeeds using the Keystore and Key alias.
When I upload the apk to the Play Store, there is no problem.
Should I worry about not being able to get the right Key alias password? Is this a bug in the Corona build feature?
So it was working as I stated in my post but it doesn’t do that anymore. Here’s what I did:
Open Corona and build for Android
Select keystore file and enter correct password (when I first created the keystore file and knew the password)
Wait sometime and forget the keystore password
Build an Android update without changing the keystore file (it was already selected from last time). I was asked to enter a password and upon entering the incorrect password I got an error in the console log but the keystore alias still showed and a successful build was still completed. I uploaded this build to the Play Store with no problems.
Back to Corona and I did an Android build but this time I selected a debug keystore, everything worked fine.
Back in Corona, I selected my game’s keystore file for production and upon asking for the password and entering the incorrect one, it did NOT display they keystore alias this time and it did NOT build my Android app successfully (expected).
I guess the first time it worked without a password was just cached data? When I switched the keystore files it stopped working, or should I say it worked as expected.
Anyway, I am using this to try to recovery my Android keystore password but if it doesn’t work then I don’t have any choice but to create a new app with a new keystore file and write down my password this time.
So it was working as I stated in my post but it doesn’t do that anymore. Here’s what I did:
Open Corona and build for Android
Select keystore file and enter correct password (when I first created the keystore file and knew the password)
Wait sometime and forget the keystore password
Build an Android update without changing the keystore file (it was already selected from last time). I was asked to enter a password and upon entering the incorrect password I got an error in the console log but the keystore alias still showed and a successful build was still completed. I uploaded this build to the Play Store with no problems.
Back to Corona and I did an Android build but this time I selected a debug keystore, everything worked fine.
Back in Corona, I selected my game’s keystore file for production and upon asking for the password and entering the incorrect one, it did NOT display they keystore alias this time and it did NOT build my Android app successfully (expected).
I guess the first time it worked without a password was just cached data? When I switched the keystore files it stopped working, or should I say it worked as expected.
Anyway, I am using this to try to recovery my Android keystore password but if it doesn’t work then I don’t have any choice but to create a new app with a new keystore file and write down my password this time.