App Store Review Guidelines in plain English (and the rejections they cause)
A plain-English map of Apple's App Review Guidelines, the rejection reasons developers often hit (2.1, 2.3, 3.1.1, 4.2, 4.3, 5.1.1), how to reply and how to appeal.

Apple's App Store Review Guidelines are one long page with five sections: Safety, Performance, Business, Design and Legal. When a build is rejected, App Review cites a guideline number from that page, such as 2.1 or 4.3, and that number tells you what to fix. This guide is a map of the page, then the rejection reasons developers often meet, with the fix for each.
Everything here is from Apple's App Review Guidelines, whose current version says "Last Updated: October 16, 2026", and Apple's appeal help. Guidelines change, so check the page for your submission. I call a reason "common" from developer experience, not from statistics: Apple doesn't publish a ranking of rejection reasons.
The five sections
| Section | What's in it |
|---|---|
| 1. Safety | 1.1 Objectionable Content, 1.2 User-Generated Content, 1.3 Kids Category, 1.4 Physical Harm, 1.5 Developer Information, 1.6 Data Security, 1.7 Reporting Criminal Activity |
| 2. Performance | 2.1 App Completeness, 2.2 Beta Testing, 2.3 Accurate Metadata, 2.4 Hardware Compatibility, 2.5 Software Requirements |
| 3. Business | 3.1 Payments, 3.2 Other Business Model Issues |
| 4. Design | 4.1 Copycats, 4.2 Minimum Functionality, 4.3 Spam, 4.4 Extensions, 4.5 Apple Sites and Services, 4.7 Mini apps, mini games, streaming games, chatbots, plug-ins and game emulators, 4.8 Login Services, 4.9 Apple Pay, 4.10 Monetizing Built-In Capabilities |
| 5. Legal | 5.1 Privacy, 5.2 Intellectual Property, 5.3 Gaming, Gambling, and Lotteries, 5.4 VPN Apps, 5.5 Mobile Device Management, 5.6 Developer Code of Conduct |
In plain English: Safety is about content and people getting hurt, Performance is "does it work, and does the listing tell the truth," Business is how you charge, Design is whether the app is worth having on the store, and Legal is privacy, intellectual property and your own conduct. Most solo developers spend their time in Performance (2), Business (3) and the privacy rules in 5.1.
Apple also lists items under "Before You Submit," including testing for crashes and bugs, making sure metadata is complete and accurate, giving App Review full access to your app (with a demo account if there's a login), and turning on your backend services. That list is a fair preflight for any submission.
Rejection reasons developers often hit
Guideline 2.1: App Completeness
What it says: submissions "should be final versions with all necessary metadata and fully functional URLs included," and Apple will "reject incomplete app bundles and binaries that crash or exhibit obvious technical problems." It also asks for demo account info if your app has a login, with your back end switched on. 2.1(b) covers in-app purchases: they must be complete and visible to the reviewer.
Typical triggers: a crash on launch on the reviewer's device, a login with no demo account, a server that was off, a placeholder screen, a support URL that doesn't load, an in-app purchase the reviewer can't find.
Fix: test the exact build you upload on a device. Put a working demo account in App Review Information and check it still works the day you submit. If an in-app purchase is hard to reach, say where to find it in the review notes.
Guideline 2.3: Accurate Metadata
What it says: customers should know what they're getting, so your metadata must accurately reflect the app's core experience. 2.3.1(a) requires new features to be "described with specificity" in the Notes for Review, and says generic descriptions "will be rejected." 2.3.7 asks for keywords that accurately describe the app and limits the name to 30 characters (see App Store character limits).
Typical triggers: screenshots that show features the app doesn't have, a description that promises something not delivered, trademarked or competitor names in keywords, pricing words in the subtitle, review notes that say only "bug fixes."
Fix: compare your screenshots and description with the build, line by line. Write the review notes for a person who has never seen the app. Remove other companies' names from the keyword field (see the keyword field guide).
Guideline 3.1.1: In-App Purchase
What it says: to unlock features or functionality (subscriptions, in-game currencies, levels, premium content, a full version) "you must use in-app purchase." Apps "may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, cryptocurrencies and cryptocurrency wallets." Digital gift cards and vouchers redeemable for digital goods can only be sold in the app with in-app purchase.
Typical triggers: a "Buy on our website" button or link to a payment page for digital content, a license key field, or text that tells people how to pay outside the app.
Fix: sell digital content with in-app purchase, or take the external purchase path out of the build. Section 3.1 has other cases (for example 3.1.2 for subscriptions), so read the sub-clause named in your rejection message.
Guideline 4.2: Minimum Functionality
What it says: your app "should include features, content, and UI that elevate it beyond a repackaged website." 4.2.2 adds that other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links.
Typical triggers: a web view wrapped around your site, a one-screen app, an app that is mostly a brochure.
Fix: show the reviewer what the app does that a website can't: native features, offline use, notifications, device integration. Say so in the review notes, with steps.
Guideline 4.3: Spam
What it says: 4.3(a) "Don't create multiple Bundle IDs of the same app" (for example a separate map app for each city), and 4.3(b) "Don't submit apps that are indistinguishable from what's already widely available." Apple names dating, flashlight, sound effects, wallpaper, simple timers and fortune telling as well-established categories where it won't accept new submissions unless they offer a meaningfully different or improved experience.
Typical triggers: a template app resubmitted under many names, a clone of a popular app, a new app in a crowded category with no distinct angle.
Fix: if you have many variations, ship one app and offer the variations through in-app purchase, as 4.3(a) suggests. Otherwise explain in your reply what is meaningfully different, with screenshots or a short video, and make that difference visible in the listing.
Guideline 5.1.1: Data Collection and Storage
What it says: 5.1.1(i) all apps "must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner." 5.1.1(ii) apps that collect user or usage data must get consent, and (iii) apps should only request data relevant to their core functionality. 5.1.1(v) says that if you don't have significant account-based features, let people use the app without a login.
Typical triggers: no privacy policy link in the app, a permission request (location, contacts, tracking) with no clear reason, a mandatory sign-up for an app that doesn't need accounts, privacy answers in App Store Connect that don't match what the app does.
Fix: add the policy link in both places, write permission purpose strings that say why you need each one, and make sure your App Privacy answers match your SDKs (analytics and ad SDKs count).
How to reply in Resolution Center
A rejection arrives as a message in the Resolution Center in App Store Connect, with the guideline number and what App Review found. Reply there, not by email:
- Read the guideline text, not just the number. Rejections often cite a sub-clause such as 2.1(a) or 4.3(b).
- Check whether you can fix it. If the reviewer is right, fix it, upload a new build if the problem is in the binary, and reply to say what changed.
- If it's a misunderstanding, explain it in plain steps: where to tap, which account to use, what the feature does. Attach a short screen recording if it helps.
- Be specific and polite. One short message with the facts works better than an argument.
Timing depends on the queue, so see how long App Review takes. If a delay is costing you something real, an expedited review is a separate request, and the appeal form isn't the way to ask for one.
Appeals
If you disagree with a decision, the App Review Board handles appeals. Apple's help says to appeal when your app was rejected or removed but you believe it follows the guidelines and the Developer Program License Agreement, or when you believe you experienced unfair or biased treatment. Apple's steps:
- First reply to the rejection message in App Store Connect and clarify the issue.
- If that doesn't resolve it, use the "Submit an appeal to App Review" form. Point to the specific requirements involved and explain how your app satisfies them.
- Wait for the App Review Board to message you in App Store Connect. It may ask for more information or schedule a call.
The limits: one appeal per rejected app (address every cited guideline in it), and the form takes up to five apps. Don't use it to get a status update, request an expedited review, answer a request for more information, or after you've already fixed the issues and resubmitted. Apple says even a complete appeal "does not guarantee" that the Board will overturn the decision, and doesn't promise a timeline.
Catching it before submission
Storewatch has a Pre-submission check that looks at What's New in every language, text limits, listing problems, your demo account, review notes, and whether there's a valid build with the right version number. It also has an optional AI check against the App Review Guidelines. When a submission comes back with issues, the Rejection log adds an entry automatically, and you can edit the notes, so you remember what App Review said and what fixed it. It won't replace testing the build yourself.
Frequently asked questions
What are the App Store Review Guidelines?
Apple's published rules for apps on the App Store, in five sections: Safety, Performance, Business, Design and Legal. App Review checks every submission against them and cites a guideline number when it rejects one.
What does guideline 2.1 mean?
App Completeness. Your app should be a final version, with complete metadata, working URLs, a demo account if there's a login, and no crashes or obvious technical problems.
What does guideline 4.3 mean?
Spam. Don't create multiple Bundle IDs of the same app, and don't submit apps indistinguishable from what's already widely available. If you have variations, use a single app with in-app purchase.
What are the most common reasons for App Store rejection?
Apple doesn't publish a ranking. From developer experience, guidelines 2.1 (crashes, missing demo account), 2.3 (metadata that doesn't match the app), 3.1.1 (payments outside in-app purchase), 4.2, 4.3 and 5.1.1 come up often.
How do I appeal an App Store rejection?
Reply to the rejection in App Store Connect first. If that doesn't resolve it, submit the appeal form to the App Review Board, point to the specific guidelines and explain how your app meets them. Submit only one appeal per rejected app.
How long does an App Review take?
It varies, and Apple doesn't promise a fixed time. See App Store review times for the numbers Apple shows.