Rejection Decoder
Home / Guidelines / 2.1

Guideline 2.1 rejection: Information Needed

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

Subject line you may see: Guideline 2.1 - Information Needed

In one line: Nothing is broken. The reviewer wants more context, often a screen recording on a physical device, who the app is for, and how it makes money.
Usual next move: Reply, usually no new buildThe reviewer needs information, not a code change. Answer every question in one reply in App Store Connect.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: CausesFixReplyReal casesQuestions

Common real causes

How to fix it

  1. Answer every question, in the order asked, in one reply
  2. Record the full flow on a physical device
  3. Say who it is for, what it does, and how it makes money
  4. List external services and the data they receive

What to put in your reply

Thank them and name Guideline 2.1.
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 is in the Rescue Kit.

Real cases: others who got 2.1

No public cases logged yet.

Questions developers ask about 2.1

What does a Guideline 2.1 rejection mean?

Nothing is broken. The reviewer wants more context, often a screen recording on a physical device, who the app is for, and how it makes money.

Why do apps get rejected under Guideline 2.1?

The most common real causes: new developer account (very common in 2026); unclear business model or audience; features the reviewer could not reach without help.

How do I fix a Guideline 2.1 rejection?

1. Answer every question, in the order asked, in one reply. 2. Record the full flow on a physical device. 3. Say who it is for, what it does, and how it makes money. 4. List external services and the data they receive.

Do I need a new build for Guideline 2.1?

Reply, usually no new build. The reviewer needs information, not a code change. Answer every question in one reply in App Store Connect. 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?

Reply in App Store Connect. Thank the reviewer and name Guideline 2.1, 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?

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(a) App Completeness2.1(b) In-app purchases not found

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