Skip to content

Guideline 2.1 App Completeness rejection: what it means and how to fix it

What guideline 2.1(a) and 2.1(b) say, the causes we see behind them, how to fix each one, what to write back to App Review and a checklist so it doesn't happen again.

By our team. Published . 6 sources.

A guideline 2.1 rejection means App Review could not finish reviewing your app as a complete, working product. Usually it crashed or hit an obvious bug on the reviewer's device, contained placeholder content or a dead link, could not be signed into, or had in-app purchases the reviewer could not find or buy. The fix is nearly always to correct the specific thing the reviewer hit, fill in App Review Information properly, and reply with exact steps to reach every feature.

It is the most common rejection there is. Apple says that "on average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more" [2]. The good news is that it is also one of the most fixable.

Send us your rejection

Paste what App Review sent you. We read it against the guideline and reply with what it will take and a fixed price, the same working day if it reaches us before 2pm UK time. Free, and no access needed yet.

We use your details only to reply about this; see our privacy notice.

What does guideline 2.1 say?

Guideline 2.1 sits under section 2, Performance, and currently has two parts [1].

2.1(a) covers the app as a whole: "Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app's full features and functionality. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems" [1].

2.1(b) covers in-app purchases: "If you offer in-app purchases in your app, make sure they are complete, up-to-date, visible to the reviewer and functional. If any configured in-app purchase items cannot be found or reviewed in your app, explain the reason in your review notes" [1].

So when a rejection cites "Guideline 2.1 - Performance - App Completeness", read the reviewer's description to see which half they mean. A crash, a broken link or a login wall is 2.1(a). A paywall that wouldn't load, or a subscription configured in App Store Connect that the reviewer couldn't find in the app, is 2.1(b).

Why was my app rejected under 2.1?

These are the causes we see most often in the 2.1 rejections we fix, roughly in order of how often they come up.

What the reviewer sawThe usual causeThe fix
The app crashed on launch or in a main flowA device, iPad or OS version the team never tested on; a missing permission string; a server or feature flag that behaved differently for reviewGet the crash log, reproduce on the same device type and iOS version, fix and test the exact build
"We were unable to sign in"Demo account expired, password changed, two-factor code needed, or the account was lockedA permanent review account, codes in the notes, back end switched on
The app showed an error or an empty screenBack end down, test server switched off, data only seeded in your regionKeep services live through review and check regional behaviour
Placeholder text or imagesLorem ipsum, "TODO", test products or "coming soon" screens left inRemove them, in every language
A link did nothing or led to an error pageSupport URL, privacy policy URL or an in-app web link brokenClick every link in the app and the listing
In-app purchases could not be foundPaywall only shown after onboarding, after a trial, or in certain regionsExplain the exact path in the review notes
A purchase failed or the products did not loadPaid Apps Agreement not active, products not submitted, or not tested in the sandboxFix the App Store Connect set-up and test in the sandbox
On iPad, the layout was brokenAn iPhone app the reviewer ran on iPadTest on iPad, even if you didn't design for it

A few of these deserve more detail.

Crashes and obvious bugs

Apple's own advice is to "thoroughly test on devices running the latest software and fix all bugs before submitting" [2]. Its App Review help adds that reviewers evaluate apps "the way your users will use them: installed on real devices and connected to networks with real-world conditions" [5]. An iPhone app that doesn't depend on iPhone-only hardware can be downloaded onto iPad, and Apple notes that removing iPad as a supported destination in Xcode "won't change that app's availability on iPad" [5]. So if you haven't opened your iPhone app on an iPad, that is the first place to look.

Missing or broken review access

If your app has accounts, Apple asks for "either an active demo account or fully-featured demo mode" [1]. Its help pages go further: the username and password must "work at the time of submission", and "credentials that expire or change before your review starts may result in the submission being rejected" [3]. If the app needs a code as well as a password, put it in the Notes field in advance; otherwise "a call may be required to continue the review", and those calls are "typically completed within three to five business days" [3]. A login that needs a text message to your own phone is one of the slowest ways to lose a week.

In-app purchases the reviewer couldn't find or buy

Reviewers test purchases in the sandbox. Apple says: "The Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect, then confirm the agreement is in effect. Paid In-App Purchases won't function in review until this agreement is active" [4]. If you show the paywall only in certain storefronts or device set-ups, Apple asks you to say so in the review notes [4]. For subscriptions, Apple suggests providing "a demo account with an expired subscription to enable review of the entire purchase flow" [3].

Hardware and hard-to-reproduce set-ups

If the app pairs with a device, Apple asks for "a video (not a screen recording) that shows your app running on a physical Apple device as it pairs and interacts with the hardware" [3]. On its main App Review page it says that where features need hardware or an environment that is hard to replicate, you should "be prepared to provide a demo video or the hardware" [2].

When App Review asks for information instead of rejecting

Sometimes the message doesn't reject the build outright but asks questions first, citing 2.1: what the app does, who it is for, how to reach a feature, or for a demo video. Treat it exactly like a rejection. Answer every question, attach what was asked for, and don't resubmit until you have replied. Apple's appeal guidance also asks you to "respond to any requests for additional information before submitting an appeal" [2].

How do I fix it?

  1. Read the message for the specific symptom. It usually names the device, the iOS version and what happened. If a crash log is attached, symbolicate it before changing any code.
  2. Reproduce it on the same kind of device. Use the device type and iOS version the reviewer used, and install the build through TestFlight, not from Xcode, so you are testing what Apple tested.
  3. Fix the cause, then look for its siblings. If one link was dead, check every link. If the paywall failed in one place, test every entry point to it.
  4. Fill in App Review Information properly. Apple's help lists what it wants: the app's concept and business model, purpose and audience, "Devices and OS versions tested", external services the app relies on, required hardware and regional differences [3].
  5. Check the App Store Connect side of purchases. Paid Apps Agreement active, products in Ready for Review and submitted with the build, and each one tested in the sandbox [4].
  6. Upload a new build if code changed, then reply. If nothing in the app needed to change, for example the reviewer simply couldn't find the paywall, you can often reply with better instructions and ask for the same build to be reviewed again.

What should I write in the reply to App Review?

Use Reply to App Review in App Store Connect. Apple asks you to "be specific about what you're asking, such as the exact feature, guideline, or step you need clarified" and to "provide additional information that can help App Review understand the app's concept and intended functionality" [6]. Don't use the reply to appeal or to ask for an expedited review; those have their own forms [6].

A good 2.1 reply is short, factual and testable. For example:

Three things make the difference: say what was wrong in one sentence, say which build fixes it, and give click-by-click steps to every feature and purchase.

How do I stop it happening again?

Most 2.1 rejections come from the gap between the build you tested and the conditions the reviewer meets: a different device, a fresh install, no data, a different region, an account that has since changed. Close that gap before each submission.

  • Test the archived build from TestFlight on a real iPhone and a real iPad with the latest iOS, from a fresh install.
  • Walk every main flow with no data, with permissions denied and on a slow network.
  • Keep a permanent review account whose password nobody changes, with a lapsed subscription if you sell one.
  • Describe new features "with specificity" in the review notes; guideline 2.3.1(a) says "generic descriptions will be rejected" [1].
  • Keep your back end, test servers and feature flags live for the whole review, in every region you sell in.

Pre-submission checklist for guideline 2.1

  • The exact build has been installed from TestFlight and tested on a real iPhone and iPad with the latest iOS.
  • No placeholder text, test data, "coming soon" screens or lorem ipsum, in any language.
  • Every link works, including the support URL and privacy policy.
  • App Review Information has a working demo account (or an approved demo mode), any codes, and the devices and iOS versions you tested on.
  • The back end and any third-party services will be live during review.
  • The Paid Apps Agreement is active and every in-app purchase is Ready for Review, submitted with the build and tested in the sandbox.
  • The review notes give the exact path to the paywall and to every non-obvious feature.
  • If the app works with hardware, a video of it running on a physical device is attached.
  • If anything differs by region, the notes say so.

Questions we get asked

What is the difference between guideline 2.1(a) and 2.1(b)?
2.1(a) covers the app as a whole: crashes, obvious bugs, placeholder content, broken URLs and missing demo account information. 2.1(b) covers in-app purchases: they must be complete, up to date, visible to the reviewer and working, and if any can't be found you must explain why in the review notes.
Do I need to upload a new build after a 2.1 rejection?
Only if the app itself needs to change, for example to fix a crash or remove placeholder content. If the reviewer couldn't sign in or couldn't find a feature, updating App Review Information and replying with clear steps is often enough without a new build.
What if my app can't give App Review a demo account?
Guideline 2.1(a) allows a built-in demo mode instead of a demo account if you can't provide one for legal or security reasons, but only with prior approval from Apple, and the demo mode must show the app's full features and functionality.
Why can't the reviewer see my in-app purchases?
The most common reasons are that the Paid Apps Agreement isn't active, the products weren't submitted with the build, the products weren't tested in the sandbox, or the paywall only appears after a step the reviewer didn't take. Apple says paid in-app purchases won't work in review until the Paid Apps Agreement is in effect.
My app is iPhone-only. Why did it fail on iPad?
An iPhone app that doesn't depend on iPhone-only hardware can still be downloaded onto iPad, and reviewers may test it there. Apple says removing iPad as a supported destination in Xcode won't change that. Test the app on an iPad before submitting.
Should I appeal a 2.1 rejection?
Rarely. A 2.1 rejection usually describes something the reviewer actually saw. Fix it or explain it in a reply. Appeal only if you can show the app worked as submitted and the reviewer misunderstood it, and answer any outstanding questions from App Review first.

Sources

Checked on 17 November 2026.

  1. 1.Apple Developer, "App Review Guidelines" (2.1(a), 2.1(b), 2.3.1(a), Before You Submit; last updated 16 October 2026): https://developer.apple.com/app-store/review/guidelines/
  2. 2.Apple Developer, "App Review" (avoiding common issues, appeals): https://developer.apple.com/distribute/app-review/
  3. 3.Apple Developer, App Review Help, "Provide information for a complete review": https://developer.apple.com/help/app-review/before-submitting-for-review/complete-review
  4. 4.Apple Developer, App Review Help, "Configure In-App Purchases for review in the sandbox": https://developer.apple.com/help/app-review/before-submitting-for-review/configure-in-app-purchases
  5. 5.Apple Developer, App Review Help, "Test your app on compatible devices": https://developer.apple.com/help/app-review/before-submitting-for-review/test-compatible-devices
  6. 6.Apple Developer, App Review Help, "Contact App Review for help with a submission": https://developer.apple.com/help/app-review/after-submitting-for-review/contact-app-review

Planning something similar?

Tell us what you're building. We'll give you an honest view of cost and timing, and the simplest way to start.