App rejected by Google Play? Common reasons and how to fix them

A rejection email from Google Play can be vague and stressful — but most rejections are not mysterious. They cluster into a few common categories. Here is how to read the message and fix the real problem.

1. Policy violations

The biggest bucket. Common triggers:

• Permissions your app requests but does not clearly need (especially sensitive ones like SMS or location).
• Privacy policy missing, or not matching the data you actually collect.
• Misleading content — screenshots or descriptions that do not match the app.

Fix: request only the permissions you use, publish an accurate privacy policy, and make your listing honest.

2. Broken or crashing builds

If reviewers hit a crash or a feature that does not work, you are out. Fix: test on a range of real devices and Android versions before submitting. (This is exactly what a tester feedback cycle surfaces.)

3. Metadata and listing issues

• Keyword-stuffed or misleading titles.
• Screenshots with excessive promotional text or wrong aspect ratios.
• Incorrect content rating.

Fix: keep the listing clean and accurate, and complete the content-rating questionnaire truthfully.

4. Incomplete account or test requirements

For new personal accounts, not finishing the production-access requirements can block you. Fix: complete the 14-day closed test first.

Read the rejection carefully — Google usually names the policy. The fix is almost always "make the app and listing match reality."

How to appeal

If you believe it was a mistake, use the appeal link in the email. Be concise: state what you changed and why it now complies. Fix first, appeal second — appealing without changing anything rarely works.

Prevent it next time

Most rejections are caught by real testing. A stable build, honest listing, and a completed test cycle clear the vast majority of issues before a reviewer ever sees them.