Phew. Sorted it! I was entering the old password for the individual keystore for this app, which Corona was allowing me to do with no error, so I assumed it was the right password. Turns out the conversion tool set the new password to be the same as the overall Keystore password for all apps, so all my old individual passwords are now not used (which is easier).
So for anyone else having this issue, here is what I did…
Firstly, I was getting the following error:
ERROR: Build Failed: Error code: 256
When loading the Keystore in Corona on the Android build page, I was also seeing this:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore KSF\_Android.keystore -destkeystore KSF\_Android.keystore -deststoretype pkcs12
To migrate the keystore, as the above error suggested, I used the suggested command in the terminal, but this didn’t fully work, as I needed to add the -destkeypass to the end of that command, so I actually ran:
keytool -importkeystore -srckeystore KSF\_Android.keystore -destkeystore KSF\_Android.keystore -deststoretype pkcs12 -destkeypass PASSWORD
I had to enter all the old Keystore passwords for all the apps I had associated with that Keystore. Once that was done, I reloaded Corona, reloaded the Keystore on the Android build page, built for Android, and everything worked fine (no more build error).
However, when I then went to copy the app to the device to overwrite the old version, I couldn’t install it, getting the error:
App not installed. An existing package by the same name with a conflicting signature is already installed.
This was because, when I loaded the Keystore on the Android build page in Corona, I was asked first for the overall password (which I entered correctly) and then for the individual password for the particular app I was building. I entered the old, unique password for that app, as I assumed that had been migrated (as I had to enter it during the migration process). Turns out that wasn’t the case - the new password for each of my apps had been reset during the Keystore migration process to the same value as the overall Keystore password. So now I have one password for the Keystore and that same password is also the individual password for every single app.
I reloaded the Keystore in Corona, entering the same overall password twice and the build worked perfectly AND installed over the top of the old version of my app no problems. On running the app, all data remained from the old version and everything worked fine.
Hopefully anyone else having this issue will find the above works.
Thanks!
