App Rejected on Google Play?
Every rejection has a specific cause — and a specific fix. Find your rejection type below and follow the recovery steps.
More Testing Required
Google believes your 14-day closed testing did not meet the standard. This can happen even if Play Console showed 14 days — usually because tester engagement signals were too low or your questionnaire answers were insufficient.
Fix
Run a second 14-day window with a fresh tester pool. Ask testers to actively use the app, not just install it. Push one update mid-window. Then resubmit with detailed, specific questionnaire answers referencing actual tester interactions.
Insufficient Questionnaire Answers
Production access questionnaire answers that are too brief, generic, or vague are a common rejection trigger. Each answer should be at least 250 characters and reference specific testing events.
Fix
Rewrite every questionnaire answer to include: your exact tester count, how you recruited them, which features testers used, specific feedback or bugs reported, and the changes you made in response. Generic answers ('testers found it worked well') are not sufficient.
Policy Violation
Your app or store listing violates a specific Google Play Developer Policy. The rejection email references the exact policy section.
Fix
Read the policy reference in the rejection email. Fix the specific violation in the app or listing. Do not resubmit until the violation is fully resolved. Appeals without corresponding fixes are rejected automatically.
Incomplete Store Listing
Missing or incomplete store listing elements — missing screenshots, incomplete description, privacy policy URL error, or unfinished content rating.
Fix
Complete every required store listing field. Screenshots must show the real app. The privacy policy URL must be live and functional. Recheck the content rating and data safety sections for any incomplete declarations.
Permission Issues
Your app requests permissions that are not justified by its core function — particularly SMS, call log, location in background, or microphone for apps without clear justification.
Fix
Remove permissions not required by your app's core function from AndroidManifest.xml. If a permission is required, add a declaration in Play Console explaining why. Rebuild and upload the corrected version.
Developer Account Issue
Your account has an unresolved policy strike, pending identity verification, or a previous app that was removed for violations. Production access can be blocked at the account level.
Fix
Check Play Console notifications for account-level alerts. If identity verification is pending, complete it. If there is a policy strike, resolve it through the Play Console appeal process. Do not reapply until account issues are cleared.
Related Guides
Need to redo closed testing?
If your rejection requires a new 14-day testing window, we can get you the testers immediately — with a participation log you can use in the questionnaire.
Start the Fix →