Google Play “More Testing Required”: Why Production Access Gets Rejected and How to Fix It

What Does “More Testing Required” Mean in Google Play Console?

You have built your Android app, recruited testers, completed your closed testing period, and applied for production access. But instead of getting approval, Google Play Console displays this message:

“More testing required to access Google Play production.”

This can be frustrating, especially for indie developers publishing their first app. However, this message does not necessarily mean your app has permanently failed review. It means Google has determined that additional testing is needed before your app can access production.

In this guide, we explain what the message means, why production access may be rejected, and what you can do to prepare a stronger application.

Understanding Google's 12 Testers and 14 Days Requirement

For personal developer accounts created after November 13, 2023, Google Play requires a closed test with at least 12 testers who remain opted in continuously for at least 14 days before the developer can apply for production access.

Meeting this minimum requirement allows you to apply; it does not guarantee approval. Google also asks questions about your testing process, app functionality, feedback, and production readiness.

Read the official requirements here: Google Play Console testing requirements.

Why Does Google Play Reject Production Access?

1. Testers Were Not Sufficiently Engaged

Recruiting 12 testers is an important starting point, but your testing process should also help demonstrate how the app works for real users. If testers join the test but do not meaningfully explore the app, you may have limited evidence about its usability and reliability.

How to improve:

• Give testers clear instructions about the features and user journeys to test.
• Ask them to explore important screens and complete realistic tasks.
• Encourage them to report crashes, errors, confusing screens, and usability problems.
• Keep the app available through the required testing period and confirm that testers remain opted in.

2. Testing Feedback Was Not Properly Reviewed

Testing is more valuable when developers collect feedback, review it, and use it to improve the app. Simply completing the calendar period without evaluating the app's quality can leave important problems undiscovered.

How to improve:

• Create a clear channel for receiving feedback, such as email or a tester group.
• Maintain a record of reported bugs and usability concerns.
• Prioritize important issues and fix them before production.
• Retest the affected features after making changes.

Public ratings and reviews should not be treated as a substitute for genuine testing. Focus on useful feedback and the quality of your testing process.

3. Production Access Answers Were Too Generic

When you apply for production access, Google asks about your closed test, app or game, and production readiness. Answers that are vague or do not reflect your actual testing experience may fail to explain how you evaluated the app.

How to improve: Explain who tested the app, which features they explored, how you collected feedback, what you learned, and what changes you made. Use specific, truthful details rather than copying generic answers from the internet.

4. Important Bugs or Usability Issues Remain

An app can complete closed testing and still have problems that affect the user experience. Crashes, broken navigation, incomplete features, login problems, or confusing onboarding can undermine production readiness.

How to improve:

• Test the main user journeys from start to finish.
• Check login, registration, navigation, network failures, and error states where relevant.
• Verify that key features work on supported devices and screen sizes.
• Review available crash reports and pre-launch reports.
• Provide valid review credentials if your app requires login.

What Should You Do After Receiving “More Testing Required”?

1. Read the rejection message carefully. Identify the specific feedback provided in Play Console or the notification email.
2. Review your tester participation. Confirm that at least 12 eligible testers have remained opted in continuously for the required period.
3. Continue meaningful testing. Give testers clear tasks and encourage them to explore the app's main features.
4. Collect and evaluate feedback. Record the problems reported and the steps taken to investigate them.
5. Improve the app where necessary. Fix important bugs and retest the affected functionality.
6. Prepare accurate application answers. Explain the testing process, lessons learned, changes made, and reasons you believe the app is ready.
7. Follow Google's next steps. Continue testing for any additional period requested and reapply when your app and testing evidence are ready.

Sample Answers for the Production Access Application

The following examples are templates, not guaranteed approval answers. Replace the bracketed sections with accurate information from your own test.

How did you recruit testers?

“We recruited testers through [your actual recruitment channels]. They joined our closed test using the Google Play opt-in link. We shared instructions explaining the main features to test and how to report issues.”

How did testers use your app?

“Testers evaluated [your app's main features] and completed tasks such as [actual user journeys]. We reviewed their feedback to understand usability issues and identify areas requiring improvement.”

What changes did you make based on testing?

“During testing, we identified [actual issues or observations]. We addressed these by [actual fixes or improvements] and retested the affected functionality. We also reviewed [other relevant checks] before preparing for production.”

Why is your app ready for production?

“We evaluated the main user journeys, reviewed the feedback collected during closed testing, and checked the app for important functional issues. Based on these results, we believe the app is ready for production because [specific evidence from your testing].”

Important: Do not claim that you collected feedback, fixed bugs, or tested specific features unless you actually did so.

Google Play Production Readiness Checklist

• At least 12 eligible testers remain opted in for the required continuous 14-day period.
• Testers receive clear instructions about what to test and how to report issues.
• The main app features and user journeys have been evaluated.
• Feedback has been reviewed and important issues have been addressed where necessary.
• Crashes, broken screens, login problems, and other critical issues have been checked.
• Application answers accurately describe the actual testing experience.
• The app complies with applicable Google Play policies.
• Any additional instructions from Google have been followed.

How PlayLaunch Helps Android Developers

Preparing for a Google Play launch involves more than finding testers and waiting 14 days. Developers also need a structured testing process, clear communication, useful feedback, and a reliable way to review app readiness.

PlayLaunch helps Android developers organize closed testing, coordinate testers, track testing progress, collect feedback, and prepare for a more structured production-readiness review.

Whether you are launching your first Android app or managing multiple app releases, a well-organized testing process can help you identify issues earlier and make better release decisions.

Explore PlayLaunch and prepare for your next app launch.

Frequently Asked Questions

Does completing 14 days guarantee production access?

No. The required closed-testing period makes you eligible to apply, but Google reviews your testing process and production-readiness answers before granting access.

Do testers need to provide public reviews?

Public ratings and reviews are not the same as closed-testing participation. Follow Google's testing guidance, collect useful feedback through an appropriate channel, and summarize the feedback when applying for production access.

Should I upload a new app version after rejection?

Upload an update when you have meaningful fixes or improvements to make. A new build by itself is not a universal guarantee of approval. Follow the feedback provided for your app.

Can I apply again after rejection?

You can follow the next steps provided in Play Console, continue testing as needed, address the identified concerns, and apply again when eligible.

Where can I find the official testing rules?

Visit the official Google Play Console testing requirements for the latest guidance.

Final Thoughts

The “More Testing Required” message is a signal to review your testing process, not simply to wait for more days to pass. Focus on genuine tester participation, useful feedback, app quality, and accurate production-access answers.

Prepare carefully, follow the specific guidance shown in your Play Console, and use testing to make your app more reliable before releasing it to real users.