Unable to upload Android app aab file in Play Console

Asked 1 years ago, Updated 1 years ago, 110 views

After creating and releasing one app on Android Studio, I am now trying to upload the second app from the Play Console.When I try to upload a file with the extension .aab created with Android Studio in the Play Console, I get the following error:

The Android App Bundle has been signed with the wrong key.Please sign the App Bundle with the correct signature key and try again.App Bundle is fingerprinted with SHA1:xxxxxx...
It must be signed with the certificate in , but the fingerprint of the certificate used to sign the uploaded App Bundle is "SHA1:yyy...
".

The fingerprint of the correct signature key here was the same as the fingerprint of the SHA-1 certificate in the Upload Key Certificate of the app being created.It's different from the one in the first app.

I would appreciate it if you could tell me in detail what to type and which button to press on which Android Studio screen.

Or is it possible to reissue the key?In that case, will the key of the first application be changed?

I have looked into the Android developer site and many other things, but I don't seem to understand how the key works.

Tried

I deleted it in the Play Console, deleted the Android Studio file once, and re-created and uploaded the aab file from the file I saved in the backup before creating the aab file.

After running Build>Clean Project on Android Studio, I also tried to create a new aab file again.

android-studio kotlin google-play-console

2022-09-30 16:16

1 Answers

As for self-solving, I made a new aab file by backing up the developed file, created a new Play Console, and uploaded it to it, and it was successful.
I think there is a more appropriate way, but it has been solved, so please refer to it.
I can't use it to update the app.


2022-09-30 16:16

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.