# Google Play "More testing required" for production access: what the email means and how to re-apply (2026)

> Google Play said more testing is required for production access? Decode the testers-not-engaged email, fix your closed test and rewrite the questionnaire answers.

Canonical: https://makeyourapp.live/blog/google-play-more-testing-required-production-access-fix
Last updated: 2026-11-02

By [Yagyesh Bobde](https://www.bobdeyagyesh.in) · Store submission · Published Nov 2, 2026 · 7 min read

Got the "More testing required to access Google Play production" email? Learn what each reason means, rewrite your questionnaire answers and re-apply after one well-run extra 14-day test instead of several.

## Short answer

"More testing required to access Google Play production" means Google reviewed your Apply for production request and decided your closed test didn't show enough real use. Common reasons are fewer than 12 opted-in testers, low engagement, no updates made in response to feedback, or thin questionnaire answers. To fix it, keep the closed test running, ship updates based on tester feedback, collect evidence for another 14 consecutive days, then re-apply with specific answers.

## Key takeaways

- Personal Play Console accounts created after November 13, 2023 need a closed test with at least 12 testers opted in continuously for 14 days before they can apply for production.
- Google says applications can fail for "fewer than 12 opted-in testers or insufficient tester engagement during the testing period"; installs alone are not engagement.
- The rejection email asks you to test "for an additional 14 days with real testers", so keep the current closed test running and don't let testers opt out.
- The questionnaire asks what testers used, what feedback they gave, how you collected it and what you changed. Answer with names of features, counts and version numbers.
- Google says the production access review usually takes seven days or less, and the account owner is notified by email.

The Google Play "More testing required to access Google Play production" email means Google turned down your production access application. It is not a policy strike and it does not suspend your app. It does cost you time: you need another 14-day block of closed testing before you re-apply. This guide decodes each reason in the email, lists what to change during the extra 14 days, and shows how to rewrite the questionnaire so your second application is your last. If you haven't started a closed test yet, begin with our [12 testers, 14 days test plan](https://makeyourapp.live/blog/google-play-closed-testing-12-testers-test-plan).

## What does "More testing required to access Google Play production" mean?

It means a Google reviewer read your Apply for production request and decided your closed test hadn't produced enough evidence that the app is ready for the public. Production and pre-registration stay locked until you run more testing and apply again.

As of November 2026, Google's [app testing requirements](https://support.google.com/googleplay/android-developer/answer/14151465) apply to personal developer accounts created after November 13, 2023. Those accounts must run "a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days." Meeting those numbers only lets you apply. The application itself is reviewed, and Google names two reasons you may need more testing: "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period." Google says the review "usually takes seven days or less, but can occasionally take longer," and the account owner gets the decision by email.

## What does each reason in the rejection email mean?

Each line in the email points to a specific gap: testers who didn't really use the app, a test with no visible changes in response to feedback, or questionnaire answers too vague to judge. The email can list one, two or all three reasons.

Developers who have posted the email publicly quote the same reasons: "Testers were not engaged with your app during your closed test", "You didn't follow testing best practices, which may include gathering and acting on user feedback through updates to your app", and answers about the app, closed test or production readiness that were "incomplete or insufficient". The closing instruction is: "Before applying again, test your app using closed testing for an additional 14 days with real testers." Google doesn't publish how it measures engagement, so the table maps each reason to the matching text on Google's own help page and to a fix.

| Reason in the email | What Google's help page asks for | Fix during the next 14 days |
| --- | --- | --- |
| Testers were not engaged | "Whether testers used all available app features" and whether usage matched expected production behavior | Give each tester a short task list covering every main feature, and check in on days 3, 7 and 11 |
| Didn't follow testing best practices | Fix bugs during testing, give testers "a clear way to send feedback", consider a pre-launch report | Ship at least two closed-track releases that respond to named feedback, with release notes |
| Answers incomplete or insufficient | Summarize feedback, how it was collected, what changed and how you judged readiness | Keep a dated feedback log so every answer can cite features, counts and versions |
| Fewer than 12 opted-in testers | 12 testers opted in for 14 consecutive days; opting out and back in restarts the streak | Recruit 15 to 20 testers so a few dropouts don't sink the count |

## What should you do right after the rejection?

Keep the closed test running, tell your testers to stay opted in, and ship a new closed-track build within a few days. Google's page says that if you aren't approved, "you may need to continue running your closed test," so tearing it down and starting a new one throws away your tester base.

1. Don't remove the closed track or your tester list. Google warns that "If a tester opts out and opts back in later, the 14 days must be consecutive," so any tester who leaves now restarts their own clock.
2. Message every tester. Explain that the test continues for 14 more days, that they must stay opted in, and what you want them to try this round.
3. Check your tester count in Play Console. Replace anyone who never installed the app with people who will actually use it. Friends who install and never open the app are the usual cause of the "not engaged" reason.
4. Set up one feedback channel. Google suggests a group chat; a shared form also works. Whatever you pick, save every message with a date.
5. Write a task list that covers each main feature: sign up, the core action, settings, purchases (with license testers if the app has billing) and any offline or notification flows.
6. Ship a closed-track update within the first week that fixes something a tester reported, and name the fix in the release notes. Plan a second update before day 14.
7. Run the pre-launch report and fix the crashes and accessibility warnings it finds.
8. Before you re-apply, check that your content rating, target audience and Data safety form are accurate. If the app needs a login, include "valid, working login credentials" as Google's page asks.

> **Don't pay for clicks:** A tester service that only provides opt-ins won't give you the feedback, changes or story the questionnaire asks about. Two of the developers in the cases below used outside testers, then had nothing specific to write and were sent back for another 14 days.

If your app also needs a target SDK bump before it can go live, do it inside the same window. Our [target API level 36 guide](https://makeyourapp.live/blog/target-api-level-36-google-play-extension-fix) covers the November 1, 2026 deadline.

## How do you rewrite the production access questionnaire answers?

Replace general statements with specifics: which features testers used, how many reports came in, how you collected them, which version fixed what, and what evidence showed the app was stable. Every answer should be something only a developer who ran a real test could write.

You open the form from the **Dashboard** in Play Console with **Apply for production**. It has three parts: your closed test, your app, and your production readiness. Progress is lost if you leave a part before clicking Next, so draft your answers in a document first. One developer on itch.io reported "a 300 character limit to each response," which is another reason to draft and trim ahead of time. The answers in Part 2 aren't shown publicly and don't affect your app's visibility.

Worked example for a hypothetical habit-tracker app. The weak answers are typical of applications that come back with "incomplete or insufficient":

| Question (Google's wording) | Weak answer | Rewritten answer |
| --- | --- | --- |
| Did testers use all available features? | Yes, testers used the app. | 15 testers created habits, logged streaks and changed reminders. Only 4 tried CSV export, so we added a prompt to it in v1.0.3. |
| "Summarize the feedback received from testers and describe how feedback was collected." | Feedback was positive. | 22 reports via a Telegram group and Google Form: 9 bugs (reminders missed on Android 14), 8 UX notes (dark-mode contrast), 5 feature requests. |
| "Describe any changes made to your app or game based on what you learned from your closed test." | Fixed some bugs. | Fixed the reminder bug with exact alarms (v1.0.2), raised button contrast (v1.0.3), added onboarding skip (v1.0.4). |
| "Describe how you determined that your app or game was ready for production." | We tested it a lot. | No crashes in the pre-launch report on v1.0.4, all 9 bugs closed, and testers confirmed reminders on Pixel and Samsung devices. |
| "Specify the target audience for your app or game. Be as specific as possible." | Everyone. | Adults building daily routines, such as students and remote workers, who want offline habit tracking without an account. |

## What have other developers reported after a "more testing" rejection?

The public reports share a pattern: testers who opted in but never sent feedback led to rejection, while a small group that sent feedback and saw the app change was approved. Tester count mattered less than evidence of use.

- On the [MIT App Inventor community](https://community.appinventor.mit.edu/t/googles-20-testers-requirement-now-only-12-14-testers-jun-2025/100767?page=3), developer shigeki_suzuki reported in July 2024 that their app Season Clock reached 20 testers for 14 days through a tester-exchange app, then received "More testing required to access Google Play production" with "Testers were not engaged with your app during your closed test." They wrote that they didn't know who the testers were and had received no feedback, so they couldn't describe how testing went or what changed. They had to repeat the test.
- On the [Adalo forum](https://forum.adalo.com/t/how-to-get-ready-for-play-store-production/49021), user siang32195 reported the same "More testing required" message in August 2024 after using recruited testers. They asked how to verify that testers had actually used the app. The reply suggested time-tracking tools or a written report listing the test scenarios each tester covered. The thread doesn't say whether the second application succeeded.
- A solo game developer writing on [itch.io](https://itch.io/blog/1101760/making-the-dream-work-part-5.amp) had "barely 12 testers" but wrote that they had "made several updates to the game" and "recorded everything I could from my interactions with my testers." They used that record in the application and reported: "Within 36 hours of posting the application, I was granted Production Access."

The comparison: 20 testers with no feedback trail were rejected, while 12 testers with a documented trail of feedback and updates were approved. Re-apply when your notes can answer every questionnaire field with specifics, not as soon as the day count reaches 14.

## When should you click Apply for production again?

Re-apply once at least 12 testers have been opted in for 14 more consecutive days and you have shipped feedback-driven updates during that time. Google's page doesn't mention a waiting period, but applying with the same evidence is likely to get the same answer.

- At least 12 testers opted in, with no opt-out gaps, for 14 more consecutive days (aim for 15 or more as a buffer)
- At least two closed-track releases since the rejection, each with release notes naming a tester-reported fix
- A dated feedback log with counts by type (bugs, UX, requests) and how each item was collected
- Testers who used every main feature, including login, purchases and notifications where relevant
- A pre-launch report with no unresolved crashes
- Accurate content rating, target audience and Data safety form, plus working reviewer login credentials
- Questionnaire answers drafted in a document, with features, counts and version numbers

Google's page also warns that "Submitting non-compliant apps expecting reviewers to identify issues leads to rejections, review delays, and lengthier appeal processes," so fix any policy problems before you apply, not after. If you'd rather hand the Play Console setup, closed test plan and application to someone else, our [App Store submission service](https://makeyourapp.live/services/app-store-submission) covers both stores for $599. Developer account fees are separate.

## Frequently asked questions

### How long does Google Play take to review a production access application?

Google says the production access review usually takes seven days or less, but it can occasionally take longer. The account owner gets the decision by email. Some developers report faster approvals: one solo game developer on itch.io was approved within 36 hours. Plan around the full seven days, and keep your closed test running while you wait so that a rejection doesn't also reset your testers' streaks.

### Do I have to restart the 14 days after production access is rejected?

The rejection email asks you to test "for an additional 14 days with real testers," and Google's help page says you may need to continue running your closed test. Keep the existing closed track and tester list rather than creating a new one. A tester who opts out and back in has to complete 14 new consecutive days, so ask everyone to stay opted in.

### Do paid tester services work for Google Play production access?

They can supply 12 opt-ins, but opt-ins alone don't answer the questionnaire. Google asks whether testers used all features, what feedback they gave, how it was collected and what you changed. Developers who used testers they never heard from have publicly reported "Testers were not engaged" rejections. If you use any outside testers, make sure they send real feedback through a channel you can document.

### Can I appeal a "More testing required" decision on Google Play?

Google's testing requirements page doesn't describe an appeal for this decision. The guidance is to continue closed testing and apply again. The more productive route is to run another 14 days with engaged testers, ship updates in response to their feedback, and resubmit with specific questionnaire answers. Fix any policy issues before you apply, because Google warns that non-compliant apps lead to rejections and delays.

### Does the 12 testers rule apply to organization developer accounts?

No. As of November 2026, Google's app testing requirements apply to personal developer accounts created after November 13, 2023. Those accounts need a closed test with at least 12 testers opted in continuously for 14 days before they can apply for production. Organization accounts and personal accounts created before that date aren't covered by this rule, although testing before launch is still worthwhile.

## Sources & further reading

- [App testing requirements for new personal developer accounts - Play Console Help](https://support.google.com/googleplay/android-developer/answer/14151465) (checked Nov 2, 2026)
- [Set up an open, closed, or internal test - Play Console Help](https://support.google.com/googleplay/android-developer/answer/9845334) (checked Nov 2, 2026)
- [Google's 20 testers requirement (now only 12/14 testers) - MIT App Inventor Community](https://community.appinventor.mit.edu/t/googles-20-testers-requirement-now-only-12-14-testers-jun-2025/100767?page=3) (checked Nov 2, 2026)
- [How to get ready for play store production? - Adalo Forum](https://forum.adalo.com/t/how-to-get-ready-for-play-store-production/49021) (checked Nov 2, 2026)
- [Making the Dream Work - Part 5 - itch.io](https://itch.io/blog/1101760/making-the-dream-work-part-5.amp) (checked Nov 2, 2026)

## Related

- [Google Play closed testing: 12 testers, 14 days, and a test plan that gets production access (2026)](https://makeyourapp.live/blog/google-play-closed-testing-12-testers-test-plan)
- [App Store submission checklist (2026): from Xcode 26 build to Submit for Review](https://makeyourapp.live/blog/app-store-submission-checklist)
- [All posts](https://makeyourapp.live/blog)