Error in google play console when tried to upload an aab file exported from the test server

General Discussion
1

Hello Expert,

Today I exported the aab file from the test server and uploaded it to the google play console to find out if it's working or not. I ran into the following error message.

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. Your App Bundle is expected to be signed with the certificate with fingerprint:

SHA1: B4:11:DA:AE:2C:7C:51:3A:EF:1D:28:87:C7:AF:9A:F4:3C:25:B5:4A

but the certificate used to sign the App Bundle you uploaded has fingerprint:

SHA1: CB:D2:2D:87:BE:B8:92:E5:71:8E:0B:BB:6F:6F:BA:75:94:A7:AE:CB

I guess I will just wait till I hear MIT App Inventor's announcement.

2

You shouldn't use the test server for production. If you need the SDK 34 update, please wait for it to be rolled out on the main servers.

3

If you want to build with the test server, you should export your keystore from the regular server and import it into the test server. Always keep backups of keystores because we do not have the ability to restore them if you make a mistake.

2 Likes
4

Thank you so much!