I am trying to upload a new APK file to GooglePlay. I have uploaded several updates for the same app before, but now I get this error:
I have no idea what's wrong here, especially since I've uploaded new APK's for this app before. Can someone enlighten me on what may be the problem, and how to fix it? Thanks!
The error is with the certificate (keystore) used to sign the application.
Did you sign the application? Or perhaps you are trying to upload a debug build (straight from eclipse for example)?.
An app needs to be signed with a keystore. They keystore is unique to you. If you loose it, your app can't be signed with another one. Google Play uses that as security, to ensure your app comes from you and not someone else.
Related
I am managing a mobile application that was first published by another person and I was on my way to release the first update on my own but I couldn't.
Used technology : react-native
What I did:
Followed official react-native doc on how to publish (create keystore, configuring project accordingly, generating aab, uploading it to Google Console)
When I uploaded my .aab file, I got the following error
Upload failed
Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again: SHA1: *SHA1 Key*
I understood that there is a key problem but I couldn't know what would solve it, I tried downloading the keys provided in the Google Console but that also was a dead-end !
What can I do ? Can someone explain how can two developers (or more) manage the releases of the same application ?
You have to basically have the same signing certificate which was used to upload a build in the first place and use the same certificate they have used to originally sign the app. Otherwise you cannot publish a new update for the app. if you have lost the certificate, you can contact the google team.
Hope it helps. feel free for doubts
I have gotten my app ready for distribution but when uploading am getting this frustrating error saying, "You uploaded an APK signed with a certificate that is not yet valid" . You need to sign your APK with a certificate that is currently valid".
Have tried several remedies i found online yet no success. I have changed by time zone severally, renamed my apk, cleaned project, even new keystores for my signed apk.
Is there a sure way to get round this? Please help. I renamed my packaged name earlier. Not sure if it contributed to this
I have published my app on Google play a few days​ ago and since then i had to uninstall and reinstall my Android studio. Now I don't have the signing key anymore. Is is possible to make the exact same or i can't update my anymore on Google play?
Signing key is a jks file independent from AS.
If you have lose that file, you can't update your app anymore.
As mentioned in this other answer
You can create a new keystore, but the Android Market wont allow you
to upload the apk as an update - worse still, if you try uploading the
apk as a new app it will not allow it either as it knows there is a
'different' version of the same apk already in the market even if you
delete your previous version from the market
Do your absolute best to find that keystore!!
When you find it, email it to yourself so you have a copy on your
gmail that you can go and get in the case you loose it from your hard
drive!
You have to save the jks file in a directory different from the Android Studio one. It is not related to Android Studio
I suppose if you change pakage name and app name it shouldn't give you any problem on google play console. But you can't update that one, sorry. Try your best to recover the jks file!
I have developed and android Application and export as APK file to publish this on google play .Problem is that when i try to upload an apk file there gernerated an error of
"The certificate that signed this apk is not valid until the future. Create a new certificate."
And Apk dnt be uploaded please any one help me or tell me where will be the issue i have exported it as apk file its certificate information as required in eclips
There is probably some issue with the certificate. The certificate guide lets you create a certificate valid for many years, which it suggests to make at leat 25. Double check if you made sure that is correct.
OR
Try moving your system time back one day and sign your app, should be a fair workaround :)
I think you have set the time in your machine wrong. Maybe a time ahead of the google servers.
Check this out,
time set 3 hours ahead in my windows
This also proves it
You need to generate a valid certificate. See the following link for signing your app for a release:
App signing & releasemode
I upload my first app into market, and now I want to upgrade a new version, but I got this exception when I upgrade my app. " The apk must be signed with the same certificates as the previous version."
I lost my certificate keystore, what can I do in this situation? unpublish my app and rename the package?
Can I upload other app using the other keystore?
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.
Of course, any other your application you can upload with other certificate. It is used only for the security purposes: to ensure that upgrading person is the one who is the author.
Generally, the only advise that exists on keystores: always backup it!