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
Related
I'm trying to upload a new app to Google Play using Android Studio Bumblebee 2021.1.1 Patch 3 and followed the instruction in Sign your app for creating a new upload key and keystore. However, I got the following error:
Your App Bundle is expected to be signed with the certificate with fingerprint:
SHA1: xxx...
but the certificate used to sign the App Bundle you uploaded has fingerprint:
SHA1: yyy...
I checked out the solutions in SO for the similar problem but nothing helped. I should add that I have several apps already on Google Play and I suppose I could use one of the upload keys for them, but I'm loathe to do that for various reasons. I only wish I could remember how I got the other apps to upload.
On Google Play, I discarded the release and uploaded it again. This time, when I navigated to App integrity in Google Play, I was able to specify that I wanted Google Play to generate an app signing key for me. I thought it had done that already, since that's the default. I selected the default and Google Play accepted the app. Had it failed, I was prepared to use the key from another of my published apps.
Click on the Select Sign-in key(locate top of AppBundle text) and select Release signed by google
If it's not working then delete the old Keystore and create again maybe you mistake in it
I got the error: JAR_SIG_NO_SIGNATURES, when I try to publish my brand new app on the Play Store. I have tried checking the V1, V2, and both boxes together, none of them solved the issue. That seems to be the only solution I can find.
I am using app-release.apk and there are no errors upon the signed APK being built.
Just because you generate release type of your .APK doesn't mean it's being automatically signed. You need to get familiar with this steps to sign your app.
Bottom line, you need to generate a release key that will be used to sign your builds. This can be done various ways, the easiest one being following Android Studio IDE steps in
Build -> Generate Signed Bundle / APK
I realised as I took the screenshots that I wasn't logged into the owner account and hadn't yet accepted the terms of service to allow Google to manage app signing.
I contacted Google and asked for the owner email, which happened to be one I made years ago, then was allowed to accept and upload my app. Thanks all.
This is now resolved.
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 made an app & then created an APK, generated a signed APK (I was using AndroidStudio 3.0).
I tried to post it, but I had this issue: "You must use a different package name because "com.example" is restricted." I searched on youtube then I solved this issue.
Now I have another issue when I publish my APK to Google Developer Console. The APK is signed I don't know why this doesn't work....
The error is: "You uploaded an APK signed with a certificate that is not yet valid. You must sign the APK file with a certificate that is valid"
You should read the whole of the article on "Manage your app signing keys" then maybe re-ask the question when you understand it a little better.
Every app on android is signed. Google will do the signing for you if you opt-in to Google Play App Signing (you should) but you still need to sign your app with an upload key so that Google knows it comes from you, and not some malicious attacker who has taken over your account.
This upload key can be replaced by the Play Console support team, but you should only need to do this in an emergency. Until then you should generate an upload certificate, sign your app with it, and keep the certificate safe.
All the instructions for how to generate an upload key, and sign your app with it are in the article linked above.
We have recently purchased a game from another company and have done some updates to it with all the information converted over to our side.
The game is made and updated using Unity and is for the Android platform.
After doing all of these updates in Unity and using the Keystore that they supplied us (along with the passwords for the Keystore and the Key), we built the APK with no errors.
When I go into the Google Developer account and try to upload the new APK for testing, I get an error at the end of the upload that tells me that the certificate used in the APK is different than the one originally used on the other APKs so it can not upload the APK.
I have searched everywhere and people are saying that it is the Keystore and the key but I have the correct Keystore and Key because Unity would not allow me to build outside of debug testing without it (I tested this by putting a wrong password in for the Key and Unity gave me errors saying I had the wrong password).
I am using
- Macbook Pro with OSX 10.8.3
- Unity Version 4.1.3
I have all the correct SDKs for Android and the manifest package name matches the Bundle Identifier for the project. (The Bundle Identifier also matches the correct one attached to the Google Dev site.
Please help.
Unity will not stop you from building out an APK signed with a keystore that is different that what a previously built APK was signed with. So the unfortunate truth is that the version currently on Google Play was indeed signed with a different keystore. I've run into this problem myself in the past.
If you don't find the keystore that the app was originally signed with, you will need to pull down the current app and upload a new app.
I try to follow the practice of making the sure the production keystore is stored within the project's repository in an easy-to-find location.