Skip to main content
← Data, API & Backend
Data, API & Backend January 29, 2025 · 1 reply

Issue with Unsigned AAB File for Google Play Submission

Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.

Dear Bravo Studio Support,

I hope this message finds you well.

I am experiencing an issue when trying to upload the AAB file generated by Bravo Studio to Google Play. The following error appears:

"You need to use a valid debug signing key to upload your app. The current APK or App Bundle is not signed with the required debug certificate. Please ensure that your app is signed with the correct debug key before uploading it to Google Play."

It seems that the AAB file is not signed correctly, either with a debug or production key. Could you please clarify the following:

  1. Does Bravo Studio automatically sign AAB files with a debug or production key?

  2. If not, is there a way to manually add a valid signature to the generated AAB file before uploading it to Google Play?

  3. Are there specific steps I should follow in Bravo Studio to ensure that the AAB file meets Google Play's signing requirements?

Thank you in advance for your assistance. I look forward to your guidance to resolve this issue.

1 reply

Wrote something in this thread and want it removed? Request removal

Still stuck?

Ask the community on Discord

This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.

Join the Discord