I recently tried to update my app in the google play store using the apk I generated 3 years ago. I have been using the same key store file since 3 years.All of a sudden, it says SHA1 doesn't match.
I am attaching the screenshot for further reference. I checked the SHA1 values for the key store file before uploading it to the store. The values are exactly the same, but when I upload to the store it gives an error.
I have the key store and the password with me safely. I do not want to lose my app history and i want to update my app with same package name and bundleId. Is there any way to achieve this?
Here is the link to the google play console help, complete instructions for creating a new upload key are written towards the end of the page.
Related
This question already has answers here:
What is Android keystore file, and what is it used for?
(4 answers)
Closed 3 years ago.
I am new in android and I have made a app and I am thinking to publish it on play store but I do not know much about keystore and what is signed APK .
I did search on youtube and Google and also on stack overflow that help me
Stackoverflow link 1
Stackoverflow link 2
According videos and these link I am able to make .APK of android project but I am confused with some blog that say to make signed APK and save keystore in gradle file or something similar like that . Also some blog Says if you want to update your app you should store keystore locally
And I am getting very confused . Pleas explain me what is the process . Thank You .
It is necessary to generate signed apk while publish app on play store for that purpose you have to select path(key store path) where .jks file is generated that contain details app info(keystore file info) & other signing authority details
More than 3 years ago we have started with our app on Play Store and we were using RSA1024 keystore .p12 file. However, since JDK 1.8_121 1024 bit keystore files are not supported by Oracle, so I cannot use newer java version to compile the app.
When I tried to create RSA2048 bit key file, it works, however I couldn't upload the update cause a "wrong developer information" or similar.
Any idea how to create 2048 bit key from 1024 bit key and to be recognized by Google Play Store?
Once you have a key to sign your app, you can't change it. This is a restriction with Android, and not specific to Google Play. Changing your key is known as "Key rotation". Key rotation may be coming in the future according to this article but doesn't exist yet. I'd wait.
If you really need to do this, a process which involves publishing a second app is described here.
I have developed an application few months ago by Android Studio and the operating system was windows and i did upload that application in play store that time. Now i have changed my operating system from windows to Ubuntu. Now when i am going to upload an update of that application, it's showing SHA-1 key is not matching. Now how can i replace my old SHA-1 key by new SHA-1 key for the application ? Help needed . upload error image
You can't do anything .
Google says it clearly that the application is identified by the keys used to sign it.
Consequently if you've lost the keys, you need to create a new application.
This question already has answers here:
The apk must be signed with the same certificates as the previous version
(15 answers)
Closed 6 years ago.
I have read lot of similar questions but none of them answered my question
This is first time I am had uploaded an apk in google play store.
I made a mistake by uploading a developer sign key and publishing it to Alpha group.
Now I had unpublished it but it won't let me overwrite a new apk with production key.
Moreover now I can't create a new app in my profile since app with my package name already exists in play store now.
Is their something I can do now?
I really don't want to change package name, since thousands of users are already using this app from different sources. They need to get this apk with same package name and same production sign key.
Any guidance will be helpful.
Is their some way I can reach out to Google Support team?
Thanks!
EDIT: I had published it using a developer sign key we use internally for testing purpose
Unfortunately, signatures are set forever after your first publish to any channel. You'll have to create a new app with a new ID in order to get your correctly-signed app on the market.
I am adding Google Maps into my application for the first time.
I have gone through several tutorials for getting the Google Maps API key for deployment.
But every where the first step indicated is to create a debug.KeyStore OR the create our own application keyStore
Then copy our SHA1 and paste it with the package name while generating API Key.
My small doubt is:
I am giving an Update of my application and added Google Maps in my version 2.
I do have the keyStore of my application that is already live on the play store.
So what do i do now as I already have my key and have to use the same key for the Update.
I dont want to mess up things at the time of deployment.
Please Help.
You must be use that keystore file which is already within the application on Google Play Store. Because if you create new keystore file then you have to regenerate process again.
So you have to go to with your old one keystore file.
You should be using the keystore that you already have. Basically you have no other option.