Decode Apple's rejection message, map the guideline number to a concrete fix, reply in Resolution Center, and get back in the review queue.
Apple rejected my app. Tell me what they mean and help me fix it
How it works
- Read the rejection in App Store Connect: Vovy opens the message in App Review and pulls out the guideline number, like 4.2 Minimum Functionality or 5.1.1 Data Collection.
- Translate the guideline: A card explains what Apple wants in plain English, what usually triggers it, and whether a reply alone can fix it or code must change.
- Make the fix in your code: If code must change, like adding account deletion or removing a broken screen, Vovy types the request into Cursor or Claude Code and shows you the diff.
- Build and upload a new version: Vovy bumps the build number and runs the EAS build and submit commands. Uploading to Apple is publishing, so it asks first.
- Reply to App Review: Vovy drafts a short, polite reply that says exactly what changed and where to find it, then resubmits once you approve.
What you provide
- Access to App Store Connect
- Your app's code
- Your Expo account
What you get
- A plain-English read of the rejection
- The fix, in code or in your listing
- A resubmitted build with a clear reply
FAQ
Is a rejection bad for my account?
No. Rejections are routine, especially on a first submission. Just fix the issue and resubmit.
What if I think the reviewer is wrong?
Reply in App Review with specifics. If that fails, you can file an appeal with the App Review Board.
What are the most common rejections?
Crashes or broken features, missing demo login, apps that feel like a thin website wrapper, and missing in-app account deletion.
Related tasks
All tasks