问题
Ok folks.. long story short, I was developing on a computer that I no longer have access to. I was able to retrieve the source code, but not the .keystore file used to sign and publish my application to the market (with several updates). Am I, and my poor users, out of luck if I ever want to update?
I know the password used to sign the key (at least it is one of three it could be), so can I create another? There must be a way around this.. what about a hard drive fail?
回答1:
Faced the same problem. I was trying to restore it via deleted files restoring tools, but it failed. So, there is no other way: you should issue another application.
Generally, the only advise that exists on keystores: "always back it up!"
回答2:
Now it is possible don't worry, here is the full and final steps to reset .JKS file.
Step-1
Download the UPLOAD CERTIFICATE (file name - upload_cert.der) from your Google Play Store Console
Step-2
Go to this LINK https://support.google.com/googleplay/android-developer/contact/otherbugs And fill the application form with your valid Email ID and upload the file (upload_cert.der).
Step-3
Now you will get the Email from support team, and they don't need your .JKS file but .PEM file here is the email Sample.
Step-4
to convert .JKS file to .PEM file you just have to download KeyStore Explorer
After replying the Mail, wait for 48 to 72 hours your keystore fill will reset.
回答3:
Until today, losing your key would make it impossible to update your app with a new version. In such cases, the only solution was to publish a new app, with a new package name and key, and ask all of your users to install it.
Starting from today, the app signing key in the Play Console is now securely managed by Google Play meaning that you are only responsible for managing your upload key. If your upload key is compromised or lost, Google's developer operations team can assist by verifying your identity and resetting your upload key. Google will still re-sign with the same app signing key, allowing the app to update as usual.
For existing apps, it requires transferring your app signing key to Google Play. For new apps, Google can generate your app signing key. Once enrolled in app signing, you sign your APK with an upload key, which Google uses to authenticate your identity. They'll then strip that signature and re-sign your app with the app signing key.
Reference: Play Console Help > Manage your app signing keys
回答4:
If you know your keystore password, you still don't have the associated private key to sign your app. You also have no chance to generate the same private key which corresponds to your public key.
Therefore: Always backup your keystore file. It's as important as your source code.
回答5:
It is possible for a long while.
- Follow the instructions in the Android Studio Help Center to generate a new key. It must be different from any previous keys. Alternatively, you can use the following command line to generate a new key:
keytool -genkeypair -alias newalias -keyalg RSA -keysize 2048 -validity 9125 -keystore nameofkeystore.jks
This key must be a 2048 bit RSA key and have 25-year validity.
- Export the certificate for that key to PEM format:
keytool -export -rfc -alias newalias -file upload_certificate.pem -keystore nameofkeystore.jks
Then upload this pem file and fill the form and submit it to this site . And then you will receive an email once we've registered the new upload key . Only accepts key reset requests from the Play Console account owner.
All well and good. You can publish new release apk with your new jks file.
回答6:
No need to Remove Your app from play Store You can Update Your app. it’s Possible now, After May 2017 you can Update your app if you lost your keystore or keystore password. Don’t lose Hope you can update your app using new Keystore file please refer this blog new keystore update on playstore here i wrote how to update apk if you lost your keystore follow the step and create new keystore , I updated my app using this step. you need to enable google play app signing on play store console
回答7:
From long days, I also search a solution for that, but not successfully till now. If you have the last version of your app apk, then you can retrieve certificates from that by using the jarsigner cmd command. But you need a private key for update. Google Play did not provide any relaxation for that.
回答8:
I have generated the signed apk using android studio , so in the "key Store Path" i just typed some name without extension, and fill this popup and signed the application.
next time for publishing the application i don't remember the path and name where it was created.
somehow i find the default location which is "C:\Program Files\Java\jdk1.8.0_45\jre\bin" : \jre\bin
and in that folder short by date ,then i tried with recent file and it worked for me.
Note : you should remember the Key store password and key password.
回答9:
There must be a way around this.. what about a hard drive fail?
I would like to add that always keep a backup of the keystore in cloud storage like Google Drive, Dropbox or email it to yourself.
回答10:
Yes, you can release an update to existing app with a new key!
Google now allows you to upload the new key to existing app by requesting them to reset it through email/live chat in Google Support.
This process takes 1-2 business days.
I followed this process and uploaded an update to the same app with a new key. Google Play Store technical team helped me to reset the previous key.
回答11:
It’s Possible now, After May 2017 you can Update your app if you lost your keystore or keystore password. You can not recover your lost keystore but you can replace keystore on playstore. Click here
来源：https://stackoverflow.com/questions/4322367/i-lost-my-keystore-file