App Store Review Guidelines: What Gets Your App Rejected in 2026

Apple rejected over 1.7 million app submissions in 2025. That is not a typo. Nearly 40% of all submissions hit at least one rejection before being approved. For indie developers who have spent months building their app, a rejection email is demoralizing. But it does not have to be surprising.

The vast majority of rejections fall into a small number of predictable categories. If you understand what Apple’s review team is looking for and what triggers an automatic rejection, you can avoid weeks of back-and-forth and get your app approved on the first try.

This guide breaks down the most common rejection reasons with real percentages, explains the rules that trip up indie developers most often, and gives you a pre-submission checklist to catch issues before Apple does.

The Most Common Rejection Reasons (By the Numbers)

Apple publishes transparency data, and developers who have been through the process repeatedly have shared their experiences. Here is what the data tells us about why apps get rejected:

Rejection Reason	Percentage of All Rejections	Severity
Guideline 2.1 — Performance: App Completeness	18%	Common, easy fix
Guideline 4.0 — Design: Minimum Functionality	12%	Moderate, may require redesign
Guideline 2.3 — Performance: Accurate Metadata	11%	Common, easy fix
Guideline 5.1.1 — Legal: Data Collection and Storage	10%	Growing in 2026
Guideline 3.1.1 — Business: In-App Purchase	9%	Complex, strict enforcement
Guideline 4.2 — Design: Minimum Quality	8%	Subjective, can be frustrating
Guideline 2.5.1 — Software Requirements	7%	Technical, usually clear fix
Guideline 1.2 — Safety: User Generated Content	6%	Requires moderation plan
Other guidelines combined	19%	Varies

The top three reasons account for 41% of all rejections, and they are all preventable with proper preparation.

Metadata Rejections: The Most Avoidable Category

Guideline 2.3 covers your app’s name, description, screenshots, and keywords. It is one of the easiest rejection categories to avoid yet remains in the top three because developers rush through their metadata.

What Triggers a Metadata Rejection

Misleading screenshots. If your screenshots show features that do not exist in the app, or show a UI that looks significantly different from the actual app, you will be rejected. This includes using mockups instead of real screenshots and showing premium features without indicating they require a purchase.

Keyword stuffing. Apple explicitly prohibits using competitor names, irrelevant terms, or generic descriptors like “best” or “free” in your keyword field. Your title and subtitle are also subject to this rule.

Inaccurate descriptions. Your description must accurately reflect what the app does. Promising features that are “coming soon” or describing capabilities the current version does not have will trigger a rejection.

Placeholder content. Leftover “Lorem ipsum” text, test data visible in screenshots, or default app icons will get you rejected under the completeness guidelines.

Metadata Element	Common Mistake	How to Fix
App name	Including generic terms like “Best” or “Free”	Use descriptive, unique name
Subtitle	Keyword stuffing	Write naturally, include 1-2 keywords
Screenshots	Showing features not in current version	Use real, current app screenshots
Description	Mentioning upcoming features	Only describe current functionality
Keywords	Using competitor brand names	Research legitimate keywords
What’s New	Leaving blank or generic “Bug fixes”	Describe actual changes

Your screenshots deserve special attention. Follow the screenshot best practices and make sure every screenshot accurately represents the current state of your app. Use a tool like Screenshot Lab to create professional screenshots from your actual app captures.

UI/UX Rejections: Design Standards That Matter

Guidelines 4.0 and 4.2 cover design quality and minimum functionality. These rejections are more subjective and can feel unfair, but Apple has clear patterns in what they enforce.

Minimum Functionality (Guideline 4.0)

Apple will reject apps that are essentially websites wrapped in a WebView, simple RSS readers without added value, apps that duplicate built-in iOS functionality without meaningful improvement, or apps with a single feature that could be a widget or a website.

The standard is higher than you think. Your app needs to provide genuine value that justifies its existence as a native app.

Minimum Quality (Guideline 4.2)

This guideline catches apps with poor UI, broken layouts, missing error handling, or experiences that feel unfinished. Common triggers:

Broken UI on certain device sizes
Missing loading states (blank screens while data loads)
No error handling for network failures
Landscape mode that is clearly broken
Accessibility issues (missing labels, poor contrast)

Test your app on every supported device size. If you support iPhone, test on SE, standard, and Max sizes. If you support iPad, test on all iPad sizes. If you support Mac, test on different window sizes.

Privacy and Permission Rejections

Privacy rejections have increased dramatically since 2024. Apple is enforcing data handling requirements more strictly than ever.

Privacy Nutrition Labels

Your App Privacy details in App Store Connect must accurately reflect every piece of data your app collects, links to the user, or uses for tracking. Common mistakes:

Data Practice	Often Missed By Developers
Analytics SDKs (Firebase, Mixpanel)	Collecting device identifiers, usage data
Crash reporting (Crashlytics, Sentry)	Collecting device info, crash logs
Ad SDKs (AdMob, Unity Ads)	Tracking identifiers, browsing data
Social login (Sign in with Apple, Google)	Collecting name, email
Push notifications	Collecting device token

If you use any third-party SDK, read its privacy documentation and declare every data type it collects. Underdeclaring is a guaranteed rejection.

App Tracking Transparency

If your app accesses the IDFA (Identifier for Advertisers) for any reason, you must implement the ATT framework and show the tracking permission dialog. This includes apps that use ad networks, even if you do not track users yourself. The ad SDK might.

Required Permissions

Only request permissions your app actually needs, and only at the moment they are needed. Requesting camera access on first launch for an app that rarely uses the camera will raise flags. Apple expects contextual permission requests with clear explanations.

In-App Purchase Rules: The Strictest Category

Guideline 3.1.1 is where Apple is most inflexible. The rules around in-app purchases affect how you monetize your app, and violations can lead to extended review times and repeated rejections.

The Core Rules

All digital content must use Apple’s IAP system. You cannot link to an external website for purchases, mention that cheaper alternatives exist, or use your own payment processing for digital goods.
Physical goods and services can use external payment. If you sell physical products, real-world services, or person-to-person services, you can use Stripe, PayPal, or any other processor.
Subscriptions must clearly communicate terms. The price, duration, and renewal behavior must be visible before the user subscribes. Free trial terms must be prominent.
No “bait and switch” paywalls. You cannot make an app appear free and then require payment to use basic functionality. The free tier must provide genuine value.

Monetization Type	Apple IAP Required?	Commission Rate
Digital subscriptions	Yes	15-30%
One-time digital purchases	Yes	15-30%
Physical goods	No	0%
Real-world services (Uber, Airbnb)	No	0%
Reader apps (Netflix, Spotify)	Complex — special rules	Varies

For a detailed breakdown of pricing models and their implications, see our app pricing strategies guide.

How to Appeal a Rejection

If you believe your rejection is wrong, you have the right to appeal. Here is how to do it effectively:

The Appeal Process

Reply to the rejection in App Store Connect. Do not submit a new build. Use the Resolution Center to respond directly to the reviewer.
Be specific and polite. Reference the exact guideline cited. Explain clearly why you believe your app complies. Include screenshots or screen recordings if they help.
Request an Appeal Board review. If the reviewer does not reverse the decision, you can escalate to the App Review Board. This is a different team that reviews the original decision independently.
Contact Apple Developer Relations. For complex cases, reach out to developer relations through your Apple Developer account.

Tips for Successful Appeals

Never argue emotionally. Stick to facts and guidelines.
Provide evidence. Screenshots, documentation, and comparisons to approved apps are all helpful.
If the reviewer’s feedback is vague, ask for clarification before making changes.
Keep your response concise. Long, rambling appeals are harder to process.

The success rate for appeals varies, but well-documented, specific appeals have a reasonable chance of success. Vague complaints about fairness do not.

The Pre-Submission Checklist

Run through this checklist before every submission. Print it out. Pin it to your wall. Most rejections are preventable.

Metadata

Technical

App runs without crashes on all supported devices
No placeholder or test content visible
All features shown in screenshots are functional
Network error handling is implemented
Loading states are present (no blank screens)
Permissions are requested contextually with clear explanations
IPv6 networking is supported
Minimum OS version is set correctly

Privacy

App Privacy details accurately declare all data collection
Privacy policy covers all data practices
ATT dialog implemented if using IDFA
App Check and authentication properly configured

Business

All digital purchases use Apple IAP
Subscription terms are clearly displayed
Free tier provides genuine value
No external payment links for digital goods
Restore purchases button is accessible and functional

Content

User-generated content has moderation plan
No copyrighted material without permission
Age-appropriate content for declared rating
No misleading claims about app capabilities

Using this checklist consistently will save you the most frustrating part of app development: waiting for a rejection, fixing it, resubmitting, and waiting again.

What Changed in the 2026 Guidelines

Apple updates its review guidelines regularly. Here are the most significant changes for 2026:

Change	Impact	What to Do
Stricter AI disclosure requirements	Apps using AI must disclose it	Add AI disclosure to description and settings
Enhanced privacy nutrition labels	More granular data categories	Audit all SDKs for data collection
Mandatory accessibility baseline	VoiceOver support required for new apps	Add accessibility labels to all interactive elements
Updated EU DMA compliance	Alternative payment processors in EU	Implement if targeting EU market
Stricter screenshot accuracy enforcement	AI-generated mockups flagged more often	Use real app screenshots via tools like Screenshot Lab

Stay current with the official App Store Review Guidelines and subscribe to Apple’s developer news for updates.

FAQ

How long does App Store review take? The average review time in 2026 is 24-48 hours for new submissions and updates. However, first-time submissions from new developer accounts may take longer, sometimes up to 5-7 days. Expedited reviews are available for critical bug fixes through App Store Connect, but Apple grants them at their discretion.

Can I resubmit immediately after a rejection? Yes. Fix the cited issue, and resubmit through App Store Connect. There is no waiting period. However, make sure you address the specific feedback in the Resolution Center before resubmitting. Submitting the same build without changes will result in another rejection and may flag your account for additional scrutiny.

Do screenshots really cause rejections? Yes. Misleading or inaccurate screenshots are one of the top metadata rejection reasons. Apple’s review team compares your screenshots to your actual app. If they do not match, or if they show features that do not exist, you will be rejected. Follow the screenshot creation guide to create accurate, professional screenshots.

What happens if I get rejected multiple times? Repeated rejections for the same issue may result in longer review times and additional scrutiny on future submissions. If you are stuck in a rejection loop, use the Resolution Center to communicate with the reviewer and ask for specific guidance. You can also escalate to the App Review Board for a fresh perspective. Consider reviewing the App Store listing optimization checklist to ensure everything is in order.