12AppTesting logo12AppTestingClosed Testing Service
HomeAboutHow It WorksPricingBlogFAQContact
Home › Blog › How to Publish a Thunkable App on Google Play Store

How to Publish a Thunkable App on Google Play Store

Quick answer To publish a Thunkable app on Google Play, use Publish and Download, choose Publish Android and get the AAB by email, create the app in Play Console, upload the bundle, complete the store forms, and run the 12-tester closed test if your account needs it.
Illustration for the guide: How to Publish a Thunkable App on Google Play Store

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.

Can you publish a Thunkable app on Google Play?

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.

A note on accuracy: Thunkable updates its interface and documentation from time to time. If a button name differs from what you see, follow Thunkable's current guide and keep the order of the steps here.

What do you need before you start?

ItemWhy you need itGuide
A Google Play developer accountOne-time US$25 fee plus identity verificationDeveloper account fee
A tested appInstall the app on a real phone before you publishWhy apps get rejected
A final package nameIt cannot be changed after you publish, and updates need the same oneAAB file guide
A privacy policy URLThunkable says every Thunkable app requests sensitive permissions or dataData safety and privacy policy
Icon, screenshots and descriptionRequired for the store listingFirst publish guide
12 testers for 14 daysRequired for many new personal accountsHow to get 12 testers

Using another no-code builder? See our guides for Kodular and MIT App Inventor.

How do you get the AAB from Thunkable?

  1. Open your projectCheck the app name, icon, version and package name in the project settings before you export.
  2. Start the publish flowIn your project, click Publish and Download, then choose Publish Android.
  3. Enter your emailType the email address that should receive the file and click Send.
  4. Wait for the emailThunkable says the AAB arrives within about 30 minutes. If Chrome blocks the download, it suggests Firefox or Safari.
  5. Save the filePut it in a folder named after your app and version so you can find it later.

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.

How do you handle the keystore?

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.

SituationWhat Thunkable saysWhat to do
Normal first releaseGoogle can manage app signing for youAccept Play App Signing and still download the Keystore Zip from project settings
You want to manage signing yourselfOptional. Download the Keystore Zip, then in Play Console choose to export and upload a key from a Java keystore and provide the zipFollow Thunkable's current steps exactly
You lose the keystoreSave 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 projectDuplicated projects share the original keystore, but apps copied from a Share link do notCheck which keystore your copy uses before you publish
You import a keystoreImporting replaces the project's existing keystoreMake 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.

Back up now: Copy the Keystore Zip and its password to two safe places before your first upload. Never share them in a forum or with anyone offering to publish for you.

How do you create the app and upload the bundle?

  1. Create the appIn Play Console choose Create app, then enter the name, default language, App or Game and Free or Paid, and accept the declarations.
  2. Complete Set up your appWork through the tasks on the Dashboard, including the main store listing and the privacy policy.
  3. Create a closed testing releaseGo to Testing > Closed testing, create a release, accept Play App Signing and upload the AAB under App bundles.
  4. Add release notesWrite a short note about this version and click Next.
  5. Add testers and share the linkCreate the tester list and send the opt-in link. See how to add testers and how to share the link.

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.

Which store forms must you complete?

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.

How do you run the closed test?

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.

How do you update the app later?

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.

What are the common problems?

ProblemLikely causeFix
No email with the AABStill processing, or filteredWait about 30 minutes, check spam, then try again
The download is blockedBrowser settingsTry Firefox or Safari, as Thunkable suggests
The AAB will not install on the phoneAABs cannot be installedUse Thunkable's separate download for an installable file
Play will not accept the updateDifferent keystore, lower version or other package nameUse the same keystore and package name and raise the version
Keystore lostNo backupRequest an upload key reset in Play Console. See Play App Signing
Rejected over declarationsForms do not match the appReview components, then fix. Reasons apps get rejected
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.

Sources

Frequently asked questions

Can I publish a Thunkable app on Google Play?

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.

How do I get the AAB file from Thunkable?

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.

Can I install the AAB on my phone?

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.

Do I have to manage the keystore myself?

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.

What do I need to update a published Thunkable app?

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.

Do I need 12 testers for a Thunkable app?

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.