Key takeaways
- The package name ties together Play Console, Firebase, RevenueCat and Google sign-in – choose it once, before the first build.
- Google sign-in that works in testing often fails in Play-distributed builds until the Play app signing certificate fingerprints are registered.
- APKs are for quick device tests; Play needs an App Bundle from a production build profile that targets API level 36.
- New personal accounts run a 14-day closed test with at least 12 testers – start it with a build that already works end to end.
From a Bolt project to a Play listing in four parts
Bolt, the browser-based builder from StackBlitz, creates an Expo project when your first prompt asks for a mobile app. You test it on an Android phone through Expo Go. From there, the way to Google Play has four parts, and Bolt is involved in none of them except as the place where the code started:
- the package name – your app's permanent identity,
- the App Bundle – a signed build that meets Play's technical rules,
- the testers – internal and closed tracks, including the closed test for new personal accounts,
- the production review – listing, policy forms and Google's decision.
Our post on converting Bolt to an Android app compares the Expo route with wrapping a Bolt web app. This article follows the Expo route all the way to production.
Part 1: the package name – choose once, register everywhere
The package name (android.package in the app config) is a reverse-domain identifier such as com.yourcompany.appname. Once a bundle with it is uploaded to Play Console, it cannot change, and no other app can use it. Choose it before the first build – not after an agent has already filled in a placeholder.
The same string reappears in several services, and each one must match:
- Firebase for push notifications – the Android app is registered by package name.
- RevenueCat or another billing layer – products are linked to the Play app.
- Google sign-in – the Android OAuth client needs the package name and the SHA-1 fingerprint of the signing certificate.
- App Links – the
assetlinks.jsonfile on your domain lists the package name and SHA-256 fingerprints.
The last two carry a trap. With Play App Signing, users receive builds signed with Google's app signing key, not your upload key. If only the upload key's fingerprint is registered, Google sign-in and verified links work in your internal APK and fail in the version from the Play Store. Copy the app signing key's fingerprints from Play Console's app integrity page and add them as well.
Talk to an AI Code Engineer about shipping your app to Google Play.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
Part 2: the App Bundle Play accepts
EAS Build can produce both formats. Use each for its purpose:
| APK (preview profile) | AAB (production profile) | |
|---|---|---|
| Purpose | Install directly on test phones | Upload to Play Console |
| Signing | Your keystore | Your upload key, re-signed by Google |
| Accepted by Play for new apps | No | Yes |
Before the first production build, check four things in the app config and on a device:
- Target API level 36. Google has enforced Android 16 as the target for new apps and updates since the end of August 2026. Older Expo SDKs can raise it through
expo-build-properties; test the result on Android 16. - Edge-to-edge layout. On recent Android versions, content draws behind the status and navigation bars. Generated screens often need safe-area padding.
- Back gesture. The system back gesture must lead somewhere sensible on every screen, and leave the app only from the start screen.
- Notification permission. Since Android 13, ask for it in context, after the user turns on something that needs notifications.
Every upload needs a higher versionCode; letting EAS increment it remotely removes one source of failed uploads.
Part 3: testers – internal, closed and the 14 days
Create the app in Play Console, upload the first bundle to the internal testing track and accept Play App Signing. Your team installs it from Play – the first time you see the app exactly as users will, including the Google-signed build.
Personal developer accounts opened after November 13, 2023 face one more step: a closed test in which at least 12 testers stay opted in for 14 days in a row, before Play Console lets you request production access. Practical advice for Bolt projects:
- Start with a build in which sign-up, login and the core feature already work. Testers who meet a broken first screen drop out.
- Recruit from people who actually want the app – a waitlist, existing web users, a community – and give them a simple feedback channel.
- Ship fixes as new builds to the closed track during the test; testers receive them through Play.
- Read the pre-launch report for every closed-track build and add test credentials so its crawler gets past your login screen.
Our closed testing guide also covers the questions you answer afterwards.
Part 4: the production review
After the production access application is approved, your release and listing go through Google's review. Prepare both carefully:
- Listing. A short description of up to 80 characters, a full description of up to 4,000, a 1024 × 500 feature graphic, phone screenshots and an icon. Describe the app as it is – no keyword lists, no promises of features that are not in the build. Our guide to the metadata policy lists common mistakes.
- Data safety. Cover Bolt Database or Supabase account data, analytics, crash reporting and any data sent to AI services.
- Account deletion. An in-app flow plus a public web page where users can request deletion.
- Payments. Digital upgrades use Google Play Billing. A Stripe checkout from the web version only covers physical goods and services.
- Stable backend. A free-tier database that pauses after inactivity can make the reviewer's first sign-in fail.
When this is not how you want to spend your week, our AI Code Engineers handle EAS credentials, Play Console setup, the listing, Data safety, the test phase and the review inside your Play Console – details on the Android submission service page. For the iOS side, read Bolt Expo app to the App Store.
Bolt Expo app on Google Play: checklist
- android.package is final and matches Firebase, the billing layer and the OAuth client.
- Play app signing fingerprints are registered for Google sign-in and in assetlinks.json.
- The production profile builds an AAB; APKs are only used for direct device tests.
- The build targets API level 36 and was tested on Android 16, including edge-to-edge screens and the back gesture.
- The notification permission is requested in context.
- version codes increase automatically with every build.
- The first bundle is on the internal track and the app is enrolled in Play App Signing.
- New personal accounts: 12 testers stayed opted in to the closed test for 14 days.
- Listing texts and graphics describe the app as it is.
- Data safety, account deletion page and Play Billing are complete.
Frequently asked questions
Why does Google sign-in work in my test APK but not in the Play version?
Play App Signing re-signs your app with Google's app signing key. Add that key's SHA-1 fingerprint from Play Console to your Android OAuth client – and the SHA-256 fingerprint to assetlinks.json if you use App Links.
Can I upload an APK from Bolt to Google Play?
Not for a new app. Google Play requires Android App Bundles for new apps. Use the APK for installing directly on test phones and build an AAB with a production profile for Play Console.
Can I change the package name later?
No. Once a bundle is uploaded, the package name is fixed for that app. A different package name means a new app with a new listing, no reviews and no installs carried over.
How long does the whole process take?
For a new personal account, the closed test alone takes at least 14 days, followed by the production access decision and the release review. Organization accounts skip the mandatory closed test but still go through review.
Can you publish our Bolt Expo app on Google Play?
Yes. In a free call an AI Code Engineer looks at your project and Play Console with you and outlines the four parts; we can then run them in your own account.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.