How to Promote a Closed Test Release to Production

Before promoting

• Production access granted: you’ve received approval after your application.
• Your best build is on the closed track, with crashes fixed (see Android vitals).
• Store listing polished: final screenshots and description (see listing graphics).
• Production countries chosen.

Steps

1. Play Console → your closed track → Releases.
2. On the release you want, choose Promote release → Production (wording may vary).
3. Check the bundle, version and release name.
4. Write public release notes. These are for users now, not testers.
5. Review errors and warnings, save, and send for review from Publishing overview.

Promoting reuses the exact bundle your testers used, which is safer than uploading a new build. If you have to build again, use a higher versionCode.

First release vs later updates

Google’s staged rollout help says staged rollouts can only be used for app updates, not when publishing an app for the first time. So:

• First production release: goes to all users in the countries you selected once approved. Keep countries narrow if you want a soft launch.
• Later updates: use a staged rollout (for example 10% → 50% → 100%), and halt if something goes wrong.

Keep the closed track

Your testers on the closed track get whichever version is newest. Keep it as a beta channel for future updates (see keep the closed test running).

Launch-day checklist

• Monitor Android vitals and Crashlytics hourly on day one.
• Reply to early reviews.
• Thank your testers and ask the happy ones for an honest public review.

Frequently asked questions