# App Store rejection reasons and fixes (2026), guideline by guideline

> Most App Store rejections cite one of a small set of App Review Guidelines (2.1 App Completeness, 2.3 Accurate Metadata, 3.1.1 In-App Purchase, 4.2 Minimum Functionality, 4.3 Spam and 5.1.1 Data Collection and Storage), and each is fixed by changing the build or the metadata, replying in App Store Connect, or, if you believe the decision is wrong, appealing to the App Review Board.

Uptika team · Published: 2026-11-05 · Last updated: 2026-11-05 · https://uptika.app/en/guides/app-store-rejection-reasons

## How does App Review decide?

App Review checks every new app, update, in-app purchase, in-app event and custom product page against the [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/). The current version was last updated on **16 October 2026**; check that date before you rely on any rejection guide, including this one. Apple says it typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours, and that complex apps, or apps rejected repeatedly for the same guideline, take longer.

When something fails, the submission's status changes to **Unresolved Issues** and you get a message in App Store Connect that names the guideline. Apple's own statistic tells you where to look first: "On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more."

## Which guidelines cause most rejections, and how do you fix each?

Each row gives the guideline as Apple numbers and names it, what the reviewer usually saw, and the fix. The detailed guides go deeper on each.

| Guideline | What the reviewer usually saw | Fix |
|---|---|---|
| 2.1 App Completeness | Crash on launch or on a key flow; placeholder text; dead links; no demo account; backend off | Test on a device with the latest OS; remove placeholders; give a demo account that works at submission; keep the backend on. See [Guideline 2.1](https://uptika.app/en/guides/guideline-2-1-app-completeness) |
| 2.1(b) In-app purchases | A configured purchase the reviewer could not find or buy | Make every IAP complete and reachable, or explain in the review notes why one is not visible |
| 2.3.3 Screenshots | Screenshots that only show a splash, login page or marketing art | More than half of the screenshots for each device must show the app in use |
| 2.3.7 Accurate metadata | Other apps' names, trademarks, prices or irrelevant terms in the name, subtitle or keywords | Remove them; describe your own app. See [metadata rejections](https://uptika.app/en/guides/app-store-metadata-rejections) |
| 2.3.10 | Names, icons or imagery of other mobile platforms or alternative marketplaces | Remove them from metadata and screenshots, including status bars |
| 2.3.12 | A generic "What's New" for a significant change | List the new features specifically |
| 2.3.6 Age rating | A rating that does not match the content | Answer the questionnaire honestly. See [App Store age rating](https://uptika.app/en/guides/app-store-age-rating) |
| 3.1.1 In-App Purchase | Digital content unlocked by another payment method, or a link to buy outside the app where not permitted | Use in-app purchase for digital goods, or qualify for an entitlement or exception. See [Guideline 3.1.1](https://uptika.app/en/guides/guideline-3-1-1-in-app-purchase) |
| 3.1.2(a) Subscriptions | A subscription shorter than seven days, or one that does not work on all the user's devices | Offer periods of at least seven days that work everywhere the app is available |
| 4.1 Copycats | An app that copies another app's name, icon or interface | Make the identity your own; do not use another developer's brand without approval |
| 4.2 Minimum Functionality | A repackaged website, a collection of links or too little functionality | Add native features and lasting value. See [Guideline 4.2](https://uptika.app/en/guides/guideline-4-2-minimum-functionality) |
| 4.3 Spam | Multiple near-identical apps (4.3(a)) or an app in a saturated category with nothing new (4.3(b)) | Merge variants into one app; show what is meaningfully different. See [Guideline 4.3](https://uptika.app/en/guides/guideline-4-3-spam) |
| 4.8 Login Services | A third-party or social login as the main account method without an equivalent option | Also offer a login service that limits data to name and email, lets users hide their email and does not track for ads without consent |
| 5.1.1(i) Privacy policy | No privacy policy link in App Store Connect or in the app | Add both links; the policy must say what is collected, how and why, how third parties protect it, and how to delete data |
| 5.1.1(ii) Purpose strings | A permission prompt with a vague reason | Write one specific sentence per protected resource, localized |
| 5.1.1(v) Account sign-in | Forced login for an app without account features, or account creation without in-app deletion | Let people use non-account features without a login; offer account deletion inside the app. See [Guideline 5.1.1](https://uptika.app/en/guides/guideline-5-1-1-data-collection) |
| 5.1.1(ix) Regulated fields | Banking, health, gambling, crypto exchange or air travel submitted by an individual | Submit from the legal entity that provides the service, with documentation |

Not a guideline but a common blocker in the European Union: every developer must declare a trader status under the Digital Services Act, and traders' contact details are shown on the product page. See [DSA trader status](https://uptika.app/en/guides/dsa-trader-status-app-store).

## What should you do after a rejection? A decision tree

1. **Read the whole message.** Note every guideline it cites; one fix rarely covers two guidelines.
2. **Is it metadata only?** If the issue is in text or screenshots, fix it and resubmit. Apple says that after a metadata issue "you can resubmit the same build".
3. **Is it the build?** Fix it, upload a new build, and resubmit. In the submission you can edit rejected items once, or remove them and continue with the approved ones.
4. **Did the reviewer miss something?** Reply in App Store Connect with the clarification: where the feature is, a working demo account, a short screen recording. Many 2.1 issues end here.
5. **Do you disagree after replying?** Submit an appeal to the App Review Board. Cite the guideline and explain point by point how the app meets it. One appeal per rejected app; do not appeal after you have already resubmitted a fix.
6. **Is the app already live and this is a bug fix?** Apple says bug fixes for live apps "will not be delayed over guideline violations except for those related to legal or safety issues". If App Review offers this, reply that you accept and will address the issue in the next submission.
7. **Is timing critical?** You can request an expedited review for a critical bug fix or an event-related release. Reserve it for real urgency.

The full appeal procedure, with a template, is in [replying to App Review and appealing](https://uptika.app/en/guides/app-review-board-appeal).

## How do you reply to App Review in App Store Connect?

1. In Apps, select the app.
2. At the top of the page, click the link that says there are unresolved issues.
3. In the In Progress section, click Resolve next to the submission.
4. Click Reply to App Review, write your reply, attach files if useful, and click Reply.

A reply that works is short and specific:

> Hello App Review team. Thank you for the review of version 2.4 (build 118). Regarding Guideline 2.1: the sign-in screen needs an account, so we added a demo account to App Review Information (user: review@example.com, password in the notes). The feature you mentioned is under Settings > Sync; a 40-second screen recording is attached. The backend is live 24/7 during review.

Avoid long arguments, marketing language and references to other apps that "were approved"; the board judges your app against the guideline.

## What should you check before you submit?

Apple's own "Before You Submit" list from the guidelines, with the details that most often go wrong:

- **Test for crashes and bugs** on a real device with the latest OS.
- **Complete and accurate metadata**: no placeholder text, working URLs, a support URL with real contact details (Guideline 1.5).
- **Full access for the reviewer**: an active demo account or a fully featured demo mode. Demo credentials must work at submission; subscription apps should give an account with an expired subscription so the reviewer can see the whole purchase flow.
- **Backend services live** during review.
- **Review notes** that explain non-obvious features and in-app purchases. App Review notes can hold up to 4,000 bytes.
- **Documentation** for regulated features (medical, finance, gambling, third-party content rights).
- **Privacy**: privacy policy link in App Store Connect and in the app; purpose strings for every protected resource; in-app account deletion if users can create accounts.
- **Metadata hygiene**: no other apps' names, no prices in screenshots or name, no other platforms' names, screenshots that show the app in use.

## How is a Google Play rejection different?

Google Play works with Developer Program Policies rather than numbered guidelines, shows issues on the Policy status page in Play Console, and has a ladder of outcomes: rejection, removal, suspension and account termination, where suspensions count as strikes. The fixes and the appeal path are in [Google Play rejections and policy violations](https://uptika.app/en/guides/google-play-rejection-reasons).

## Where does Uptika fit?

Many metadata rejections can be caught before you submit. The free [Metadata Linter](https://uptika.app/en/tools/metadata-linter) checks your name, subtitle, keyword field and promotional text in your browser for other brands, "best", "#1", "free", prices, emoji, other platforms' names and placeholder text, the risks that Guideline 2.3.7 and 2.3.10 cover. In the panel, Sayfa denetimi (listing audit) runs a rejection-risk check on your live page's most visible text, and Rakip günlüğü (competitor log) shows how rivals in your category describe themselves. Uptika does not see your App Store Connect messages and cannot appeal for you. [Start free](https://uptika.app/app/#/?signup=1).

## Questions

### What are the most common App Store rejection reasons?

Apple says that on average over 40% of unresolved issues relate to Guideline 2.1 App Completeness: crashes, placeholder content, broken links, missing demo accounts and incomplete information. Other frequent citations are 2.3 Accurate Metadata (screenshots, keywords, other platforms' names), 4.2 Minimum Functionality (repackaged websites), 4.3 Spam, 5.1.1 Data Collection and Storage (privacy policy, purpose strings, account deletion) and 3.1.1 In-App Purchase.

### How do I appeal an App Store rejection?

First reply to the rejection message in App Store Connect with the clarification App Review needs. If that does not resolve it and you believe your app follows the guidelines, submit an appeal to the App Review Board, citing the specific guideline and explaining point by point how the app meets it. Submit one appeal per rejected app and address every cited guideline in it.

### What is the App Store rejection rate?

Apple does not give an overall rejection rate on its App Review pages. What it does publish is that it reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours, and that over 40% of unresolved issues relate to Guideline 2.1.

### Why did Apple reject my app?

The rejection message in App Store Connect names the guideline, often quotes it, and describes what the reviewer saw, sometimes with a screenshot. Start from that guideline number in the table on this page, fix the cause, and reply or resubmit.

### How do App Store and Google Play rejections differ?

App Store rejections arrive as messages tied to App Review Guidelines in App Store Connect, and you can reply in the same thread. Google Play sends policy notices tied to Developer Program Policies, shows them on the Policy status page, and has a separate ladder of rejection, removal, suspension and account termination. See the Google Play rejection guide for that side.

## Sources

- [App Review Guidelines (Apple Developer, last updated October 16, 2026)](https://developer.apple.com/app-store/review/guidelines/)
- [App Review (Apple Developer)](https://developer.apple.com/distribute/app-review/)
- [Overview of submitting for review (App Store Connect Help)](https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/overview-of-submitting-for-review)
- [Reply to App Review messages (App Store Connect Help)](https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/reply-to-app-review-messages)
- [Manage a submission with unresolved issues (App Store Connect Help)](https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/manage-a-submission-with-unresolved-issues)
- [Appeal to the App Review Board (App Review Help)](https://developer.apple.com/help/app-review/after-submitting-for-review/appeal-to-the-app-review-board)
- [Request an expedited review (App Review Help)](https://developer.apple.com/help/app-review/after-submitting-for-review/request-expedited-review)
- [Provide information for a complete review (App Review Help)](https://developer.apple.com/help/app-review/before-submitting-for-review/complete-review)
- [2.3.3 Show your app in use with screenshots (App Review Help)](https://developer.apple.com/help/app-review/guideline-reference/2-3-3-screenshots)
- [5.1.1(ii) Write clear purpose strings (App Review Help)](https://developer.apple.com/help/app-review/guideline-reference/5-1-1-purpose-strings)
- [Manage EU Digital Services Act trader requirements (App Store Connect Help)](https://developer.apple.com/help/app-store-connect/manage-compliance-information/manage-european-union-digital-services-act-trader-requirements)
- [App Store search: keywords (Apple Developer)](https://developer.apple.com/app-store/search/)

---

Uptika is an ASO and store-intelligence tool for the App Store and Google Play. https://uptika.app/en