I made an app and successfully published into the Play Store. Then I discovered a bug and fixed it. Now I can’t update the app because it says that the certificate of the two apks are different.
Using the Eclipse signing tool, I tried filling in the same things I wrote the previous time, but that’s not it. I saw that if I link the old apk, I can use the “use existing keystore”, although I can’t select an alias.
If I try to create a new keystore and fill in the same things as before I get a “keytool error: java.io.IOException: Invalid Keystore format”.
Please tell me how I can update my published apk.
I just posted this answer here – Can I somehow get details from android key alias? like validity, organisation and so on – not the same question, but it has the same answer –
Sorry, there is no way to replace a lost keystore. Once it is lost you cannot get it back, do your best to find it, but failing this the best you can do is publish a new app(with a new keystore), and tell your users to install the new app for updates.
Make sure you backup your new key store, send it to yourself via email, put it in a cloud, and put it on a different computer so that doesn’t happen again.
Even if you knew the details that you put in your old keystore you could not recreate it – keystores are designed to be impossible to recreate.
Just in case you want another source: