When I am publishing .aab (Android App Bundle) extension file in google play console then it showing me error i.e. 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
I search regarding this topic solution and I get also bt didnt work for me. like : 1. clean, rebuild and again generate signed bundle.
2. change the location for generate signed bundle.
3. delete the generated file when created at the generate signed bundle time.
and many more. But didnt work anything.
Related
I have a big problem. i follow this tutorial step by step
https://developer.android.com/studio/publish/app-signing#generate-key.
I build my sign .abb file and i got this error after i uploaded it on google play console :
"Your Android App Bundle file has not been signed with the correct key. Make sure to use the SHA1 signing key : XX:XX...."
I don't know why .. and i don't know what to do next .. i've already tried everything..
Edit :
Solved !
i create my app withs react native and i build my apk / abb file with android studio and on google play console i have deleted and recreated a new app and its working
Is this the first apk/aab uploaded for this app?
Judging by the error, it seems like the first apk/aab uploaded to google play console uses a different key (another .jks/.keystore file) then the one you are using right now.
If you lost access to the original key, and opted-in Play Managed Signature, you can easily request a key reset in (Your App > Settings > App Signing > Request Key Upgrade > Lost access...)
If you didn't opt in, I have sad news for you... :(
I have a requirement to upload an apk file to a newly created app in my Goolge Play Console. However there is already another older version of the same app under a different name in my Play Console.
When I try to upload the apk file I get the following error.
"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 have tried changing the ID of the app in the package.json file but it did not make any difference.
if I try to change app.gradle and deleted some auto generated files which had the old APP ID and rebuild it. But then I get the above error.
Any suggestions to fix this issue
I am new to publishing to google play, but everywhere I looked says that you just click build then upload the apk file you get to google play. But the file I am receiving is an .aab file with no APK file to be found. I messed with my settings but cannot figure out why this is happening.
Thing I have tried:
1. Updating Unity
2. Change keystore file
I am not too familiar with unity, so I don't want to mess with too many settings with the risk of messing up the application further
when you generate Signed Bundle or APK for release, if you select Android App Bundle you can get .aab (bundle file).
if you want to get .APK you have to select APK.
in this screen.
I am using Visual Studio 2019 16.4.1. I am trying to put a app onto the Google Play Store in internal testing. My app is being bundle as a aab file. I am getting a upload failed message:
"You uploaded an APK or Android App Bundle with invalid or missing signing information for some of its files. You need to create a valid signed APK or Android App Bundle. Learn more about signing."
I also saw this message which might indicate a bug with VS.
https://developercommunity.visualstudio.com/content/problem/845978/you-uploaded-an-apk-or-android-app-bundle-with-inv.html?inRegister=true
Now my question is how can you poke around inside the aab file and see if it is properly signed?
Also if it isn't signed...is it possible to sign that aab file and how would you do that?
i'm getting this error when i try to upload my app update in Google Console "Upload Fail" You uploaded an APK or Android App Bundle with invalid or missing signing information for some of its files. You need to create a valid signed APK or Android App Bundle. Find out more about signing.
Your APK has to be signed by your production private key. This is how Google knows that you built the APK and will allow it to go to your users. This is a safe guard from someone putting up a fake APK in your store listing.
The Play Developer Console will show you the signature of the key so you can compare it to keys and find the correct one to sign your APK with.
Here is some documentation on signing your APK.