When I try to upload the aab file of an android app modified from the original MIT App Inventor project file (which had earlier successfully been uploaded to Google Play Console) by creating a new release, I encounter the error “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…”
Just to add, the “Export Keystore” and “Delete Keystore” options have always been disabled/greyed out for. I am not sure if there is any settings that I have to do on MIT App Inventor to enable them and to fix the issue that I have with uploading the aab file.
Thanks for replying; server is ai2.
I have now created my own keystore file and imported it to App Inventor, and hoping it wouldn’t give me any issues, once Google resets my keys to this key.
server is ai2
I have now created my own keystore file and imported it to App Inventor, and hoping it wouldn’t give me any issues, once Google resets my keys to this key.
After I imported the keystore file, “Export Keystore” and “Delete Keystore” options are now enabled.
I ran into something similar before and in my case the issue was not the code itself but the signing configuration. Google Play was rejecting the upload because the modified build was not matching the original app signature. It may also be worth checking whether the version code was increased properly before exporting the new build.
I have now created my own keystore file and imported it to App Inventor. After I imported the keystore file, “Export Keystore” and “Delete Keystore” options are now enabled. I am hoping it wouldn’t give me any issues while uploading the build to Google Play Console, once Google resets my keys to this new key, which I have requested. I will also ensure that the version code is increased properly before exporting the new build (I didn’t know this had to be done manually). Thanks for pointing it out to me!