Back to all posts
App Store Release7 min read·November 8, 2026

Why Apple Rejects iOS Apps: Common Reasons and Fixes

TB
ThynkBlox Apps Team
App Engineering

If Apple rejected your app, the cause is usually one of a few areas. The app crashed or broke during review. The store listing did not match the app. The reviewer could not sign in. The app's payment flow broke the store's rules. Or the privacy details were incomplete. Start with the rejection message: it names the area of concern. Then fix the root cause, not only the screen the reviewer happened to mention.

How should you read a rejection message?

The rejection notice explains what the reviewer saw and which part of the review guidelines it relates to. Some notices include screenshots or the steps the reviewer took. Read it as a bug report from a careful tester who has never seen your product before.

Before you change anything, work out three things:

  • What the reviewer tried to do. Which screen, account or feature were they using?
  • What they expected to see. A working feature, a description that matches the app, or a way to sign in?
  • Whether the issue happens elsewhere. If one screen fails, check the screens and flows built the same way.

If the message is unclear, reply through the review messaging channel and ask a specific question. Keep the reply short and factual, and describe what you checked.

What are the most common rejection reasons, and how do you fix them?

The table below covers the areas founders run into most often. Treat it as a pre-submission checklist as well as a repair guide.

Rejection areaWhat the reviewer usually sawHow to fix it
Crashes and bugsThe app closed on launch, froze, or a core feature failedReproduce the problem on a clean install, on current iOS versions and a range of devices. Fix it, then retest the full flow before you resubmit
Placeholder or unfinished contentTest text, empty screens, "coming soon" features or broken linksRemove unfinished features, or hide them behind a flag that stays off in the release build. Fill every screen a reviewer can reach
Incomplete or misleading metadataScreenshots, description or app name that do not match the appUpdate screenshots from the current build. Describe only features that exist. Check the support URL and privacy policy link work
No demo access for sign-inThe reviewer could not get past the login screenProvide a working demo account in the review notes. Make sure it never expires, needs no two-factor code sent to your phone, and comes with realistic data
Hardware or region dependenciesA feature needed a device, location or service the reviewer did not haveExplain the dependency in the review notes. Include a demo video or a demo mode that shows the feature
Payments for digital goodsDigital content or features were sold through an outside payment routeUse the store's in-app purchase system for digital goods and subscriptions where the rules require it. Physical goods and real-world services follow different rules
Subscription clarityPrice, billing period or what the user gets was unclearShow the price, renewal period and included features before purchase. Add a restore purchases option
Privacy detailsPrivacy labels did not match data collection, or no privacy policy was providedAudit what the app and its SDKs collect. Update the privacy answers and the policy so both match the build
Permission requestsThe app asked for camera, location or contacts access without a clear reasonAsk only when the feature needs it. Write purpose text that explains the real use
Account deletionUsers could create an account but not delete itAdd an in-app route to start account deletion, and explain what happens to the user's data
Minimal functionalityThe app was mainly a wrapped website or offered little beyond one pageAdd features that make sense on a phone, or reconsider whether an app is the right format

Why do crashes still reach the reviewer?

Most crashes that reach review never showed up in the team's own testing. Reviewers install the app fresh. They may use a device or iOS version you did not test, and a network that behaves differently from your office connection.

Common causes include:

  • Code that assumes data from a previous session already exists.
  • A backend pointed at staging, or a staging server that was switched off.
  • A feature that breaks when a permission is denied.
  • Slow or dropped network requests with no error handling.

Test a clean install on more than one device. Deny every permission at least once, and try the app on a slow connection. Our guides on testing mobile apps on slow networks and keeping staging and production separate cover the setup that prevents most of these surprises.

What should the review notes include?

Review notes are your chance to remove guesswork. A reviewer who has to guess how the app works is more likely to reject it.

Include:

  • Demo credentials for each user role that matters, such as a customer and an admin, if both are reachable in the app.
  • Steps to reach key features, especially anything behind a setup flow or a paid tier.
  • Explanations of anything unusual, such as features limited to one region, companion hardware or invite-only access.
  • A contact who can answer questions quickly during the review.

If your app has several roles, our guide to planning user roles and permissions helps you decide which demo accounts the reviewer needs.

How do payment rules cause rejections?

Payment rejections usually come from mixing two kinds of purchase. Digital content, premium features and subscriptions used inside the app generally have to go through the platform's in-app purchase system. Physical goods and services delivered in the real world, such as food delivery or a booked appointment, generally use an ordinary payment gateway.

Trouble starts when an app sells digital features through a web checkout, or links users to outside payment in a way the current rules do not allow. Apple's rules on links to outside payment differ by storefront, and the options allowed vary by region. Check the current guidelines before you design the flow rather than relying on older advice.

For the wider decision, see choosing a mobile app payment integration. If you sell subscriptions, also read designing an app subscription paywall.

Why do privacy answers get apps rejected?

Apple asks you to declare what data the app collects and how it is used. The reviewer compares those answers with how the app behaves. Mismatches usually come from third-party SDKs for analytics, advertising or crash reporting that collect more than the team realised.

To fix this:

  1. List every SDK in the build and check its own data collection documentation.
  2. Match your privacy answers and privacy policy to the actual build, not to plans.
  3. Make sure permission requests explain the real purpose in plain words.
  4. Confirm that users can delete their account from inside the app if they can create one there.

Related guides: evaluating third-party SDKs, designing permission requests and designing an account deletion flow.

What common mistakes make a second rejection more likely?

Fixing only the reported screen. If one flow broke, similar flows may break the same way. Check them all.

Resubmitting without retesting. A fast fix can bring in a new crash. Run the core flows again on a clean install.

Letting the demo account expire. Accounts that time out, get locked or rely on a code sent to a team member's phone are a frequent cause of repeat rejections.

Updating the build but not the metadata. If you removed a feature to pass review, remove it from the description and screenshots too.

Arguing instead of explaining. If you think the reviewer misunderstood, a clear explanation with steps or a short video works better than a debate.

When does this guidance not apply?

This article covers the common, fixable reasons for rejection. It does not cover appeals. It also does not cover apps in regulated categories such as health, finance, gambling or apps for children, which face extra requirements. If your app falls into one of those categories, review the specific rules for it, and get legal advice where needed, before you submit.

If you also publish on Android, the review process differs in important ways. Our guide to common reasons Google Play rejects an app covers that side.

What questions do founders often ask?

Does a rejection affect future submissions?

A rejection on its own is a normal part of the process. Fix the issue properly and resubmit. Repeated rejections for the same unresolved problem waste time and may lead to closer review.

Can I submit a build with features still in development?

Only if those features are fully hidden in the release build. Reviewers check what they can reach, so anything visible should work.

Do updates get reviewed too?

Yes. Each new version goes through review, so an update can be rejected even if earlier versions were approved. Keep the pre-submission checks in this article as part of every release. For planning releases after launch, see what app maintenance involves after launch.

Should I build for iOS and Android at the same time?

It depends on your audience and budget. Our comparison of Flutter and React Native for a first app explains how a shared codebase affects releasing on both stores.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.