Create the closed testing track and upload the bundle
Everything on this page happens in Play Console and works the same whatever framework built your bundle. Personal developer accounts created after 13 November 2023 can't publish to production until a closed test has run, so the closed track is where your first build goes.
Finish app setup
On the Dashboard, complete the Set up your app tasks: privacy policy, app access, ads, content rating, target audience, data safety and the store listing. Closed testing needs this setup to be done.
Open the closed track
Go to Test and release → Testing → Closed testing. Your first closed track is already there; open it with Manage track.
Choose countries
Under Countries / regions, add every country your testers are in. Testers outside the selected countries can't install the app.
Create a release
Click Create new release, upload the
.aab, add short release notes and save. On a brand-new app, this is where Play Console sets up Play App Signing.Send it for review
Review the release and send the changes to Google. The opt-in link only works once the track's status is Published; the first review can take from a few hours to several days.
Menu names follow the current English Play Console. Google moves things around from time to time; the official help pages listed under Sources are the reference.
Add testers with a Google Group and share the opt-in link
Testers are added per track. You can paste email lists, but a Google Group scales better: whoever joins the group can opt in, and you never have to edit the track again.
Add the group
In the closed track, open the Testers tab, select Google Groups and enter the group address (it ends in
@googlegroups.com). With TestBunny you add the platform's group shown in your panel, so you don't have to run a group yourself.Set a feedback channel
Enter a feedback email address or URL. Testers see it on the opt-in page.
Copy the opt-in link
On the same tab, copy the link testers use to join and save your changes. The link starts working after the release is published.
Testers join, then opt in
Each tester joins the Google Group first, opens the opt-in link with the same Google account, accepts and installs the app from Google Play. A closed-test app can't be found by searching the store.
Testers must use one Google account for the group, the opt-in page and the Play Store on their phone. Most “I can't see the app” messages come from a second account on the device.
The 12 testers / 14 days rule: what counts
To unlock production, Google needs at least 12 testers opted in to your closed test, and those testers must have stayed opted in for the last 14 days without a break at the moment you apply.
- Counts: testers who opted in through the link and stayed opted in. Uploading new releases to the track doesn't opt anyone out.
- Doesn't count: someone who opts in, stays fewer than 14 days and leaves. If they leave and come back, their 14 days start again.
- Doesn't count: internal testing. Only a closed test meets the requirement; open testing becomes available after you get production access.
- Not enough on its own: the number. Google also looks at whether testers really used the app, and it may ask you to keep testing if engagement was low.
Plan for drop-outs. If you recruit exactly 12 people and one leaves on day 10, you wait for a replacement to complete their own 14 days. That's why TestBunny's Starter plan has 15 seats and Pro has 25: the spare seats keep you above 12 when someone quits. Compare the plans.
Keep testers active and ship at least one update
Google's production access form asks how testers engaged, what feedback they gave and what you changed because of it. An honest answer needs a test where people actually used the app and you actually shipped something.
- Give testers concrete things to do each day: a flow to finish, a screen to check, a setting to change. TestBunny testers follow a daily task plan and file bug reports with evidence; your panel shows every tester's activity day by day.
- Reply to bug reports quickly and fix what's real. Write down what you changed: it becomes your answer to Google later.
- Ship at least one update to the closed track during the 14 days. Testers stay opted in and get the new version through Google Play.
How you build and upload that update depends on your framework: each setup guide shows the exact version bump and build command.
Apply for production access
Check the numbers yourself
Make sure Play Console shows at least 12 opted-in testers and that 14 days have passed. TestBunny can't see your Play Console; opt-ins on our side are reported by testers.
Open the application
On the Dashboard, choose Apply for production.
Answer three sections
Google asks about your closed test (recruiting, feature coverage, feedback), about your app (audience, value, expected installs) and about your production readiness (what you changed and how you decided it's ready). Save each page with Next; leaving without saving loses your answers.
Wait for the review
According to Google, reviews usually take 7 days or less, sometimes longer. The account owner gets an email when it's done.
TestBunny's production access prep turns your test's records (participation, devices, completed tasks, bugs, feedback) into draft answers for these three sections. Rewrite them in your own words. The decision is Google's: nobody can guarantee approval, and we don't.
Pick your framework
The Play Console part is the same for every app. What differs is how you build, sign and version the bundle. Pick your framework for exact commands, menus and the mistakes that cost testers days.
Sources
Technical details were checked against the official documentation below. Menus and defaults change between versions; when in doubt, the official page wins.
New to the 12 testers rule?
The general guide explains Google's requirement, how a TestBunny campaign runs day by day and what we can and can't guarantee.
Read the general guide