A rejection after completing closed testing is common enough that it's one of the most active discussion topics among developers right now — and it's rarely a dead end. The rejection message is usually short, but the fix is almost always findable if you review the right five things before you reapply.
On this page
Start with what Google actually told you
Check Play Console for any specific notes attached to the rejection, not just the headline message. The wording is often generic ("more testing required"), but occasionally there's more context worth reading closely before you change anything.
Review these five areas
- Tester engagement pattern across the full 14 days — not just at the start.
- Feedback you can point to: specific bugs found, specific changes made.
- Whether your production questionnaire answers actually matched your testing activity.
- App stability — crash-free sessions, no obvious broken flows.
- Whether your tester count stayed at or above 12 for the entire period — see why a tester might not count.
Run a focused second test, not just a repeat
Repeating the exact same process and hoping for a different result rarely works. Identify which of the five areas above was weakest, and run your next 14-day cycle specifically to fix that — more consistent daily engagement, a documented feedback trail, or a more stable build.
What not to do
- Don't submit fabricated feedback or engagement — it's a policy risk, not a shortcut.
- Don't assume a specific number of days or sessions guarantees approval; Google hasn't published a threshold beyond the 12-tester, 14-day minimum.
- Don't reuse a vague, generic questionnaire answer on a second attempt — if it didn't work once, it won't read better the second time.
Need help with the second round?
If you've been rejected, the next 14-day cycle has to fix whichever of the five areas above was weakest. That's what our service for rejected apps is built for:
- A fresh 14-day cycle with real Android testers who open your app every day.
- A written QA report of what testers actually found, so you have specific feedback to cite.
- Help drafting your production questionnaire answers from your real testing activity, with no invented details.
- Direct communication with me from setup through your production application.
Free to start, pay after testers join
Enrollment is free and needs no card. You pay a flat $25, with no hidden fees, and only once 12 testers show as opted in to your closed test. If our testing is the cause of a rejection, you get a refund plus a free re-test. No one can guarantee Google's decision, so we don't.
Frequently asked questions
Can I reuse the same testers for a second attempt?
Yes, there's no published rule against it. What matters is that the testing activity is genuine and reflects real engagement across the full 14 days.
How long should the second testing round run?
Google's minimum is the same 14 continuous days regardless of attempt number. Focus on the quality of engagement and feedback during that period rather than extending it further.
What should I change before reapplying?
Whichever of the five review areas was weakest for you — commonly engagement consistency, specificity of feedback, or how well your questionnaire answers matched what actually happened during testing.
Is there a limit to how many times I can reapply?
Google doesn't publish a hard limit on reapplication attempts. Each cycle still needs to independently meet the 12-tester, 14-day requirement.
Does Google explain exactly why an app was rejected?
Not always in detail. Messages are often generic, which is why reviewing your own testing activity against the five areas above is the most reliable diagnostic available.
Official sources