Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Uploading Android App Bundle to Google Play Console - key signing error

I'm trying to upload a brand new .aab file to the Google Play Console, but keep getting this error:

Upload failed
You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it.

I'm completely stumped, as I generated a new key for this app bundle at the time of generating the app bundle, i.e. through the Build > Generate Signed Bundle / APK... menu item in Android Studio, so it is a brand new key, unused by other apps.
I've even tried creating a whole new keystore with a new key in it, but always get the same error. Is this some quirk someone else has come across?

When enrolling for App Signing by Google Play for this app, I chose the "Let Google manage and protect your app signing key (recommended)" option, and from all the documentation I've read, the key that you use to sign the app with first becomes the "Upload Key", so it seems like I'm doing everything correctly, but no dice.

Does anyone have any advice, or past experience on this?

like image 249
jaseelder Avatar asked Jan 21 '19 23:01

jaseelder


People also ask

How do you fix 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?

Answers related to “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” first, you need to generate a signing key using keytool and create keystore file for your project.

How do I upload a bundle on Google Play?

Upload App Bundles or APK To Google Play This is how you do it: Navigate to the 'Release Management' and then 'App Release' tab in the menu. After this, you will be asked to choose any one type of release from four options- internal test, close test, production release, and an open test.


2 Answers

I am facing the same issues, in my case signingConfig was setup, I made one simple mistake, that I forget to change app debuggable to false. so even though I generated from menu or from gradle command, build was successfully generated but it was debuggable so play store not accepting signed apk and give me and message like Upload Failed The Android Bundle was not Signed in .

like image 77
Himesh goswami Avatar answered Oct 10 '22 21:10

Himesh goswami


make sure to change app debuggable to false in build.gradle file

enter image description here

like image 26
Mohsen mokhtari Avatar answered Oct 10 '22 21:10

Mohsen mokhtari



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!