Production access approved: your next steps on Google Play

Production access means the Production page and Open testing are now unlocked for your app in Play Console. It does not mean your app is live: you still need to create a production release, check your store listing and declarations, and send the release for review. This article walks through those steps in a sensible order.

What actually changed on your account

While you were in closed testing, Google kept some features switched off. The official help page on app testing requirements says that features such as Production and Pre-registration "remain disabled until developers meet these testing requirements," and that open testing "becomes available after you gain production access."

So after approval you can:

• create releases on the Production track
• run an open test if you want a public beta
• set up pre-registration if you would rather build interest before launch

Your closed test does not disappear. You can keep it running, which is useful (more on that below).

If you are still waiting for the decision, see how long the production access review takes instead.

Step 1: Re-check what reviewers will see

Production access was a review of your testing. Your production release gets its own review, and Google is clear that "review is not a troubleshooting step." Before you create the release, go through the basics again:

1. App content declarations. Open Policy and programs > App content and make sure nothing is outstanding: privacy policy, ads, app access (sign-in details), target audience and content, content rating, Data safety. Our article on declarations that block review covers the usual gaps.
2. Test credentials. If your app needs a login, the credentials in Play Console must still work. Reviewers need "valid, working login credentials" to test the app's features. Accounts created for the closed test sometimes expire.
3. Target API level. If you built your closed-test version a while ago, check it still meets the current target API level requirement for new apps and updates.
4. Store listing. Your public listing now matters. Read it as a stranger would: does the description match what the app does today?

Step 2: Decide where you will launch

Production has its own country and region settings. Testing tracks are synced with production by default, but you may have unsynced your closed track to add a specific country (for example, Indonesia for an Indonesia-based tester group). Our article on countries for a closed testing track explains how that setting works.

For production, pick the countries you can actually support: languages in your listing, payment methods if the app is paid, and any local rules that apply to your category. You can add countries later, so starting smaller is fine.

Step 3: Create the production release

The flow is the same one you used for the closed track:

1. Open the Production page in Play Console and create a new release.
2. Add your app bundle. You can promote the build you tested, or upload a newer one. If you upload a newer build, its version code must be higher than every build you uploaded before.
3. Write release notes. Keep them short and honest.
4. Review the release and save it.

Many developers ship the final closed-test build to production, then ship fixes as normal updates. Others make one last round of fixes first. Either works, as long as the build you send is stable. Google asks for apps that are "stable and free from broken functionality, crashes, or missing screens."

Step 4: Send it for review

Changes collect on the Publishing overview page until you send them. If managed publishing is on, approved changes wait for you to publish them, which lets you pick your launch moment. If it is off, the release goes live once it is approved.

Google says reviews can take "a few hours or up to seven days (or longer in exceptional cases)." Plan your launch date with that buffer in mind, and do not announce a fixed date to users until the release is approved.

Step 5: Keep your closed test running

Google's own best practice is to "continue running closed tests while resolving user-reported issues and bugs," because "updating your app in closed testing before releasing to production helps minimize low ratings and negative reviews."

In practice that means:

• push risky changes to the closed track first
• let your testers use them for a few days
• then promote the same build to production

Your closed testers can also keep sending private feedback, which you will find under Monitor and improve > Ratings and reviews > Testing feedback. Private feedback "won't affect your app's public rating."

Step 6: Watch the first days closely

Once real users arrive, two things deserve daily attention:

• Crashes and ANRs. Android vitals data starts once users who opted in to sharing usage data begin using the app.
• Reviews. Public ratings start with production. Reply to them politely and fix what they point out. Never offer anything in exchange for ratings; Google's policy prohibits incentivized reviews.

Checklist

• App content declarations complete, nothing pending
• Test login credentials still valid
• Target API level meets the current requirement
• Store listing accurate and up to date
• Production countries chosen deliberately
• Production release created with a higher version code (if it is a new build)
• Changes sent for review from Publishing overview
• Closed test still running for future updates

If you have more apps to launch

The testing requirement applies to apps from personal developer accounts created after November 13, 2023. If you plan to publish another app from the same account, check what Play Console shows for that app before you assume it can skip closed testing; our can you skip closed testing article covers this question.

If your next app needs a closed test and you do not have 12 people ready, GoPlayTester can provide 12+ real testers in Indonesia for the 14 days. Our guide shows the setup, and the production access guide has example answers for the form. Google makes the final decision on every application.