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
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 an Android project in my Google Play Developer Console. I managed to automate uploading of nightly build to the Alpha channel but I also need to download the APK to get its md5 hash for my internal purposes.
I can't get md5 hash before uploading because App Signing by Google Play is enabled for this app so each APK file that I upload is re-signed with Google's keystore.
Is there a way to download APK file from Alpha channel for my own project?
You can download original and re-signed APKs from the Play Console, in the Artifact Library.
There isn't an API to download re-signed APKs today unfortunately.
Pierre's answer is correct. However, taking an MD5 hash of your APK is probably a mistake. In particular if you use this for verification you will probably introduce a bug. This is because of Google Play security metadata. This won't be consistent on all versions of your APK, and in particular can change with time without you republishing.
If you need to check the authenticity of your app, can I recommend the primary thing you check is the app signing certificate hash. This should be enough for almost anyone and is what major app developers do. If this is not good enough, please check the hash of any particular section of your app you are worried about (eg the classes.dex or a particular resource file). Please don't check the whole APK, you will cause yourself problems.
Hello all I have an APP on play store and I uploaded the bundle file first time and kept the keystore save it and then uploaded to playstore. After some time I updated the APP with version 2 and used the keystore app signing key which I created in the first time it got uploaded
But now I am doing the same and the playstore say
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
I don't know what to do here, its so bad I am stuck here This is my first APP and I already have this signing issue can you suggest me how to upload the new versions of APP on playstore and fix this signing key issue.
Check for the key store you use with the app is correct and no changes made on it.Try again.And also ensure that the key store you are using is of the same app not of any other app.
There a different approaches to overcome this problem. See also the link code4rox provided though nothing of these proposals worked for me and I wasted many days and nerves. My suggestion to you would be:
Reset the old keystore with the support of Google Play Developer Support (Play Console)
Create a new keystore with your IDE
Convert the new keystore to a .pem file with JDK's command line tool "keytool" or use "KeyStore Explorer" (open source GUI replacement for the Java command-line utilities keytool and jarsigner)
Send the .pem file to Google Play Developer Support.
Two days later you can update your App with the new keystore.
I met strange thing to upload my apk on Google Store.
I needed to upgrade my app so I rebuild APK with the same keystore file which was used in last one.
But I got this issue. This is unity project.
I checked all build settings including short bundle version and build version on Unity Editor, but I couldn`t find the strange thing.
I upgraded build version and short bundle version and tried to upload APK on Google Store, but I got the same issue.
How Can I solve this problem?
Please let me know what the cause of this issue is.
The SHA1 hash for the two applications are technically different. So there are really only two options:
You are actually signing the APK with the wrong key. I would run a quick SHA-1 over what you think is the signing key to verify before doing anything else.
This is the LEAST likely. Something is wrong with your signing setup - I don't know how you produce artifacts (CI, manually, etc) but you could always try signing your APK manually without any tools to verify it isn't the problem of something else https://developer.android.com/tools/publishing/app-signing.html
Being blunt, 1 is much more likely than 2. So I would first start checking the hashes of other *.jks files you have nearby before venturing down the path of verify tool correctness.
You're using a different keystore. There is sometimes a keystore for debugging, and a keystore for the release. Ensure you're not using the incorrect one.
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.