What an App Store rejection means
An App Store rejection is a decision by App Review that your submission doesn’t meet one or more of the App Store Review Guidelines. It is not a ban. You fix the issue, reply and submit again.
The message from Apple names the guideline, such as 4.2 or 5.1.1, and often includes screenshots or steps. Read it in full before you change any code, because the guideline number tells you what kind of fix Apple expects.
The most common App Store review guidelines behind rejections
These guidelines come up often, especially on a first submission.
| Guideline | What Apple flags | How to fix it |
|---|---|---|
| 2.1 App Completeness | Crashes, placeholder text, broken links, no demo account, backend turned off | Test on a device, include a working demo account and keep the backend live during review |
| 2.3 Accurate Metadata | Screenshots, description or privacy information that don’t match the app | Update the listing to show the real app and its core features |
| 4.2 Minimum Functionality | The app is a repackaged website or isn’t “app-like” | Add iPhone features such as notifications, widgets, camera or offline use |
| 4.3 Spam | Several copies of the same app, or an app like many others already on the store | Merge versions into one app and show what makes yours different |
| 5.1.1 Privacy | No privacy policy link, or no in-app account deletion | Link the policy in App Store Connect and in the app, and add full account deletion |
| 3.1.1 In-App Purchase | Features or content unlocked by payment outside Apple’s system | Use In-App Purchase for digital features and subscriptions |
| 2.5.2 Software Requirements | The app downloads code that adds or changes features | Ship the features inside the reviewed build |
Guideline 2.1: give App Review full access
Apple asks for a final version, tested on a device, with all URLs working. If your app has a login, App Review needs an active demo account or a full demo mode.
Your backend must be live during review. Explain features that aren’t obvious, and In-App Purchases, in the App Review notes, with documents where needed.
Guideline 4.2: more than a website
Apple’s guideline 4.2 asks for features, content and interface that go beyond a repackaged website. If the app isn’t useful, unique or “app-like,” Apple says it doesn’t belong on the App Store.
This is a frequent block for apps built with web tools and AI builders. The page on AI-built apps on the App Store shows how to add the iPhone features Apple looks for.
Guideline 5.1.1: privacy policy and account deletion
Every app needs a privacy policy link in App Store Connect and inside the app. The policy must say what data the app collects, how it uses it, and how users can request deletion.
If your app lets people create an account, it must also let them start account deletion inside the app. Apple states that offering only to deactivate or disable the account is not enough.
How to reply to App Review in App Store Connect
You reply to App Review on the app’s App Review page in App Store Connect, the area many developers still call the Resolution Center. You can message the reviewer to clear up the issue before you resubmit.
A good reply is short and specific:
- Quote the guideline Apple cited.
- Say exactly what you changed, with the screen or setting where the reviewer can see it.
- Add a demo account, a video or documents if the reviewer needs them.
- Upload the new build, if the fix needed code, and resubmit.
If the issue is only in the listing, such as screenshots or the description, you can often fix it without a new build.
Keep the tone factual. The reviewer checks the app against the guidelines. A clear list of what changed, and where to see it, helps the reviewer confirm the fix.
How to appeal to the App Review Board
If you believe Apple misunderstood your app’s concept or treated you unfairly, you can appeal to the App Review Board. The appeal is for disagreements, not for fixes you can make yourself.
Apple asks for three things in an appeal:
- specific reasons why your app complies with the App Review Guidelines;
- only one appeal per submission that didn’t pass review;
- answers to any request for more information before you appeal.
Expedited review and bug-fix updates
You can request an expedited review for a critical bug fix or a launch tied to an event. For a bug, include the steps to reproduce it on the current version; for an event, include its name, date and your link to it.
If App Review finds new issues in a bug-fix update, Apple may let you fix them in the next submission. This applies when there are no legal or safety concerns, and you accept by replying to the offer in App Store Connect.
How to avoid App Store rejection next time
Many rejections can be prevented with a check before you submit. Apple’s own checklist asks you to test for crashes, complete the metadata, update your contact details, give full access and keep the backend live.
Test every flow in TestFlight with people outside your team before each submission. The guide on how to publish an app on the App Store lists every step, and the Apple Developer account guide covers the account side.
How Carvalho Karsten helps with a rejected app
Carvalho Karsten reads the rejection message, fixes the code or the listing, and replies to App Review until approval. If the case calls for an appeal, the team writes it with the guideline text and evidence.
The work covers native Swift apps and apps built with AI tools. Send the full message from Apple, and Carvalho Karsten replies with what the fix involves and the next steps.