Apple App Store Rejection Codes 2026: Every Guideline, Description & Fix
Got rejected? Here's every App Store review rejection code — Guideline number, plain-English description, and a concrete fix — all in one searchable reference. 20 codes covering Safety, Performance, Business, Design, and Legal. Free, no signup.
All App Store Rejection Codes
Filter by category or frequency. Click the Apple guidelines link on any card to read Apple's exact wording.
App contains content that is offensive, insensitive, upsetting, intended to disgust, or in exceptionally poor taste. Includes violence, adult content, defamatory material, or content that demeans groups of people.
Remove or restrict objectionable content. Use age-rating gates. If showing mature content, enable it only after explicit user opt-in and set the appropriate age rating.
Apps that enable UGC lack required safeguards: a filtering system for objectionable material, a mechanism to report offensive content, the ability to block abusive users, and a clearly accessible contact method for reporting to the developer.
Implement all four required safeguards: content filter, report button, block mechanism, and a contact/report channel. Document each in your review notes.
App makes inaccurate medical or health claims, or provides medical diagnosis/treatment advice without proper disclaimers. Applicable to apps using AI for health-related features.
Add clear "not a substitute for professional medical advice" disclaimers. Remove specific diagnostic claims. Work with a licensed medical professional to validate wording.
App is incomplete: placeholder content, lorem ipsum text, broken UI, crashes on launch, or features inaccessible to reviewers. Demo/beta/test apps are not accepted.
Ensure all features work end-to-end. Replace all placeholder content. Provide a test account in review notes if login is required. Test on a real device at the exact iOS version Apple specifies.
App name, subtitle, description, keywords, screenshots, or previews misrepresent the app's actual functionality or include false information about features, pricing, or results.
Align every metadata field with the actual shipped features. Remove superlatives ("best", "#1") unless backed by verifiable evidence. Don't list features in the description that are not yet live.
Screenshots do not accurately represent the app's UI — showing a different app, non-existent features, or marketing imagery without any actual app interface.
Screenshots must show real in-app UI at the correct resolution. Marketing text overlays are fine; showing a completely different interface is not. See shotlingo.com/tools/app-store-screenshot-sizes for exact dimensions.
App fails on Apple's IPv6-only test network. Apple requires all apps to support IPv6 since iOS 9. This surfaces if you hardcode IPv4 addresses or use old network APIs.
Never hardcode IP addresses; use hostnames. Use high-level Apple networking APIs (URLSession, Network.framework). Test on a Mac sharing internet via IPv6-only Personal Hotspot.
App uses deprecated, private, or undocumented Apple APIs that Apple's automated scan flags. Includes use of UIWebView (deprecated since iOS 12), removed networking APIs, or private symbol imports.
Replace UIWebView with WKWebView. Run a static analysis pass: grep your codebase for any symbols Apple flagged. Use Xcode's API availability checker and target the minimum iOS version you actually support.
App includes buttons, links, or other UI that direct users outside the app to purchase digital goods or unlock premium features without using Apple's in-app purchase system.
Remove any "buy on our website" links for digital content within the app. All digital goods must go through IAP. Physical goods and services (e.g. booking a taxi) are exempt.
Reader app (streaming music, video, news, magazines, books) includes an in-app link to sign up for the service. Reader apps may not link to external purchase flows.
Remove all "sign up" / "subscribe" links that open a web browser or sheet. You may tell users a paid account exists outside the app, but cannot provide a direct link to sign up. Include a link to Apple's required disclosure about reader app subscriptions.
App transmits, mines, or exchanges cryptocurrency without complying with local laws in the target markets, or without proper licensing. Crypto mining apps are prohibited outright on iOS.
Crypto apps must operate under valid money transmitter licenses in all jurisdictions where the app is available. Mining apps are not permitted. Ensure explicit documentation of licensing in review notes.
App UI does not meet Apple's general design quality bar: inconsistent icon style, broken Auto Layout on different device sizes, or UI that does not behave as iOS users expect.
Follow Apple Human Interface Guidelines. Test on all required device sizes. Use system components where possible. Ensure auto-layout handles iPhone 6.9" through SE and iPad 13" without breakage.
App does not provide enough useful functionality to be worth distributing. Thin-wrapper web apps, simple utility apps with a single feature, and apps that are entirely off-device also fall here.
Add meaningful native functionality. If the core value is a website, submit as a Progressive Web App instead, or add native features (notifications, widgets, Siri integration) that justify an App Store presence.
App is too similar to existing apps from the same developer or is one of many near-duplicate apps flooding the store with the same functionality.
Differentiate meaningfully from your existing apps. If you maintain multiple country-specific apps, consolidate into one with localization. Remove duplicate apps from your portfolio before submitting new ones.
Multiple apps submitted with the same idea — cookie-cutter or template apps with little customization, or apps created to artificially inflate rankings or reviews.
Submit one high-quality app rather than many thin variants. If you offer a white-label service, use a B2B model rather than submitting individual apps per client. Remove artificial rating/review prompts.
App collects user data without a clear privacy policy, fails to disclose data collection in App Store Connect privacy nutrition labels, or collects more data than required for app functionality.
Add a privacy policy URL to App Store Connect. Fill in all privacy nutrition labels accurately — include every data type collected, even if collected by third-party SDKs. Apply data minimization: only collect what you use.
App shares user data with third parties in ways not disclosed in the privacy policy, uses data for purposes beyond what the user consented to, or enables ad targeting without proper user consent under App Tracking Transparency.
Implement ATT prompt before any cross-app tracking. Update privacy policy to list all third-party data recipients. Audit all SDKs for data sharing. Use SKAdNetwork for attribution instead of raw IDFA where possible.
App requests location access (Always or When In Use) without a clear, specific purpose string, or uses location data for a purpose other than what was disclosed (e.g., collecting for advertising).
Write precise NSLocationWhenInUseUsageDescription / NSLocationAlwaysAndWhenInUseUsageDescription strings that explain exactly why location is needed. Only request Always access if the core function requires background location.
App uses copyrighted music, images, video, or other media without a license. Includes background music from major labels, stock images without a commercial license, or third-party brand logos.
License all media through proper channels (e.g., Artlist, Musicbed for music). Remove infringing content. If the app generates or transforms copyrighted content, add appropriate DMCA takedown mechanisms.
App involves real-money gambling, sweepstakes, or lotteries without the proper licensing for each jurisdiction in which it is available. This includes apps that simulate casino games with real-money prize redemption.
Obtain and document gambling licenses for every country where the app is available. Restrict availability to legal jurisdictions only. For simulated gambling with no real money, ensure no cash-out path exists.
The 3 Most Common Rejection Reasons in 2026
Apple doesn't publish statistics, but these three guidelines consistently account for the majority of first-submission rejections:
- Guideline 2.1 — App Completeness. The reviewer hit a crash, saw placeholder content, or couldn't access the app because there was no test account in the review notes. Fix: provide credentials, test on a real device, remove all placeholder text.
- Guideline 4.2 — Minimum Functionality. App is too thin — a web view, a PDF reader, or a single-screen utility. Fix: add at least one native feature that a mobile website can't replicate.
- Guideline 3.1.1 — In-App Purchase. A "Buy on website" button or link redirects users outside the app to pay for digital goods. Fix: remove the link; all digital purchases must go through Apple's IAP.
How to Respond to a Rejection
You have two paths: Resolution Center (direct reply to the reviewer, resolves >80% of cases) and App Review Board appeal (escalation, used when you disagree with the ruling).
- Open App Store Connect → go to the specific app version → click "Resolution Center".
- Read the rejection notice carefully. Quote the exact guideline Apple cited.
- If you agree: explain the fix, resubmit. Do NOT argue in the reply — just explain what you changed.
- If you disagree: request a call via Resolution Center. A phone call resolves ambiguous cases faster than written back-and-forth.
- If the call doesn't resolve it: submit an App Review Board appeal with screenshots, links, and precedent examples of similar approved apps.
Download the Dataset
Use the JSON in your app review checklist, CI pre-submit script, or internal wiki. The CSV opens in any spreadsheet.
Embed This Reference on Your Site
Drop the iframe below into any ASO guide, iOS dev blog, or documentation site. It auto-themes to light/dark.
Fix screenshot rejections in minutes.
Guideline 2.3.3 rejections (wrong screenshot dimensions or misleading screenshots) are the easiest to fix. Shotlingo exports every App Store screenshot at the correct size for every device class, in 40+ languages.
Start free Screenshot size reference ↗Frequently Asked Questions
What is the most common App Store rejection reason?
The most common rejection reasons are Guideline 2.1 (App Completeness — crashes, placeholder content, or missing test credentials), Guideline 4.2 (Minimum Functionality — app doesn't do enough), and Guideline 3.1.1 (In-App Purchase — linking outside the app to buy digital goods). Together these account for the majority of first-submission rejections.
How long does Apple take to review an app after a rejection?
After you resubmit following a rejection, standard review typically takes 24–48 hours. If you request expedited review (for a critical bug or time-sensitive launch), Apple targets 24 hours but this is not guaranteed.
What is Guideline 4.2 Minimum Functionality?
Guideline 4.2 means Apple considers your app too simple or thin to merit an App Store listing. It commonly hits single-feature utilities, web-view wrappers, and apps that duplicate free OS features. Fix: add native functionality (widgets, Siri shortcuts, Share extensions) that adds real value beyond what a mobile website provides.
Can I appeal an App Store rejection?
Yes. You can reply to the review team directly via App Store Connect Resolution Center to clarify misunderstandings. If you disagree after that, you can submit a formal appeal through the App Review Board. The appeal is most effective when you cite the specific guideline and explain clearly how your app complies. Most rejections are resolved via the Resolution Center without a formal board appeal.
What is the Guideline 3.1.1 rejection and how do I fix it?
Guideline 3.1.1 means your app offers a way for users to pay for digital content that bypasses Apple's In-App Purchase system — such as a "Buy on website" button. Fix: remove any link that directs users to purchase digital goods outside the app. Physical goods and real-world services are exempt. If you sell subscriptions that work across platforms, use the StoreKit external purchase entitlement (available in the EU under the DMA).
What is App Store Guideline 5.1.1 and why does it cause rejections?
Guideline 5.1.1 covers privacy data collection. Rejections happen when: (a) you have no privacy policy URL in App Store Connect, (b) your privacy nutrition labels don't accurately reflect every type of data collected including by third-party SDKs, or (c) you collect more data than your disclosed purpose requires. Fix: audit every SDK you've integrated, fill privacy labels completely, and link a specific privacy policy (not a generic company one).
How do I fix a Guideline 2.3.3 screenshot rejection?
Guideline 2.3.3 rejects screenshots that don't show the actual app interface. Reviewers use screenshots during review, so they notice when the screenshot shows a different UI than what they see. Fix: export screenshots directly from your app (not from design mockups) at the exact pixel dimensions Apple requires. Marketing text overlays on top of real UI are permitted; fake UI is not.
What happens if I get rejected three times?
There is no automatic penalty for multiple rejections, but persistent violations of the same guideline may flag your developer account for additional scrutiny. Apple can terminate developer accounts for egregious or repeated violations. After 3+ rejections on the same issue, request a call with the App Review team via the Resolution Center — a live discussion often resolves ambiguous interpretations faster than written back-and-forth.
Sources & Changelog
Sourced from: Apple App Review Guidelines. This page is maintained independently — always cross-check against Apple's current guidelines before submitting.
- 2026-06-20 — Initial publication. 20 codes covering the most common rejection categories, verified against Apple App Review Guidelines.