GUIDE  ·  11-Minute Read

App Store Rejection Reasons: How to Fix Them, When to Resubmit and How to Appeal

By Zaib Un Nisa Azam

Most App Store rejections come from a short list of App Review Guidelines: apps that crash or cannot be fully reviewed (2.1), metadata that does not match the app (2.3), copies and thin apps (4.2 and 4.3), privacy gaps such as missing account deletion (5.1.1), and social login without an equivalent private option (4.8). Each one has a clear fix. This guide explains them, using Apple’s own guidelines, help pages and its 2025 App Store Transparency Report, and covers when to reply to App Review, when to resubmit and how to appeal.

Illustration of an app install curve rising across plotted measurement points
  • Apple reviewed 9,100,620 app submissions and rejected 2,093,244 in its 2025 transparency report.
  • Performance guidelines (section 2, including app completeness and metadata) account for the most rejections: 1,354,418.
  • Fix crashes, placeholders and login walls first: give App Review a working demo account and live backend.
  • If App Review only asks for information, reply in App Store Connect. Resubmitting starts a new review.
  • Appeal to the App Review Board only after replying, and name the guideline and how your app meets it.
  • Apple aims to review 50% of submissions in under 24 hours and 90% in under 48 hours.

How often does Apple reject apps, and why?

Often. Apple’s 2025 App Store Transparency Report lists 9,100,620 app submissions reviewed and 2,093,244 rejected, about 23%. The largest group by far is Performance, section 2 of the guidelines.

The transparency report breaks rejections down by guideline section. A submission can break more than one guideline, so the sections add up to more than the total.

  • Performance (section 2): 1,354,418. Crashes, incomplete apps, inaccurate metadata and software requirements.
  • Legal (section 5): 495,673. Privacy, data collection and intellectual property.
  • Design (section 4): 415,532. Apple’s footnote says this includes copycat, minimum functionality and spam.
  • Safety (section 1): 151,159. Objectionable content, user-generated content and user safety.

The same report lists 387,087 app submissions approved after rejection. A rejection is usually a list of things to fix, not the end of the app.

Guideline 2.1 App Completeness: why crashes and login walls get rejected

Guideline 2.1 rejects apps that crash, show obvious technical problems, contain placeholder content, or cannot be fully reviewed. The fix is a tested final build, a working demo account and a live backend.

The App Review Guidelines say submissions should be final versions with all metadata and working URLs, and that placeholder text, empty websites and other temporary content should be removed. Apple will “reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.”

  1. Test the release build on physical devices, not only the simulator, and on the oldest iOS version you support.
  2. Remove every placeholder: lorem ipsum, “coming soon” screens, dead buttons and links that go nowhere.
  3. Add demo account credentials that work at submission time. Apple’s complete review guidance warns that credentials that expire or change before review starts may get the submission rejected.
  4. If the app has several account types, such as admin and standard user, add credentials for each in the Notes field.
  5. If login needs a one-time code, put it in the Notes field in advance. Apple says otherwise a call may be needed, typically completed within three to five business days.
  6. Keep the backend, staging APIs and third-party services switched on and reachable for the whole review.
  7. If the app depends on hardware, provide a video of it running on a physical Apple device as it pairs with the hardware. Apple asks for a video, not a screen recording.

What should you do when App Review asks for more information?

Reply to the message in App Store Connect with what was asked for. Do not resubmit: Apple says resubmitting starts a new review, after which App Review can no longer reply to your earlier message.

Apple’s review status guidance says it is not necessary to resubmit when App Review requested more information and there are no other issues. Some issues can also be fixed without a new build, by changing metadata or making server-side changes such as providing or activating demo credentials; then you reply to App Review once the changes are made.

You can prevent most of these requests by filling in App Review Information properly the first time: what the app does and who it is for, what changed in this version and where to find it, the devices and iOS versions you tested on, and the external services the app relies on, such as authentication or AI services.

Guideline 2.3 Accurate Metadata: screenshots, names and descriptions

Your App Store listing must match the app. Screenshots must show the app in use, the name must be 30 characters or fewer, and new features must be described specifically in the Notes for Review.

  • Screenshots (2.3.3): Apple’s screenshot guidance says they should show the app in use, not only the title art, login page or splash screen.
  • Notes for Review (2.3.1): new features and changes must be described specifically; Apple says generic descriptions will be rejected.
  • App name and keywords (2.3.7): names are limited to 30 characters, and metadata must not be stuffed with trademarked terms, popular app names or other irrelevant phrases.
  • Other platforms (2.3.10): do not show names, icons or images of other mobile platforms in the app or metadata unless there is specific, approved functionality.
  • Misleading claims (2.3.1): do not promote content or services the app does not actually offer.

Guideline 4.3 Spam and 4.2 Minimum Functionality: how to avoid design spam rejections

Guideline 4.3 rejects apps that duplicate your own apps or are indistinguishable from what is already widely available; 4.2 rejects apps that are little more than a repackaged website. The fix is a clearly different, app-like product.

  • 4.3(a): do not create multiple Bundle IDs of the same app. Apple’s example is a separate app for every city; it suggests submitting a single app instead.
  • 4.3(b): Apple names dating, flashlight, sound effects, wallpaper, simple timers and fortune telling as well-established categories, and says it will not accept new submissions in them unless they offer a meaningfully different or improved experience.
  • 4.2: the app should have features, content and UI that elevate it beyond a repackaged website. Apart from catalogs, apps should not primarily be marketing material, web clippings or a collection of links.
  • 4.1 Copycats: do not copy a popular app with minor changes, or use another developer’s icon, brand or product name without their approval.

Template and white-label apps need extra care. Guideline 4.2.6 says apps created from a template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content, and that these services should not submit apps on behalf of their clients. So a client’s app belongs on the client’s own developer account, with its own content and features, and the review notes should say who the app is for and what makes it different. Apple also warns that repeated submissions of low-effort apps may lead to removal from the Apple Developer Program.

For a web wrapper rejected under 4.2, add what only an app can do well: offline access, push notifications users opt into, device features such as the camera or location, and native navigation instead of a website in a frame.

Guideline 5.1.1: privacy policy, permissions and account deletion

Every app needs a privacy policy linked in App Store Connect and inside the app, clear purpose strings for each permission, and, if users can create an account, a way to delete it from within the app.

  • Privacy policy (5.1.1(i)): linked in the App Store Connect metadata field and inside the app, easy to find. It must say what data you collect, how and why, confirm that third parties receiving user data protect it to the same standard, and explain retention, deletion and how users revoke consent.
  • Permissions (5.1.1(ii)): apps must get consent before collecting user or usage data, give an easy way to withdraw it, and use purpose strings that clearly and completely describe how the data is used.
  • Login (5.1.1(v)): if the app has no significant account-based features, let people use it without logging in.
  • Tracking (5.1.2): tracking needs the user’s explicit permission through App Tracking Transparency, and the app may not require users to enable push notifications, location or tracking to use it.

Account deletion is one of the easiest rejections to avoid. Apple’s account deletion guidance says apps that support account creation must let people start deleting their account inside the app. Only offering to deactivate the account is not enough. A link straight to the deletion page on your website is allowed if people need to finish there. Apps outside highly regulated industries should not make people phone, email or use a chat support flow to delete their account.

Guideline 4.8 Login Services: when you need another login option

If the app uses a third-party or social login, such as Google Sign-In or Facebook Login, for the user’s main account, it must also offer an equivalent login option that limits data to name and email, lets users keep their email private and does not collect app interactions for advertising without consent.

The guideline lists cases where another login service is not required, including when:

  • The app only uses your company’s own account setup and sign-in.
  • It is an education, enterprise or business app that needs an existing education or enterprise account.
  • It uses a government or industry-backed citizen ID or electronic ID.
  • It is a client for a specific third-party service, and users sign in to that service directly to reach their content.

Reply, resubmit or appeal: which one should you do?

Reply when App Review needs information or a metadata or server-side change. Resubmit when the problem was in the build and you have fixed it. Appeal only when you believe the app already follows the guidelines.

  • Reply: answer in App Store Connect. Use this for questions, demo credentials, documentation, and metadata or server-side fixes.
  • Resubmit: upload the fixed build. Apple says this starts a full review of the new build, and warns: do not resubmit until every issue is resolved, because unresolved issues delay review and lead to the same outcome.
  • Appeal: ask the App Review Board to look again. If you resubmit while an appeal is open, the appeal is closed.

Already live and need a bug fix out? The guidelines say that for apps already on the App Store, bug fixes will not be delayed over guideline violations except those related to legal or safety issues. Use App Store Connect to tell App Review you would like to take advantage of this, and plan to fix the guideline issue in your next submission.

How do you appeal an App Store rejection?

First reply to the rejection in App Store Connect with your clarification. If that does not resolve it, submit an appeal to the App Review Board that cites the specific guideline and explains how your app meets it.

  1. Reply to the rejection message first. Apple’s appeal guidance asks you to do this before filing an appeal.
  2. Use Apple’s Submit an appeal form (sign-in required) and describe why the app follows the App Review Guidelines.
  3. Point to the specific requirement in the rejection and explain, with facts, how the app satisfies it. Screens, test steps and documentation help.
  4. If the rejection cites several guidelines, address all of them in the same appeal. Submit only one appeal per rejected app.
  5. Do not use an appeal to ask for a status update, an expedited review or to answer an information request; Apple has separate contact forms for those.

How long does App Store review take?

Apple aims to review at least 50% of submissions in under 24 hours and 90% in under 48 hours. Apps with little or no review history, apps that need documentation and complex or novel issues can take longer.

For a critical bug fix or a release tied to an event, you can request an expedited review after the submission is already with App Review. Apple asks that these requests be kept for genuine urgency.

App Store submission checklist

Run through this list before every submission. It covers the guidelines behind most rejections in this guide.

1 of 4Build and access (2.1)
2 of 4Listing (2.3)
3 of 4Design (4.2, 4.3, 4.8)
4 of 4Privacy (5.1)

0 of 14 done

Ticking a box records your own check. App Review decides against the current App Review Guidelines.

Launching on Android too? Read Google Play’s 12 testers for 14 days rule. For apps used with poor connectivity, see offline-first mobile apps, and if you are building the team, how to hire Flutter developers. The ServiPR, Just Dry Cleans and Bix Delivery case studies show apps Sigi has shipped to the App Store. Sigi’s iOS app development and mobile app development pages cover this work.

Questions this guide answers

Apple’s 2025 transparency report shows Performance guidelines (section 2) cause the most rejections, followed by Legal (section 5) and Design (section 4). In practice that means crashes and incomplete apps (2.1), inaccurate metadata (2.3), privacy gaps such as missing account deletion (5.1.1), spam or thin apps (4.2 and 4.3), and social login without an equivalent option (4.8).

It means App Review cannot finish the review without more from you, such as demo credentials, an explanation of a feature or documentation. Reply in App Store Connect with what was asked for. Apple says you do not need to resubmit when it only requested more information.

Make the app meaningfully different. Combine duplicate apps into one app, avoid crowded categories unless you offer a clearly better experience, and explain in the review notes who the app is for and what makes it unique. Template apps reused for many clients need real, distinct content and features.

Reply to the rejection in App Store Connect first. If that does not resolve it, use Apple’s appeal form to the App Review Board, cite the specific guideline and explain how your app meets it. Submit one appeal per app and address every cited guideline in it.

Apple aims to review at least 50% of submissions in under 24 hours and 90% in under 48 hours. Some submissions take longer, and you can request an expedited review for genuinely urgent cases such as a critical bug fix.

Yes. Sigi builds iOS and Android apps and can review a rejected app against the App Review Guidelines, fix the issues and handle the resubmission on your own developer account. Examples include ServiPR, Just Dry Cleans and Bix Delivery.