How to Create an AAB File for Google Play (Android Studio)
Step by step: generate a signed Android App Bundle in Android Studio or with Gradle, then upload it to Play Console.
Read the guide →
Thunkable lets you build an app without writing code, but Google Play has its own rules about bundles, signing, store forms and testing. This guide follows Thunkable's publishing flow step by step, adds the Google Play parts it does not cover, and shows how to avoid the keystore mistakes that cost developers their update path.
Yes. To publish a Thunkable app on Google Play you export the app from Thunkable as an Android App Bundle, create the app in Google Play Console, upload the bundle, complete the store forms and release it. If your developer account is new, you also have to run a closed test with at least 12 testers for 14 days before you can apply for production access.
Everything in the Thunkable section below comes from Thunkable's own publishing guide. The Google Play sections come from Google's Help pages.
| Item | Why you need it | Guide |
|---|---|---|
| A Google Play developer account | One-time US$25 fee plus identity verification | Developer account fee |
| A tested app | Install the app on a real phone before you publish | Why apps get rejected |
| A final package name | It cannot be changed after you publish, and updates need the same one | AAB file guide |
| A privacy policy URL | Thunkable says every Thunkable app requests sensitive permissions or data | Data safety and privacy policy |
| Icon, screenshots and description | Required for the store listing | First publish guide |
| 12 testers for 14 days | Required for many new personal accounts | How to get 12 testers |
Using another no-code builder? See our guides for Kodular and MIT App Inventor.
Thunkable stresses that an AAB file cannot be installed on an Android device. To test on your own phone, use Thunkable's separate download option for an installable file, and keep the AAB for Google Play. For more about the format, read how to create an AAB file for Google Play.
Thunkable says that when you first publish, Google offers to protect your signing key, and you can accept. You can also manage signing yourself, but Thunkable says that is not necessary. In both cases, treat the keystore as important.
| Situation | What Thunkable says | What to do |
|---|---|---|
| Normal first release | Google can manage app signing for you | Accept Play App Signing and still download the Keystore Zip from project settings |
| You want to manage signing yourself | Optional. Download the Keystore Zip, then in Play Console choose to export and upload a key from a Java keystore and provide the zip | Follow Thunkable's current steps exactly |
| You lose the keystore | Save the keystore and password somewhere safe. Google will not provide it. | With Play App Signing, request an upload key reset in Play Console and import the keystore zip into the project |
| You copy or duplicate a project | Duplicated projects share the original keystore, but apps copied from a Share link do not | Check which keystore your copy uses before you publish |
| You import a keystore | Importing replaces the project's existing keystore | Make sure you do not need the old one |
Google's side of this is explained in Play App Signing explained. The reset steps for a lost upload key are in Thunkable's troubleshooting page.
Thunkable says the pre-launch report may show messages that are simply warnings, not errors, and that the app should still appear on Google Play. Read each message anyway.
| Form | Guide |
|---|---|
| App access | App access instructions for reviewers |
| Ads | AdMob ads not showing in a new app |
| Content rating | Content rating questionnaire |
| Target audience | Target audience and content declaration |
| Data safety | Data safety form for AdMob apps and the general Data safety guide |
| Account deletion | Account deletion requirement |
Thunkable components can collect data or contact servers, for example ads, analytics, sign-in and cloud databases. Go through each one you use before you answer the Data safety form.
Google requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers who stay opted in for at least 14 days in a row, then apply for production. See the 14-day requirement explained.
When the days are over, follow how to apply for production access, or read why the button may be missing.
Thunkable says that to update a published app your project needs the same package name, a higher version number and the same keystore. It also says you will not need to change any app signing settings. In Play Console you create a new release, upload the new AAB, add a release name and notes and click Next. More detail is in how to update an app on Google Play.
| Problem | Likely cause | Fix |
|---|---|---|
| No email with the AAB | Still processing, or filtered | Wait about 30 minutes, check spam, then try again |
| The download is blocked | Browser settings | Try Firefox or Safari, as Thunkable suggests |
| The AAB will not install on the phone | AABs cannot be installed | Use Thunkable's separate download for an installable file |
| Play will not accept the update | Different keystore, lower version or other package name | Use the same keystore and package name and raise the version |
| Keystore lost | No backup | Request an upload key reset in Play Console. See Play App Signing |
| Rejected over declarations | Forms do not match the app | Review components, then fix. Reasons apps get rejected |
Yes. Thunkable produces an Android App Bundle (AAB). You create the app in Play Console, upload the AAB, complete the store forms and release it.
Thunkable's guide says to click Publish and Download, choose Publish Android, enter your email and click Send. The AAB arrives by email, usually within about 30 minutes. If Chrome blocks the download, Thunkable suggests trying Firefox or Safari.
No. Thunkable states that an AAB file cannot be installed on an Android device. Use its separate download option to get an installable file for your own testing.
Not necessarily. Thunkable says Google can manage your app signing when you first publish and that handling signing yourself is not necessary. You can still download the Keystore Zip from project settings and keep it safe.
Thunkable says the project needs the same package name, a higher version number and the same keystore. You do not need to change app signing settings when updating.
Thunkable makes no difference. The requirement depends on your developer account: personal accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 days in a row.