What are the most common App Store rejection reasons?

For indies, five patterns cover most rejections: the app crashed or a flow broke during review (Guideline 2.1), the reviewer couldn't test it (missing demo account or unclear instructions), digital goods sold outside Apple's in-app purchase system (3.1.1), minimum functionality: the app does too little (4.2), and metadata problems: screenshots or descriptions that promise things the app doesn't show.

How do I avoid App Store review rejections?

Test the exact build you upload on a clean device, fill in the review notes like the reviewer knows nothing (working demo account, where the paid features live, anything unusual explained), make sure every screenshot shows real app functionality, and use Apple's in-app purchase for all digital content. Most rejections are preventable paperwork, not judgment calls.

Should I appeal an App Store rejection or just resubmit?

If the reviewer is factually wrong or the guideline was misapplied, reply in Resolution Center calmly with specifics. Polite, factual responses regularly reverse rejections without code changes. If the complaint is legitimate, fix and resubmit; arguing a fair call costs days you could have spent shipping the fix.

FunnelHound / Guides / Rejection reasons & fixes

App Store rejection reasons and how to fix them

By Emin, indie iOS developer building FunnelHound · Published 27 Sep 2026

A rejection email at 6am reads like a verdict. It's usually paperwork. Five patterns cover most indie rejections, four of them preventable before upload, and the fifth is often reversible with a calm reply. Here's the pattern list, the fixes, and when to argue.

The five patterns

1. It broke during review (2.1). Crash on launch, dead flow, spinner forever. Classic causes: a backend the reviewer can't reach, a build tested in debug but shipped in release, region-dependent features. Fix: test the uploaded build, release configuration, clean device, airplane-mode the flows that should survive offline. (Our own TestFlight build once crashed for every tester over a release-only key mismatch. The "works on my machine" tax is real.)
2. The reviewer couldn't test it. Login required, no demo account provided, or the demo account expired, or the magic happens only with data the reviewer doesn't have. Fix: a working demo account in the review notes, pre-loaded with data that makes the app worth approving, plus one paragraph of "here's where everything lives". Write the notes like the reviewer knows nothing and has four minutes. They might.
3. Digital goods outside StoreKit (3.1.1). Unlocking features via external payment, links steering users to buy elsewhere. The most-litigated corner of the store and regionally in flux, but the indie-safe default hasn't moved: digital content unlocks through Apple's IAP.
4. Minimum functionality (4.2). The app does too little to be an app: thin wrappers around a website, single-shot utilities. Fix is product, not paperwork: ship a real reason to be native. If this one stings, it's because it's half true.
5. Metadata mismatch. Screenshots showing features that don't exist, keyword-stuffed names, descriptions promising the moon. Review reads your listing against your binary. The honest-screenshots rule isn't just conversion advice, it's compliance.

When to argue, when to fold

Resolution Center replies work more often than the horror stories suggest, when the reviewer is factually wrong. "The crash isn't reproducible; here's a video of the flow on a clean device" reverses rejections. What never works: arguing a fair call, or heat. If the complaint is legitimate, the fastest path through review is the fix. Rejections also aren't rare weather. Plan the release cadence assuming the occasional bounce, and launch-critical submissions get a buffer day, not a same-day deadline.

Rejection ≠ ranking damage

The persistent fear: "will rejections hurt my ASO?" A routine rejection-fix-resubmit cycle leaves no mark on your ranking: review and search are different machines. What does hurt: shipping around review with spammy metadata until trust erodes account-wide. Play the long game with a clean account, and review stays a speed bump, not a wall. Once you're through, the store's real judges take over (impressions, installs, retention), and that's the part you measure rather than appeal.

Approved. Now comes the real review.

FunnelHound tracks how the store's actual jury votes: impressions, installs, purchases from App Store Connect, every day.

Get FunnelHound

Share this on X

Data notes: guideline numbers and review mechanics per Apple's App Review Guidelines as of 2026; payment-steering rules (3.1.1) vary by region and are actively changing. Check current rules for your storefronts. Frequency ranking of rejection patterns is practitioner consensus, not Apple statistics.