Top 12 App Store Rejection Reasons in 2026 (and How to Avoid Each)

40-60% of first-time iOS app submissions get rejected. The good news: 95% of rejections are predictable, well-documented in Apple’s guidelines, and avoidable with a pre-flight checklist. We’ve shipped 22 apps - here are the 12 rejection reasons we see most, exact policy clause numbers, and the fix for each.

Why so many apps get rejected

Apple’s App Review team checks every submission against the App Store Review Guidelines. Most rejections fall into 5 buckets: incomplete info, broken functionality, privacy violations, design issues, or policy non-compliance. The pattern is so consistent we now run a 30-point pre-submission audit on every client app - reduced our rejection rate from ~50% to under 8%.

The 12 most common rejection reasons

1. Guideline 2.1 - Incomplete app information

Test account credentials missing, demo mode not working, reviewer can’t access core flows. Fix: always provide a test account with full access in the App Review Information section. Test the credentials yourself the morning of submission.

2. Guideline 4.0 - Design (cookie-cutter / spam)

Templated apps that look like 100 other apps, especially in categories like prayer apps, weather, calculators. Fix: custom UI, original branding, at least one feature genuinely unique to your app.

3. Guideline 5.1.1 - Privacy data collection without consent

Collecting location, contacts, photos, mic without a permission prompt - or with a vague reason string. Fix: every permission needs a specific, user-facing usage description in Info.plist (e.g. NSLocationWhenInUseUsageDescription).

4. Guideline 5.1.1(v) - Account sign-in without "Sign in with Apple"

If you offer third-party sign-in (Google, Facebook), you must also offer Sign in with Apple. Fix: add Sign in with Apple as a third option. ~3-5 hours of dev work.

5. Guideline 3.1.1 - Using external payments instead of IAP

Selling digital goods, subscriptions, or unlocking features through a web payment link instead of Apple’s in-app purchase. Fix: use StoreKit / RevenueCat for any digital purchase. Physical goods + services delivered offline can use external payments.

6. Guideline 4.2 - Minimum functionality

Apps that are basically a wrapper around a website with no real native functionality. Fix: add at least 2-3 genuinely native features (push notifications, offline mode, camera/photo integration, share extension).

7. Guideline 2.3.3 - Misleading screenshots

App Store screenshots show features that don’t exist, fake UI, or content that misrepresents the app. Fix: every screenshot must be from your actual app. Don’t mock up features you haven’t built.

8. Guideline 1.1.6 - Inaccurate app descriptions

Description claims features that aren’t in the app, mentions competitor brands inappropriately, includes keyword stuffing. Fix: write descriptions that match actual functionality. Avoid “like X but better” comparisons.

9. Guideline 2.5.4 - Background modes abuse

Using background location, audio, or other background modes when your app doesn’t genuinely need them. Fix: only declare background capabilities you actually use. Apple checks - they will reject if you declare audio background mode but never play audio.

10. Guideline 5.1.2 - Tracking without ATT

Tracking users across apps/websites for advertising without showing the App Tracking Transparency prompt. Fix: implement ATTrackingManager properly, show the prompt before any tracking begins.

11. Guideline 4.5.6 - Spam keyword stuffing

App name, subtitle, or keywords field stuffed with terms unrelated to your app or competitor names. Fix: keep the 30-character app name relevant. Use the 100-character keywords field for legitimate variations only.

12. Guideline 2.1 - Crashes during review

The reviewer’s device crashes the app on the first or second flow. Fix: test on real older devices (iPhone SE 2nd gen, iPad 9th gen). Run instruments for memory leaks. Submit a production build, not a debug build.

Play Store equivalents

Google Play has a much higher first-pass acceptance rate (~85-90%) but also rejects for:

• Data Safety section incomplete or inaccurate
• Sensitive permissions (SMS, Call Log, accessibility) without exemption
• Target API level too old (Google requires latest minus 1 typically)
• Content rating mismatched to actual content
• Privacy policy URL missing or broken
• App Bundle issues (not using Android App Bundle / AAB format)

How to appeal a rejection

1. Read the rejection carefully. Apple cites the specific guideline number. Read that exact guideline.
2. Fix and resubmit if the issue is clear. Faster than appealing.
3. Reply in Resolution Center if you disagree. Be specific, polite, cite Apple’s guidelines back. Provide screenshots, video.
4. Appeal Board for unresolvable disputes. Honestly, rarely worth it - faster to adjust the app.
5. Avoid Twitter / Apple PR as a strategy. The Review team doesn’t respond well to public pressure.

Pre-submission checklist (the 30 points we run)

• ✅ Test account credentials provided AND tested today
• ✅ Demo mode / restricted flow accessible to reviewer
• ✅ All permission strings (NS*UsageDescription) present and specific
• ✅ Sign in with Apple if third-party sign-in offered
• ✅ ATT prompt implemented if tracking
• ✅ Privacy policy URL live and matches App Privacy details
• ✅ App Privacy details (data collection, types, purposes) accurate
• ✅ IAP used for all digital purchases
• ✅ No mentions of payment alternatives in app or screenshots
• ✅ Screenshots all real, no mocked features
• ✅ Description matches actual functionality
• ✅ Background modes declared match actual use
• ✅ Tested on iPhone SE 2nd gen + iPad 9th gen (old but supported)
• ✅ Production build (Release config), not Debug
• ✅ No crashes in first 5 minutes of usage
• ✅ Keyboard handling works in all forms
• ✅ Status bar style appropriate per screen
• ✅ Loading states implemented (no blank screens > 2s)
• ✅ Empty states implemented
• ✅ Error states implemented
• ✅ Offline behaviour graceful (or explicit message)
• ✅ Universal links / deep links work
• ✅ External browser links use Safari View Controller, not embedded WebView
• ✅ App icon meets all required sizes
• ✅ Launch screen exists, doesn’t feel like an ad
• ✅ Login + signup flow works without errors
• ✅ Forgot password flow works
• ✅ Logout works and clears state
• ✅ Push notification permission asked at appropriate moment
• ✅ Build version + version number correct in App Store Connect

Use this checklist on every submission. It’s why our rejection rate is now under 8% vs the 40-60% industry average. Need help getting an app approved? We’ve un-stuck dozens of apps from rejection cycles. Related: how long to build an app, App Store optimization.