BrightRevamp
Blog / Google Play policy

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

By Muhi Uddin Haider, Founder8 Oct 20263 min read

This post is about a rejected update: you submitted a new version and Google said no. Most rejections come from a short list of causes. Here are ten, with a quick check for each, so you can catch them before you submit.

A rejection only blocks the new version. Your live version stays online. If your live app has been removed or you have a warning with a deadline, read removal and suspension or the policy email plan instead.

The ten common reasons

  1. Target API level too low

    Updates must meet the current target level, which is API 36 for most apps since 31 August 2026. Check: targetSdk in the app's build.gradle. 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. Check: search the dependency report for billing. 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. Check: open the link from a phone that is not logged in. It must load, and it must name your app or company.

  4. Data safety form does not match the app

    The Data safety section must describe what the app and its SDKs really collect. Check: list every SDK (analytics, ads, crash reporting, login) and compare what each collects with what your form says. SDKs are the usual gap.

  5. Permissions you cannot justify

    Sensitive permissions such as background location, SMS, call log or all-files access are restricted. Check: the merged manifest of the release build. Remove what you do not need, or complete the permission declaration in Play Console.

  6. Misleading store listing

    The title, icon, screenshots and description must describe what the app really does. Check: remove claims you cannot prove, keywords stuffed into the title, and screenshots of features the app does not have.

  7. Crashes or broken core features

    An app that crashes on launch or does not do what it says fails the minimum functionality expectation. Check: install the release build on a current Android version, not only your old phone, and open every main screen.

  8. Payments outside Google Play Billing

    Digital goods and subscriptions sold inside an app generally have to use Google Play's billing system. Check: any in-app link to a website checkout for digital content, then read the payments policy for your case and region.

  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. Check: use the app for five minutes as a new user and note every ad and every place users can post.

  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. Check: every track in Play Console, not only production.

After a rejection: how to resubmit

  1. Find the reason. Open Policy status in Play Console and read the email. Both name the policy. Fix that, not a guess.
  2. Fix it in the code or the listing, then check the other nine reasons above while you are there.
  3. Build a new version with a higher version code and upload it.
  4. Clean up every track so no old bundle with the same problem stays active.
  5. Submit and wait for review. If you are sure the rejection was a mistake, you can appeal instead, but a clear message is usually faster to fix than to argue.

Frequently asked questions

Does a rejection affect my developer account?

Google's help pages say a rejected update does not affect your developer account standing, and your previous live version stays online.

How do I find out why my update was rejected?

Open 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 the official documentation on 8 Oct 2026. Rules change, so confirm the dates in your Play Console.