Production access rejected? What to fix

By the TestLancer team · Updated

Quick answer

The most common reasons are testers who opted in but barely used the app, too little evidence of real feedback and changes, vague application answers, or an app that doesn't look ready for users. Run a further closed test with engaged testers and daily tasks, fix what they find, keep notes, and reapply with specific answers.

Read Google's message carefully

Google's response usually points to what it wants to see more of — often more testing, more tester engagement, or better evidence that the app is ready. Start there. Don't guess, and don't reapply the same day with the same answers.

Common reasons and fixes

Likely reasonWhat to do
Testers didn't really use the appGive testers a short, specific task each day and collect check-ins
No sign of feedback or iterationShip updates during the test and log what changed and why
Vague answersName specific bugs, devices, features and fixes
App not readyFix crashes, broken flows, placeholder content and missing privacy details
Very thin appMake sure the app offers clear value to a real audience

Run a better second test

  1. Recruit 15–20 committed testers so the count stays above 12 — see why the clock resets.
  2. Plan one focused task per day across the 14 days.
  3. Ask for evidence: a screenshot of a screen reached, a short note on what happened.
  4. Collect bug reports in a consistent format — see how to write a good bug report.
  5. Release at least a few improved builds during the test.
  6. Keep a log you can quote in your application.

Rewrite your answers

Use your log to answer each question concretely. Mention the number of testers, the range of devices, the main issues found and the changes you shipped. Describe your target users honestly. Our guide to applying for production access has more detail.

Get help running the test

If organising engaged testers is the hard part, our Google Play Closed Testing service provides eligible testers on real Android devices, daily check-ins, bug reports and a summary report. We provide genuine testing and feedback; approval remains Google's decision.

Frequently asked questions

How soon can I reapply?

Play Console shows when you can apply again. Use the time to run a stronger test rather than reapplying immediately.

Do I need new testers?

Not necessarily. You can keep engaged testers from the first round and add more. What matters is genuine, continuous participation.

Can I appeal instead?

Follow the options Google gives in its response. In most cases the practical path is to improve testing and reapply.

For developers & businesses

Get your product tested by real users.

Set up a campaign with your requirements and receive structured feedback and evidence from eligible testers.

For testers & freelancers

Test, freelance and earn.

One free account for app testing and small freelance tasks. Earn approved rewards for genuine work.

Join as Tester & Freelancer