Google Play production access: apply after your closed test
· 5 min read
Your closed test has run for 14 days. Now Google wants you to apply for production access, and a rejected application can mean another round of testing. This post covers what the application asks, what Google says about turned-down applications, and what to write down during the test so your answers are easy and true.
Who has to apply, and when
I checked Google's page App testing requirements for new personal developer accounts on 10 November 2026. The step applies to personal developer accounts created after November 13, 2023. Before you can apply, you must run a closed test with at least 12 testers who stay opted in continuously for at least 14 days. Testers who leave early don't count. If someone opts out and back in, the 14 days must be consecutive. The details of that rule, and how to get testers through it, are in Google Play 12 testers for 14 days.
Once you meet the requirements, you open the Dashboard in Play Console and click "Apply for production". Google's page doesn't give a more exact moment for when the button shows up. If you don't see it, check your opted-in tester count on the closed track first.
What the application asks
Google's page groups the questions in three parts. It lists the themes, not the exact wording, so here are the themes:
- About your closed test: how easy it was to recruit testers, whether testers used all the available features, whether their usage matched what you expect in production, and a summary of the feedback you received and how you collected it.
- About your app: your target audience, what value it offers, and an estimated range of installs in the first year.
- About production readiness: the changes you made after the closed test, and how you decided the app was ready for production.
Google also says you must summarize your testing feedback when you apply, and that you should offer testers a clear feedback channel such as an email address, a website or a messaging forum.
What Google says about turned-down applications
This is all Google's page says, and I'm not adding to it:
- If your app needs more testing, "you may need to continue running your closed test". The reasons Google names include fewer than 12 opted-in testers and testers who weren't engaged with the app during the test.
- Review is not a troubleshooting step. Google evaluates production apps for policy compliance, and it says that submitting a non-compliant app and hoping reviewers find the problems leads to rejections, review delays and longer appeals.
- If your app needs a login, put valid, working credentials in Play Console so reviewers can test it fully.
- Review usually takes seven days or less, but can occasionally take longer.
Google's page doesn't state a waiting period before you can apply again. It also doesn't list every reason for a rejection. If your application is turned down, read the message Google sent you in Play Console, because it's the only source that is about your app. Then keep the closed test running while you fix what people report, which Google also advises.
What to log during the 14 days
Keep one plain document, a text file or a spreadsheet. Update it a little each day instead of reconstructing it on day 14. The aim is to make every answer in the application something you can back up.
- Opted-in testers per day. Count people who opted in, not people you invited. Write down the number and the date. If it drops, find out why the same day.
- Every piece of feedback. Paste it in with the date, the source and what you did about it, including "nothing, because...". This is the raw material for "summary of feedback and how it was collected" and for "changes you made".
- Version codes you shipped to the closed track. Note each version code and what changed in it. A list like "build 7 fixed the login crash someone reported on day 3" is a true, specific answer.
- Crashes. Check Android vitals for crash rates and the pre-launch report for stability issues found on Google's test devices. Note what you found and fixed.
- What testers actually did. If a feature went untested, say so and ask someone to try it. Google asks whether testers used all the features.
Keep it honest. Don't pad the tester count, don't pay for installs and don't invent feedback. Google's questions are about real usage, and the answers are easiest to write when the test was real. Your closed track and tester list are explained in Google's help page on open, closed and internal tests.
Where TestSwap helps, and where it doesn't
TestSwap is a free site where app makers review each other's apps. You test someone's app, they test yours. Good test tasks matter here: see how to write a test task.
It can help with:
- Finding real people who open your app and leave written feedback. That feedback goes straight into your log.
- Getting specific reports on a feature nobody has touched yet, if your task names it.
It can't help with:
- Approval. Google decides, and TestSwap has no say in it and no insight into it.
- The app itself. It has to be ready and follow Play policy.
- The count. A TestSwap review is a text form on our site. It's not a Play opt-in. Your 12 testers must join your closed test and stay opted in for 14 continuous days. If you want a reviewer to be one of them, say so in your task and give them the opt-in link.
Checklist
- Closed test has 12+ opted-in testers, ideally a few more, for 14 days in a row.
- Daily opted-in count is written down.
- Feedback is saved, with what you changed because of it.
- Version codes and release notes for the closed track are listed.
- Android vitals and the pre-launch report are checked, and crashes fixed.
- The app follows Play policies, and login credentials are in Play Console if needed.
- You can say who the app is for, what value it gives and why you think it's ready.
- If turned down, you read Google's message, kept the test running and fixed what you found.
Try it
If you need real testers for your closed test, post your app on TestSwap with a test task that says exactly what to do. You get 3 credits to start, and reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).