Guideline 2.1(a) rejection: App Completeness

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 2.1 - Performance - App Completeness

In one line: The reviewer hit a crash, a dead button, placeholder text, or a login wall with no working demo account.

Usual next move: Fix, new build, then replySomething in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify.Based on how this guideline is usually resolved, not a prediction for your app.

Paste your rejection to check

On this page: Causes Fix Reply Real cases Questions

Common real causes

Backend was off, rate limited, or geo blocked during review
Demo account expired, needed 2FA, or was empty
Crash on a device you never tested (often iPad or the newest iOS)
Placeholder text, test buttons, or a dev URL left in the build
Support or privacy URL returns 404

How to fix it

Reproduce on the exact device and OS named in the rejection
Create a permanent demo account with no 2FA and sample data
Open every link in the app and metadata on cellular data
Check the iPhone app still runs cleanly on iPad

What to put in your reply

Thank them and name Guideline 2.1(a).
Say exactly what changed, and in which version and build.
Give a numbered path the reviewer can follow.
Attach proof: screenshots or a screen recording.

The full fill-in-the-blanks reply for 2.1(a) is in the Rescue Kit.

Real cases: others who got 2.1(a)

1 public case: 1 approved. Outcomes are what the developer posted.

ApprovedX · @xovist · Jul 10, 2026

2.1 App Completeness on an update, approved after resubmitting unchanged

Approved in about 4 hours, as stated.

Questions developers ask about 2.1(a)

What does a Guideline 2.1(a) rejection mean?

The reviewer hit a crash, a dead button, placeholder text, or a login wall with no working demo account.

Why do apps get rejected under Guideline 2.1(a)?

The most common real causes: backend was off, rate limited, or geo blocked during review; demo account expired, needed 2FA, or was empty; crash on a device you never tested (often iPad or the newest iOS); placeholder text, test buttons, or a dev URL left in the build; support or privacy URL returns 404.

How do I fix a Guideline 2.1(a) rejection?

1. Reproduce on the exact device and OS named in the rejection. 2. Create a permanent demo account with no 2FA and sample data. 3. Open every link in the app and metadata on cellular data. 4. Check the iPhone app still runs cleanly on iPad.

Do I need a new build for Guideline 2.1(a)?

Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 2.1(a)?

Reply in App Store Connect. Thank the reviewer and name Guideline 2.1(a), say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 2.1(a)?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

2.1 Information Needed 2.1(b) In-app purchases not found 2.5.2 Downloading or executing code 2.5.19 Hidden or undocumented features

Source: Apple's App Review Guidelines, section 2.1(a), as revised October 16, 2026. Last checked Oct 26, 2026. Always read the current official text. How we write these guides.