What “rejected” means

App rejected · Update rejected · Rejection · Removal · Suspension · Enforcement Process

Sources:O2 Enforcement Process·O4 Publish your app· last-checked: 2026-11-09

What you typically see

  • Email and Play Console notice that a new app or an update was rejected after review.
  • Publishing / update status such as App rejected or Update rejected.
  • Instructions to fix policy issues and/or appeal if you believe the action was taken in error (O2).

What public docs say

Rejection (enforcement action) — O2

  • A new app or app update submitted for review will not be made available on Google Play.
  • If an update to an existing app is rejected, the previously published version remains available.
  • Rejections do not impact access to existing user installs, statistics, and ratings.
  • Rejections do not impact the standing of your Google Play Developer account.
  • Note (O2): Do not attempt to resubmit a rejected app until you’ve fixed all the policy violations.

Neighboring actions (brief) — O2

ActionSnapshot from O2
RemovalApp (including previous versions) removed from Play; store listing hidden until a compliant update; may block in-app purchases until approved; doesn’t immediately affect account standing; multiple removals may lead to suspension. Don’t republish until all violations are fixed.
SuspensionApp removed; can follow egregious/multiple violations or repeated rejections/removals; APK/bundle can’t be reused; counts as a strike; multiple strikes can terminate accounts.
Limited VisibilityDiscoverability restricted; still reachable via direct link; no account-standing impact from this state alone.
Limited RegionsDownload limited to certain regions; prior installs may keep working without updates.
Restricted Developer AccountCatalog removed; can’t publish until violations fixed; Console access retained.
Account TerminationCatalog removed; related accounts may be suspended; new accounts opened while terminated can also be terminated.

O2 also notes: notices may not list every violation; developers must fix issues and diligence the rest of the catalog. You are responsible for third-party code/SDK compliance.

Status labels — O4

  • Update rejected: One or more changes in your update are not compliant with Google Play policy or the Developer Distribution Agreement. You can fix and resubmit, or appeal.
  • App rejected: Same compliance idea, but only applies to apps still in Draft that you are attempting to publish for the first time (O4 distinguishes this from Update rejected).
  • Related app statuses include Draft (no Play presence yet, or rejected during review), Removed by Google, Suspended by Google, etc. (full table in O4).

What to fix

  1. Read the enforcement email and Console Policy status / publishing overview for the cited policy.
  2. Classify the action: Rejection vs Removal vs Suspension (O2) — the recovery path differs.
  3. Map email keywords to a reason page under /reasons/ (Data safety, Metadata, Policy, Other).
  4. Fix all listed policy violations in the app, store listing, and App content declarations before any new submission (O2 note).
  5. If the notice looks wrong, use Google’s appeal path described in the enforcement communication (O2) — this wiki does not replace that process.
  6. Resubmit only after fixes are saved and ready for review.

Before you resubmit

Related