Troubleshooting App Store Rejections
Getting rejected is part of the iOS development lifecycle. It happens to beginners and major tech companies alike. This guide decodes the cryptic rejection messages and provides actionable steps to fix them and get your app approved.
Don't Panic
A rejection is not a ban. It is simply a request for changes. Most rejections are resolved with a simple fix or a polite clarification in the Resolution Center.
1 Using the Resolution Center
This is your direct line of communication with the Apple Review Team. It is located inside App Store Connect.
When to Reply
- Clarification: If the reviewer misunderstood a feature (e.g., "Where is the account deletion?" "It is in Settings > Account").
- Evidence: If they claim a feature is broken, but it works for you, upload a video of it working on a physical device.
- Commitment: If the issue is minor, sometimes you can promise to fix it in the next update (rare, but possible).
Best Practices
- Be Polite: Reviewers are human beings following a script. Being aggressive will not help your case.
- Be Specific: "I fixed it" is not enough. Say "I updated the Info.plist to include the specific usage string for the Camera."
- Attachments: Use screenshots and videos liberally to prove your point.
Decoding Rejection Codes
Guideline 2.1: App Completeness
FixableThe Issue: Your app crashes, has broken links, placeholder content ("Lorem Ipsum"), or features labeled "Coming Soon".
How to Fix:
- Remove any buttons that don't do anything yet.
- Ensure your backend is live and accessible from IPv6 networks.
- Provide a valid Demo Account in the review notes.
Guideline 2.3: Metadata
MarketingThe Issue: Your screenshots or description are misleading. Often, developers use "Concept Art" instead of actual app screenshots.
How to Fix:
- Ensure screenshots show the actual app UI.
- Remove claims you can't prove (e.g., "World's #1 App").
- Ensure the app name on the store matches the name installed on the device.
Guideline 4.1: Copycats & Spam
High SeverityThe Issue: You submitted multiple versions of the same app (e.g., "Guide for Game A", "Guide for Game B") or your app is a clone of a popular app.
How to Fix:
- Combine multiple apps into a single "Container App" with In-App Purchases to unlock content.
- Significantly change the UI so it doesn't look like a template.
Guideline 4.2: Minimum Functionality
DesignThe Issue: Your app is "not app-like enough." It might just be a repackaged website (Web View) or a simple marketing brochure.
How to Fix:
- Add native iOS features: Push Notifications, Core Location, Camera integration, or Offline Mode.
- Ensure the UX feels like an app, not a webpage.
Guideline 5.1.1: Data Privacy
LegalThe Issue: Requesting data without permission, missing Info.plist keys, or failing to provide account deletion.
How to Fix:
- Add
NSUsageDescriptionkeys to your plist explaining why you need the data. - Implement a self-serve "Delete Account" button in settings.
Appeals & Expedited Review
The App Review Board
If you genuinely believe your app was rejected in error and the resolution center isn't helping, you can file an appeal to the App Review Board.
Expedited Review
You can request a faster review (skipping the line) in specific emergencies.
- Critical Bug Fix: Fixing a crash affecting live users.
- Time-Sensitive Event: Your app is tied to a specific event (e.g., The Olympics) happening this weekend.
Do not abuse this. If you request it too often, Apple will stop granting it.