After rejection: fix → evidence → resubmit

When to use

After any Play rejection email or Console notice that a new app or update was rejected (see What “rejected” means).

O2 states: Do not attempt to resubmit a rejected app until you’ve fixed all the policy violations.

Checklist

1. Capture the notice

• Save the enforcement / rejection email (date, policy name, appeal link if any)
• Note Console status: App rejected (first publish from Draft) vs Update rejected (O4)
• Confirm the action is Rejection (not Removal / Suspension) using enforcement glossary

2. Map keywords → wiki reason

• Copy exact phrases from the email / Policy status page
• Open the matching category under /reasons/
• Open the specific reason entry when available (e.g. Data safety, privacy policy URL, permissions)

3. Fix before any new upload

• Address every cited policy issue in the app binary, store listing, and App content forms
• Spot-check the rest of the app/catalog for the same class of issue (O2: notices may not list every violation)
• If third-party SDKs are involved, confirm their behavior is reflected in declarations (O2 responsibility note)

4. Evidence pack

• Screenshots of corrected Console declarations / listing fields
• Links to updated privacy policy or Help docs you relied on
• Build / version code you will submit
• Working reviewer credentials if the app requires sign-in (see also O1 / O3 readiness notes on related pages)

5. Resubmit deliberately

• Changes saved in Play Console
• Publishing overview: send changes for review when ready (managed publishing: only when you intend to)
• Do not resubmit “to see what happens” while violations remain (O2)
• If you believe the action was wrong, use the appeal instructions in the official notice instead of blind resubmits

6. After you send

• Watch account-owner email and Policy status
• Keep the evidence pack until the review completes
• If rejected again, treat it as a new pass through this checklist — do not assume the same fix applied

Related

• What “rejected” means
• Rejection reasons hub
• Invalid Data safety form
• All checklists
• Pre-production checklist (shell)