How to use it
- Copy the whole message: in App Store Connect, open the rejected submission; for Google Play, the email or Play Console → Policy status.
- Paste it. Each rejection it recognises gets its own card, in the order the message lists them.
- Fix each one, then copy the reply for the reviewer and, when the fix is in the code, the prompt for Lovable, Bolt or Cursor.
App Store rejections it explains
Google Play rejections it explains
| Policy | Rejection |
|---|---|
| Broken Functionality | Broken Functionality: it crashed or didn’t load |
| Spam and Minimum Functionality | Minimum Functionality: a webview of a website |
| User Data — privacy policy | Privacy policy: missing or invalid |
| Data safety | Data safety: the form doesn’t match the app |
| App access | App access: Google couldn’t sign in |
| User Data — account deletion | Account deletion: in the app and on the web |
| Photo and Video Permissions | Photo and video permissions: use the photo picker |
| Payments | Payments: digital goods must use Google Play Billing |
| Metadata | Metadata: the listing is misleading or stuffed with keywords |
| Production access | Production access refused: more testing needed |
Rejected or Metadata Rejected?
- Rejected — the app has to change. Fix the code, upload a new build, select it on the version, and resubmit.
- Metadata Rejected — only the listing is wrong: screenshots, description, URLs, review notes. Edit it in App Store Connect and resubmit the same build.
Google Play works by release: fix the app or the listing, then send the release for review again. If you think Google got it wrong, appeal from Policy status in Play Console.
Before you resubmit
- Install the exact build from TestFlight or internal testing on a real phone, delete it, reinstall it, and sign up as a new user — that is what reviewers do.
- Reply even when you upload a new build: what changed, and where the reviewer can see it.
- Wrapped web apps that fixed one rejection often get 4.2 next. Run the Guideline 4.2 self-audit first.
- Icon or screenshot complaints: the app icon generator and the screenshot size checker.
- Google refused production access after the closed test? The 12-tester countdown drafts better answers.
In CapWrapp
CapWrapp users have this explainer in every app’s Toolbox. Once the fix is pushed, CapWrapp builds the commit on GitHub’s Mac machines, uploads it to TestFlight and Google Play, and sends the build you pick back to review from the Releases page. Get started free.