Dear good morning, in my organization we want to update the current app that is in the google play, for that I understand that the key with jks format is required, unfortunately that key is not found and was lost, I can carry out the publishing process of the app but it does not work as an update itself.
Will there be the possibility of recovering that key or some other way to generate the apk with that key for the update process?
Always make a backup in a safe place and do not forget the username and passwords.
The key you comment has a .keystore extension
If you had the keystore, but not the passwords you could probably do something with:
http://code.google.com/p/android-keystore-password-recover/
If you don't have the Keystore, you definitely have to create another one and upload a new app to your Play Store, since you couldn't replace the existing one!
HOW TO SIGN YOUR APPLICATION!
Firstly you need to obtain a production Keystore to sign the application, this is done through the utility
keytool
, this is an example:But in addition to the utility
keytool
now for ease you can use this method:Sign your release build (If you want to create a new keystore, click Create new.)
With the .keystore file that you obtain you must sign your application, from the Android Studio menu you can do it, it will require the path of your keystore:
What is the difference between
debug.keystore
and the keystore that I generate to upload applications to Google Playstore?The file
debug.keystore
is usually located in one of the following paths:~/.android/
on OS X and Linux;C:\Documents and Settings\<user>\.android\
on Windows XP;C:\Users\<user>\.android\
in Windows Vista and Windows 7, 8 and 10.but this keystore is NOT suitable for signing applications destined for the Google Playstore. , this is a Keystore or certificate for debugging. This certificate is valid for one year, you can even delete it and when you start it
Android Studio
will generate a new one.unlike the certificate or keystore that we generate, which needs an Alias password, in addition to a Keystore password. Even an important point is that you can define a validity of this certificate in years.
https://developer.android.com/studio/publish/app-signing.html#release-mode
Unlike the keystore you generated, it
debug.keystore
is extremely important to save it , make a backup and avoid losing it! because you will not be able to upload signed updates of your application in case you lose it. If you lose it you will be forced to create a new signature and upload a different application.You can even set up to automatically sign your app with this keystore that you created for production.
Impossible if you don't have the
keystore
one that was initially signedapk
, what I advise is to deactivate the current app and upload the update, as if it were a new app, this involves changing the internal identifier of the application.To inform that there is a new update: You can modify the information on the tab and then put the application in "deactivated" mode. Current users who have the app installed will always see that tab. New users will only see the listing for the new app.
Save it
keystore
in a safe place, and it is recommended to have several copies in the cloud, usb disk, laptop etc...It happened to me that I had the keystore corrupted and I could also update by generating a new one and I did not have to reset anything.
Just send an email to Google explaining the situation and they ask you for a .pem file that is achieved with a new keystore. They respond to you around 2 days maximum in my case and you can then update as usual.