5 Common Reasons Google Play Rejects Apps (And How to Fix Them)

Why Apps Get Rejected

Google Play reviews every app submission before it reaches users. In 2025, Google rejected over 2.28 million app submissions for policy violations alone. Based on our experience handling 500+ submissions, we have identified the five most common rejection reasons and how to avoid them.

1. Developer Program Policy Violations (35% of rejections)

The most common rejection category. Google's policies cover everything from ads to user data handling.

Most Frequent Policy Violations

• Deceptive behavior — App functionality does not match the store listing description
• Intellectual property — Using trademarked names, logos, or copyrighted content without permission
• Restricted content — Gambling, adult content, or regulated substances without proper classification
• Ads policy — Interstitial ads that cannot be closed, deceptive ad placement, or ads in notifications
• Permissions abuse — Requesting permissions that are not necessary for your app's core functionality

How to Fix

Read the specific policy cited in your rejection email. Google always references the exact policy section. Remove or modify the offending content, then resubmit with a note explaining what you changed.

2. Store Listing Metadata Issues (25% of rejections)

Your store listing is the first thing Google reviews, and many apps fail at this stage.

Common Metadata Problems

• Misleading descriptions — Claiming features your app does not actually have
• Keyword stuffing — Repeating keywords unnaturally in title or description
• Inappropriate screenshots — Screenshots showing content not in the app, or from a different app
• Icon violations — Using Google Play or Android branding in your app icon
• Impersonation — Title or icon too similar to an existing popular app

How to Fix

Ensure every claim in your listing is accurate and verifiable within the app. Use real screenshots from your actual app. Follow Google Play screenshot guidelines and ASO best practices.

3. App Functionality Problems (20% of rejections)

Google tests your app on real devices. Crashes, ANRs, and broken features trigger automatic rejection.

What Triggers This Rejection

• Crash on launch — App crashes within the first 30 seconds
• Core feature failure — Primary functionality does not work as described
• Login failures — Unable to create account or log in during review
• Excessive loading — Blank screens or infinite loading states
• Broken deep links — Links within the app leading to 404 or error pages

How to Fix

Test your app on at least 5 different Android devices before submission. Use Firebase Crashlytics to catch crashes early. If your app requires login, provide demo credentials in the review notes.

4. Data Safety & Privacy Issues (12% of rejections)

Since the Data Safety section became mandatory, incomplete or inaccurate declarations are a major rejection cause.

Common Issues

• Data Safety form does not match actual data collection
• Missing privacy policy (required if you collect any personal data)
• Privacy policy URL returns 404 or is not accessible
• Collecting data not declared in the Data Safety form
• Using third-party SDKs that collect data without declaring it

How to Fix

Audit every SDK in your app for data collection. Check Firebase, analytics, ad SDKs, and crash reporting tools. Update your Data Safety form to match reality. See our Data Safety form guide.

5. Content Rating Errors (8% of rejections)

The IARC questionnaire must be completed accurately. Incorrect answers lead to wrong age ratings and rejection.

Common Mistakes

• Under-rating violence or mature content in your app
• Not accounting for user-generated content (UGC)
• Forgetting that ads can contain mature content
• Marking your app as "no interactive elements" when it has social features

How to Fix

Re-take the IARC questionnaire carefully. When in doubt, rate higher rather than lower — a higher rating rarely causes rejection, but an inappropriately low rating always does. See our IARC content rating guide.

Prevention Checklist

Before every submission, verify:

1. All store listing claims match actual app functionality
2. App does not crash on launch and core features work
3. Data Safety form matches actual data collection (including all SDKs)
4. Privacy policy is accessible and up to date
5. IARC questionnaire is accurate
6. No trademarked content used without permission
7. All permissions are necessary and justified
8. Screenshots are from the actual app
9. Test credentials provided if login is required
10. App tested on 5+ device configurations