Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google Play rejected my app update and I do not know why

Short answer

A rejected update does not touch your account standing, and Google says the version published before it stays available. Read the policy named in your Play Console notifications and email, fix it in every release track, deactivate the non-compliant bundles, and do not republish until the violation is fixed.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I got an email from Google Play that my update was not approved.
  • Play Console shows a policy problem I do not understand.
  • I resubmitted and the same problem came back.
  • My developer says the app is fine and Google is wrong.
  • A release date for a customer or campaign is close.

Why does this happen?

  1. The update broke a Developer Program Policy

    Google's enforcement page says to read the policy cited in the enforcement message, and to check your app against the other Developer Program Policies too, since further enforcement can follow additional violations.

  2. An older release is still active on another track

    Google says to update every release type, including production and the open, closed and internal test tracks, and to deactivate the non-compliant bundles. It warns that failing to deactivate them can cause your resubmission to fail.

  3. The app does not meet a store requirement

    Some rejections are about a technical rule, such as the required target API level or a declaration that must be completed, rather than about your content.

  4. A declaration or data form does not match the app

    Forms such as the advertising ID declaration must describe what the app really does. A mismatch between the form and the build can block a release.

What can I do about it today?

  1. Read the notification, not only the emailGoogle says to check your Play Console Notifications and email, which contain information about the policy your app violated.
  2. Remember what stays liveGoogle says the version published prior to the update will still be available on Google Play, and that a rejection does not affect the standing of your developer account.
  3. Do not republish the same bundleGoogle's guidance is not to republish a rejected app until the violation has been fixed.
  4. List every track that holds a bundleProduction, open, closed and internal testing. A forgotten test track is a common reason for a second rejection.
  5. Decide whether to fix or appealIf the policy was broken, fix and resubmit. If you believe it was not, Google allows one appeal per enforcement action, through the File an appeal link. Do not send repeated or abusive messages, which can make you ineligible for further email support.

When should I bring someone in?

  • The cited policy is about data, permissions or payments and you cannot judge what must change.
  • The same rejection comes back after a fix.
  • A removal warning has a countdown and the fix is not clear.

How do I handle it?

  1. Translate the policyI read the cited policy next to your app and tell you in plain words what Google is asking for.
  2. Check every track and declarationI look at all release tracks and the Play Console forms, so the same problem is not left behind on one of them.
  3. Fix, test and submit onceI make the change, test the build on a clean device and submit a new release that replaces the non-compliant bundles.
  4. Draft the appeal if one is justifiedIf the decision looks wrong, I write a short factual appeal for you to send. Google decides, and I cannot promise the outcome.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does a rejection put my account at risk?

Google says rejections do not affect the standing of your developer account. Repeated or egregious violations are a different matter, so do not ignore the message.

Is my current app still available to users?

Google says the version published prior to the update will still be available on Google Play.

How long will the next review take?

The Google page I used gives no timeline for rejections or appeals, so I cannot give one.

Is this the same as my app being removed?

No. A removal takes the published app down, and another page covers that. This page is about an update that was refused.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.