DEV Community

Cover image for App Store rejection reasons: 11 fixes before you resubmit
ExtensionBooster
ExtensionBooster

Posted on Originally published at appranker.net

App Store rejection reasons: 11 fixes before you resubmit

Originally published on AppRanker.

Most App Store rejection reasons come from a short list of guidelines, and most of them are things you can catch on your own machine before App Review ever opens your build. Below is the data on where rejections actually land, a fix table you can run through before each submission, and the reply-or-resubmit decision once a rejection arrives.

Where rejections actually come from

Apple's 2025 App Store Transparency Report puts numbers on the problem. Out of 9,100,620 submissions reviewed, 2,093,244 were rejected. That is roughly one build in four. The good news: 387,087 of those were approved after an initial rejection, so a rejection is usually a round trip, not a dead end.

Here is how the rejections split by guideline section:

Guideline section Rejections
2.x Performance 1,354,418
5.x Legal 495,673
4.x Design 415,532
3.x Business 283,820
1.x Safety 151,159

Performance dominates, and inside it one rule stands out. Apple's App Review page says more than 40% of unresolved issues relate to Guideline 2.1, App Completeness. In practice that means crashes, missing login details, placeholder screens and broken links, not exotic policy edge cases.

Read the message before touching code

Before you open Xcode, check three things in the rejection itself:

  1. Which guideline and sub-section is cited. "2.1(a)" and "2.1(b)" need completely different fixes.
  2. Whether it is really a question. An "Information Needed" status means the reviewer wants an answer, not a new binary.
  3. Whether a Bug Fix Submission is offered. That changes your timeline, covered further down.

The 11 fixes, as a pre-flight table

Treat this as a checklist for every release, not just the first one.

# Guideline What gets flagged What to do before submitting
1 2.1(a) Crashes and bugs Fresh install of the release build on a real device running the latest iOS. Test offline, with permissions denied, on both iPhone and iPad. Review crash reports in Xcode Organizer or TestFlight.
2 2.1, 2.3.1(a) No demo account or review info Put working credentials, setup steps and any hardware or location needs in App Review Information. Describe new features specifically.
3 2.1, 5.1 Placeholders, dead links, no privacy policy Click every link, including Support and Privacy Policy URLs. The policy should cover what you collect, why, who you share it with, how long you keep it and how users request deletion.
4 2.1(b), 3.1.1 In-app purchase problems Submit IAP products together with the build, make sure the reviewer can reach the paywall, add a Restore button and drop any license-key unlocks.
5 5.1.1(ii) Vague permission prompts Write a specific, localized purpose string for every permission, including ones your SDKs trigger.
6 5.1.1(v) No in-app account deletion Put Delete account in settings. Deactivation does not count. If you use Sign in with Apple, revoke the tokens through the REST API.
7 4.8 Social login with no equivalent Offer a privacy-focused option such as Sign in with Apple next to third-party logins. Not needed if you only use your own account system.
8 2.3.3 Screenshots that don't show the app More than half of each device's screenshots must show the app in use: with three screenshots, two must be real screens; with four, three must be.
9 4.2, 4.2.2 Thin app or wrapped website Add native value: offline use, notifications, widgets, App Intents, sharing, camera or health integrations.
10 4.3(a), 4.3(b) Spam and duplicates Merge per-city or per-team Bundle ID variants into one app. A flashlight or timer clone needs a meaningfully different experience.
11 4.1 Copycat names and keywords Remove competitor or trademarked names from the name, subtitle, keywords and screenshots.

Fix 5 is the easiest to get wrong, so here is what a usable purpose string looks like in Info.plist. The wording below is an illustration; the rule is to name the feature and what the user gets from it:

<key>NSLocationWhenInUseUsageDescription</key>
<string>Your location is used to show coffee shops within walking distance on the map.</string>
Enter fullscreen mode Exit fullscreen mode

Compare that with a bare "To use location.", which is the kind of string that gets flagged. Remember to localize it for every language your listing supports.

Rejected anyway? Choose the cheapest path

Not every rejection needs a new build. Work through these in order:

  • Reply first. Many "Information Needed" rejections close with a reply in App Store Connect and no new binary.
  • Use a Bug Fix Submission if offered. For an update to an already-approved app, and for issues that are not legal or safety related, Apple may let you ship now and fix the issue in the next update. You cannot defer the same issue twice.
  • Appeal only when you believe you comply. Reply to the reviewer first, then file one appeal per app with the App Review Board and answer each guideline point by point.
  • Request expedited review only when it is urgent. A critical bug fix or a date-bound event qualifies; put the reason in the Notes field.
  • Talk to App Review before submitting. You can request a 30-minute Webex appointment on Tuesdays and Thursdays. It will not preapprove your app, but it can settle a guideline question early.

For context on timing, Apple's stated targets are at least 50% of submissions reviewed in under 24 hours and 90% in under 48 hours, so a clean resubmission rarely costs more than a day or two.

Key takeaways

  • Roughly one in four submissions gets rejected, and Performance (2.x) accounts for the largest share.
  • Guideline 2.1 App Completeness is behind more than 40% of unresolved issues: crashes, missing demo accounts, dead links.
  • A demo account, a real privacy policy URL and specific purpose strings prevent a large share of avoidable rejections.
  • Account deletion (5.1.1(v)) and an equivalent login option (4.8) are hard requirements, not nice-to-haves.
  • Read the cited sub-section first; a reply often beats a rebuild.

The original post has the full 12-item pre-submission checklist, a sample App Review notes block and an FAQ: see the complete guide to App Store rejection reasons and fixes. Once you are approved, you can also list your app on the AppRanker app leaderboard to help people find it.

Which guideline has rejected your app most often, and what finally got it through review? Share it in the comments.

Top comments (1)

Collapse
 
mosmox_studio profile image
Mosmox Studio •

Great checklist. One item I'd add as #12 right now: the age rating questionnaire. Since 16 November App Store Connect asks two new questions (Shared Location and Dating and Relationships), and every app has to answer them by 12 January 2027. The questions pop up exactly when you submit an update, so an unanswered questionnaire can stall a release that is otherwise ready. Worth checking side features too: a courier seeing a customer's location or DMs between strangers can change the answer, and dating features mean a minimum 18+.