BrightRevamp
Blog / Google Play policy

Why Google Play Rejects Android Apps: 10 Common Reasons and Fixes

BrightRevamp Team8 Oct 20263 min read

Most rejections come from a short list of causes. Here are ten, with the fix for each. Check them in order, because the first two are by far the most common for older apps.

  1. Target API level too low

    New updates must meet the current target level. Raise targetSdk and test the app. See our target API guide.

  2. Outdated Play Billing Library

    If your app, or an SDK inside it, includes the billing library, it must be on a version Google still accepts. See Play Billing Library 8.

  3. Missing or wrong privacy policy

    Apps that handle personal or sensitive data need a privacy policy at a public URL, linked in Play Console and inside the app.

  4. Data safety form does not match the app

    The Data safety section must describe what the app and its SDKs really collect. Check analytics, ads and crash-reporting SDKs, which collect data you may have forgotten.

  5. Permissions you cannot justify

    Sensitive permissions such as background location, SMS, call log or all-files access are restricted. Remove what you do not need, or complete the permission declaration.

  6. Misleading store listing

    The title, icon, screenshots and description must describe what the app really does. Remove claims, keywords stuffed into the title, and screenshots that do not match the app.

  7. Crashes or broken core features

    An app that crashes on launch or does not do what it says fails the minimum functionality expectation. Test on a recent Android version, not only your old phone.

  8. Payments outside Google Play Billing

    Digital goods and subscriptions sold inside an app generally have to use Google Play's billing system. Check the payments policy for your case.

  9. Ads and user-generated content problems

    Ads that mislead, cover the interface or appear outside the app are not allowed. Apps with user content need moderation and a way to report it.

  10. Old bundles left on other tracks

    After a fix, an old non-compliant bundle still active on an internal or closed testing track can make the resubmission fail. Update every track.

Read the message first. Play Console and the email name the exact policy. Fix that, not a guess. See what to do after a policy violation email.

Frequently asked questions

Does a rejection affect my developer account?

A rejected update does not affect your account standing, and your previous live version stays online.

How do I find out why my update was rejected?

Open Notifications and Policy status in Play Console, and read the email. Both name the policy that was violated.

Can I appeal a rejection?

Yes, but fix the issue and resubmit first if the message is clear. Appeal only when you believe the decision was a mistake.

Keep reading

Rejected and not sure why?

BrightRevamp updates older native Android apps (Java and Kotlin) to Google Play's current rules. Same app, same design, same features.

Email us about your app

Sources

Checked against Google's own documentation on 8 Oct 2026. Rules change, so confirm the dates in your Play Console.