I have lost my keystore file now i need to update my app on play store is there any way to get my keystore file i have my old signed apk please any answer will be appreciated
Access:
https://support.google.com/googleplay/android-developer/contact/otherbugs?hl=en
and mark the options like below:
You cannot recover a lost keystore.
The signature on your existing APK is just a signature- you cannot reproduce the signature without the key that generated the signature.
Google does not store, keep track of, or ever have access to your keystore. It is completely on the developer to manage the keystore.
Your options are:
Find the keystore
Generate a new keystore and re-upload your application as a new application. You will be starting completely fresh with this option.
Related
I recently inherited a app, and I want to post the update but can't without the originally keystore and key. I got the keystore file and I am not sure if that is enough to create a signed APK from Android Studio that will be accepted by google play?
Until and unless you have the keystore password, you won't be able to use that keystore to sign the app.
My advice would be to contact the original author of the app to provide you with the alias and password for the keystore.
Could someone please clarify if I can use a copy (created at release #1) of keystore for signing off a new release (let say release #3) of Android apk, if previous release (#2) was signed using original keystore? Or should I make a backup copy of an original keystore each time when a new release is signed off?
You can use it any time you want, and any copy you want.
The important thing is that once you upload an APK and release it updates ONLY can be signed with the same keystore. You can and in fact you should store your keystore files at multiple places so you don't lose them. We did once and that was awful, would not recommend. :)
You have to use the same Keystore each time you want to create a Signed application using the same Password which you use to create Keystore.
If you use different details for new Keystore you will not be able to update the new build on Google Play. To update new version of same application apk must be signed with same Keystore each time.
You can also create new Keystore each time while signing the application but it is not needed as you can use the same copy of certificate.
I know how to get my SHA-1 fingerprint either through terminal or eclipse (go to: Window->Preferences->Android->Build), but there has been not many answers on how to keep the SHA-1 fingerprint in cases of emergencies.
Eg, my hard disk died, and I had to export my .apk under a different SHA-1 fingerprint and hence under a complete app new listing in Google Play store.
In case of another harddisk breakdown or a new computer, is there a way to still use the same SHA-1 fingerprint? Maybe I am lacking some knowledge of how keystore certificate works and hopefully someone can enlighten me.
If your concern is about app store apk file then you have to preserve keystore file with which you have uploaded apk on to play store.Don't worry about SHA-1 fingerprint in any case you have to preserve only keystore. And apk creation is dependent on keystore after you have created it.
I am creating an in-app purchase app. I have uploaded apk file once while creating the application in Google Play developer console. But now when I am trying to upload another version of apk file it is showing error of different SHA-1 keys. I have changed the version code and package name is also same. I referred questions here and I got to know that apk should be signed with same certificate.
But my problem is when I export the project from Eclipse to generate signed apk it is not allowing to use existing keystore; moreover when I select existing keystore the dropdown list of alias are empty. So each time I have to create new keystore. Also it is showing "Invalid keystore format" on selecting exiting keystore. Please provide me with some solution to how can I generate an APK with same SHA-1 key.
Is this apk file generated from another computer than the first?
Make sure to have the same .keyStore file on your different PC.
I have the app ready so trying to sign it. I read the dev docs. Am using eclipse and adt so started using export. Am able to export a sample app. While exporting they says to have the key. I have created a new file and proceeded and finally I got the output apk. Once whn I opened the key file, I cant read anything. So I am confused.. Will it be readable?? or like the same? Please tell me about the certificate they are mentioning on signing the app, is this same as the one, the file I have created?? Thanks in advance..
Once whn I opened the key file, I cant read anything. So I am confused.. Will it be readable??
Your keystore file (e.g. mykeystore.keystore) should not be readable in a text editor or other such program.
Please tell me about the certificate they are mentioning on signing the app, is this same as the one, the file I have created??
Once you have finished signing your APK using your keystore (see Signing your Application), the APK will contain a META-INF directory that contains a CERT.RSA file, which is the application's certificate. You don't need to worry about this file at all, and it is automatically generated by keytool when you sign your APK.
Your private key (see Obtain a Private Key) is also referred to as your signing certificate, and is what is stored in the keystore. This is the key that you use to sign your application. After you have generated this key using keytool, you shouldn't need to worry about it anymore.