Question 1

What are the most common App Store rejection reasons?

Accepted Answer

The five rejection reasons that account for the majority of App Review declines are Guideline 2.1 (App Completeness — crashes, incomplete builds, broken links), Guideline 4.2 (Minimum Functionality — apps that feel like websites, are too simple, or duplicate an existing web experience), Guideline 5.1.1 (Data Collection and Storage — asking for data you do not need or missing a privacy policy), Guideline 4.3 (Spam — near-duplicate apps or repurposed templates), and Guideline 2.3 (Accurate Metadata — screenshots, keywords, or descriptions that misrepresent the app). Metadata rejections are usually the fastest to fix because they do not require a new binary. Functionality and design rejections almost always require a new build. The rejection message will always cite the specific guideline number, which is why decoding that number first is the fastest path to a fix.

Question 2

How long does it take to get re-reviewed after fixing a rejection?

Accepted Answer

For metadata-only fixes made in App Store Connect, re-review is usually completed within 24 hours because it does not require a new build to be re-uploaded. For rejections that require a new binary — for example, a crash fix, a design change, or an added feature — you have to upload a new build to TestFlight, wait for processing (usually 5 to 30 minutes), submit it for review, and then wait for the review itself. As of 2025, Apple reviews about 90 percent of submissions within 24 hours and about 50 percent within 12 hours. Expedited reviews are available for critical fixes affecting many users and typically come back within 12 hours. You can request one from App Store Connect, but do not abuse it — Apple grants only a few per year per team.

Question 3

Can I appeal an App Store rejection I disagree with?

Accepted Answer

Yes. If you believe your app was rejected in error or that the reviewer misunderstood your app, you can appeal via the App Review Board directly from Resolution Center. Click "Appeal" on the rejection and explain, with evidence, why your app follows the guideline. Include screenshots, video demos, and links to precedent apps that use the same pattern and were approved. Appeals typically get a response within 3 to 5 business days. In parallel, you can also reply in Resolution Center to ask clarifying questions or provide more context to the original reviewer — sometimes a rejection is really a request for information, and a reply is faster than an appeal. Do not resubmit the same build hoping for a different reviewer. That is against the rules and is easy for Apple to detect.

Question 4

What is Guideline 4.2 and how do I fix it?

Accepted Answer

Guideline 4.2 — Minimum Functionality — is Apple's catch-all for apps that they consider too simple, too web-like, or lacking a real reason to exist as a native app. Common triggers: your app is a WebView wrapping a website, your app duplicates a well-known site or template with no additional value, your app is a single-screen calculator or utility with no native features, or your app is essentially a portfolio for one company. Fixes: add native features that a browser cannot do (push notifications, offline mode, camera, biometrics, widgets, Live Activities, App Shortcuts), add real interactivity and data that is not just a mirror of your website, add multiple screens with a clear user journey, and if you must wrap web content, add native UI around it and integrate at least three native iOS features. Guideline 4.2 rejections are extremely common for RapidNative-generated apps because they compile to real React Native, which passes 4.2 easily — the trap is when you ship a mostly-empty app.

Question 5

What is Guideline 2.1 and how do I fix it?

Accepted Answer

Guideline 2.1 — App Completeness — means Apple hit something that shows the app is not ready for users. The three most common triggers are: (1) crashes on launch or during core flows, (2) broken or placeholder content (Lorem Ipsum, "Coming Soon" screens, buttons that go nowhere, dead links), and (3) missing sign-in credentials for a demo account, which prevents the reviewer from testing gated features. To fix 2.1: test on a real device (not just the simulator) using the exact build number you are submitting, walk through every user flow end-to-end, remove or hide any placeholder content, and if your app requires an account, provide reviewer credentials in the App Review Information field. If the rejection mentions a crash, download the crash log from App Store Connect — it will symbolicate the exact line — and fix that first. Most 2.1 rejections are resolved in a single resubmission if you fix all three of those categories at once.

Question 6

What happens if my app keeps getting rejected?

Accepted Answer

Repeated rejections do not put you on a blacklist, but they do slow you down and can eventually trigger a manual review by a senior Apple reviewer or, in extreme cases, a developer account warning. Each rejection resets your position in the review queue, so five rejections effectively cost you five review cycles. The three most useful things you can do after a second rejection are: (1) reply in Resolution Center with specific questions before you resubmit — "Which screen exhibits the crash?" is much cheaper than another rejected build, (2) request a phone call with the App Review team from Resolution Center — Apple actually offers these and reviewers are often willing to walk you through what they saw, and (3) if you have exhausted normal channels, appeal to the App Review Board with a clear demo video. Do not resubmit the same build unchanged, and do not use different developer accounts to try to bypass rejection — both violate the Developer Program License Agreement.

Guideline	Title	What it really means
2.1	App Completeness	Crashes, placeholder content, missing demo credentials
2.3	Accurate Metadata	Screenshots or description misrepresent the app
3.1.1	In-App Purchase	Digital goods must use IAP, not Stripe or web checkout
4.2	Minimum Functionality	Feels like a website; needs more native iOS features
4.3	Spam	Near-duplicate of another app or a repurposed template
5.1.1	Data Collection & Storage	Missing privacy policy or asking for unneeded data
5.1.2	Data Use & Sharing	Sharing user data with third parties without consent

Pre-flight check	Prevents
Test the exact build on a real device, not just the simulator	2.1 App Completeness
Provide demo credentials in App Review Information	2.1 Missing credentials
Remove all Lorem Ipsum, "Coming Soon" and dead links	2.1 Placeholder content
Add 3+ native iOS features (push, widgets, camera, biometrics)	4.2 Minimum Functionality
Publish a privacy policy URL that names every SDK and data type	5.1.1 Privacy
Use IAP for any digital goods or subscriptions	3.1.1 IAP
Match screenshots and description to the actual app	2.3 Metadata accuracy
Ensure your app has a distinct concept, not a repurposed template	4.3 Spam

Guideline	Title	What it really means
2.1	App Completeness	Crashes, placeholder content, missing demo credentials
2.3	Accurate Metadata	Screenshots or description misrepresent the app
3.1.1	In-App Purchase	Digital goods must use IAP, not Stripe or web checkout
4.2	Minimum Functionality	Feels like a website; needs more native iOS features
4.3	Spam	Near-duplicate of another app or a repurposed template
5.1.1	Data Collection & Storage	Missing privacy policy or asking for unneeded data
5.1.2	Data Use & Sharing	Sharing user data with third parties without consent

Pre-flight check	Prevents
Test the exact build on a real device, not just the simulator	2.1 App Completeness
Provide demo credentials in App Review Information	2.1 Missing credentials
Remove all Lorem Ipsum, "Coming Soon" and dead links	2.1 Placeholder content
Add 3+ native iOS features (push, widgets, camera, biometrics)	4.2 Minimum Functionality
Publish a privacy policy URL that names every SDK and data type	5.1.1 Privacy
Use IAP for any digital goods or subscriptions	3.1.1 IAP
Match screenshots and description to the actual app	2.3 Metadata accuracy
Ensure your app has a distinct concept, not a repurposed template	4.3 Spam

App Store Rejection Decoder

Most-Cited App Store Guidelines

How to Resubmit After a Rejection

Rejection-Proof Your First Submission

Frequently Asked Questions

Most-Cited App Store Guidelines

How to Resubmit After a Rejection

Rejection-Proof Your First Submission

Frequently Asked Questions