The rejection patterns we see every day
After running thousands of closed tests, most rejections come down to a handful of repeatable mistakes. Good news: they’re all fixable.
1. Testers who aren’t real
Google has gotten very good at detecting fake accounts, duplicate devices and suspicious sign-up patterns. If your tester list looks automated, the review team will bounce it.
2. Testers who don’t engage
An opted-in tester who never opens the app counts against you. Google looks at usage signals, not just the checkbox.
3. Policy violations hiding in your app
- Misleading permission requests
- Content that violates Play’s deceptive-behaviour policy
- Broken or placeholder features in the build
How to fix a rejection
Read the exact reason in the Play Console, fix the specific issue, then re-apply on the same test — don’t start from scratch. Keep the 14-day timer running while you patch things up so you don’t lose progress.
Most fixes take under 48 hours. The expensive mistake is letting the 14-day window expire while you figure it out.