Hi there, sorry to hear you’re having issues! It’s likely that you fall into the third category of makers in the guide who receive .aab build files out of Adalo. Could you submit this as a ticket to support so we can take a closer look? Also, @oivaizmir are you updating an existing app or submitting this AAB for a completely new Play Store app (Bundle ID)?
I tried a new Firebase project and a new store listing, this is where the error on the screenshot above was coming from.
On the original Google Play Store listing when I uploaded a new build the app would not finish uploading, it would just hang. I tried twice with thirty minutes to upload and no completion.
So this AAB is for a completely new Play Store app (Bundle ID)
I gotcha. So you updated the bundle ID in the Adalo build settings before building as well? AABs are tied to Bundle IDs and signing keys so all three must match up in order for them to be accepted by Google.
I have tried with a new Firebase build just to make sure I did not make some mistake.
I followed the Adalo android guide.
What I resulted with was in the Adalo Android build settings that had the Bundle ID, Frontend google-services.json and Service Account Key google-services.json all reflect together.
I have done this process a fair number of times with APKs, but I have not been able to make it work with the AAB.
I have now done three Firebase projects for this app to triple check, I am still getting ‘your Android App Bundle is signed with the wrong key’.
I have tried this with two separate Google Console projects and had the same issue.
Yes please submit a support request for us to push an .APK build for you. In the future this will be streamlined so that makers can do it themselves, but currently this is the process for pushing builds for copied apps (i.e. new Adalo apps) that are publishing to .APK builds already in the Play Store.