Pushbuild

How to resolve a Google Play rejection and resubmit

Google Play explains rejections in Play Console and by email, and names the policy. The steps after that matter: an update has to replace the rejected version on every track, or the resubmission can fail again.

At a glance

  1. 1. Read the Policy status pageIn Play Console, open the app and go to Policy status.
  2. 2. New personal account? Check the testing ruleGoogle requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers who stay opted in for 14 days in a row before applying for production.
  3. 3. Common reasonsData safety form does not match what the app or its SDKs collect
  4. 4. Fix and resubmit the right wayChange the app, then upload the new bundle to every track that had the old one, not only production.
  5. 5. Appeal if the decision is wrongIf you believe Google made a mistake, appeal from the Policy status page with a clear explanation.

1. Read the Policy status page

In Play Console, open the app and go to Policy status. It shows whether a release was rejected, the app was removed, or it was suspended. Google says a rejected update leaves the last published version live, a removed app stays off Play until a compliant update is published, and a suspended app needs a successful appeal.

2. New personal account? Check the testing rule

Google requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers who stay opted in for 14 days in a row before applying for production. Testers who leave early do not count, and Google says review of the application usually takes up to 7 days.

3. Common reasons

  • Data safety form does not match what the app or its SDKs collect
  • Missing or broken privacy policy link
  • Login needed but no test account given in App access
  • Permissions the app does not clearly need, such as SMS, call log or background location
  • Misleading store listing, icon or screenshots
  • Target API level below Google's current requirement

4. Fix and resubmit the right way

Change the app, then upload the new bundle to every track that had the old one, not only production. In the new release, leave the non-compliant bundle under Not included, then send the changes for review. Google warns that a resubmission can fail if the old bundle is still active on any track.

5. Appeal if the decision is wrong

If you believe Google made a mistake, appeal from the Policy status page with a clear explanation. Google allows one appeal per enforcement and says a reply can take up to 7 days.

Updated 2026-10-29. General guidance, not advice for your situation; we scope each project in writing before any work starts.

Want us to handle it?

We can read the rejection, make the changes, write the review notes and resubmit, or set up your developer accounts from the start.

Get help with this

Questions people ask first

Can I just upload a new version?

Only after fixing the cause, and only if the old bundle is removed from every track. Otherwise it can be rejected again.

Why was my update rejected when the app was live before?

Policies and target API levels change, and each update is checked against the current rules.

Can I pay for testers?

Google's community guidance warns that paid tester groups are not recognised testing services. Use real users: staff, customers and friends.

Will a rejection get my account banned?

A rejection does not. Repeated serious violations can lead to account action, so fix the cause before resubmitting.

Tell us what you need built.

Tell us the process and the tools involved, or call. We reply with questions or a written scope.

hello@pushbuild.com

(617) 299-8887