· 12 min read · Nadeera Silva
Guideline 2.1 Information Needed: How to Get Approved
What App Store Guideline 2.1 Information Needed asks for on a new app, how to reply without a new build, and how it differs from App Completeness.

You submit your first app and App Store Connect shows Unresolved Issues with a message titled "Guideline 2.1 - Information Needed". Nothing is broken yet. Apple cannot finish the review without more from you: a working demo account, a code for your OTP login, a screen recording, or plain answers about what the app does. This post explains what the guideline 2.1 information needed message asks for, how I answer it so the review continues on the same build, and how it differs from the "Guideline 2.1 - Performance - App Completeness" rejection that does need a new build.
Quick answer
"Guideline 2.1 - Information Needed" means App Review paused your submission because it is missing something it needs to test the app, not because the app failed. Answer every numbered point with Reply to App Review in App Store Connect, attach what they asked for (often a screen recording from a physical iPhone), fix anything server side such as an expired demo account, and do not upload a new build unless the code has to change. Apple says resubmitting starts a new review, after which App Review can no longer reply to your previous message.
What this means for your app or business
This message is a delay, not a verdict. The app is waiting on you.
- Cost: usually a few hours of a developer's time to record a video, set up a reviewer account and write clear notes. No rebuild, no new release.
- Risk: each slow or incomplete reply adds another review round. Apple says it reviews 50% of submissions in under 24 hours and 90% in under 48 hours, but new developer accounts with little review history can take longer.
- Timeline: if the reply answers everything, the review normally continues from where it stopped. If App Review needs a call because your login needs a code it does not have, Apple says calls are typically completed within three to five business days.
- When to get help: if you got the same request twice, your login uses SMS codes, or the message also mentions crashes or in-app purchases.
What is the "Guideline 2.1 - Information Needed" message?
Guideline 2.1 is App Completeness. Part (a) says submissions should be final, tested on a device, and should "include demo account info (and turn on your back-end service!)" if the app has a login. Part (b) says in-app purchases must be complete, visible to the reviewer and functional, and that you should explain in the review notes if a configured item cannot be found in the app (App Review Guidelines, 2.1).
The "Information Needed" variant is how App Review asks for what is missing before it can apply that guideline. For new apps, the version developers have posted in 2026 asks for a list of items in one go. In a June 2026 r/iosdev thread, the message opens by saying App Review needs additional information to continue the review of this new app, then asks for:
- A screen recording on a physical device running the latest OS, starting from app launch and covering sign up, login, account deletion, purchases, user-generated content with reporting and blocking, and permission prompts, where the app has them.
- The device models and OS versions you tested on.
- The app's purpose, target audience and the problem it solves.
- Steps to reach the main features, with login credentials or sample files.
- The external services the app depends on, such as authentication, payments, data providers or AI services.
- Any regional differences, or confirmation that the app works the same everywhere.
- Documents proving you are authorised, if the app is in a regulated field or uses protected third-party material.
That list matches Apple's own complete review page almost item for item, so I use that page as the template for every first submission.
Why does App Review send it?
The usual triggers, from Apple's help pages and developer reports:
- No demo account, or one that stopped working. Apple says credentials that expire or change before the review starts may get the submission rejected, and the App Store Connect field help says the demo account "must not expire" (platform version information).
- The login needs a one-time code. If sign-in needs an SMS or email code, Apple asks you to put it in the Notes field in advance. Without it, a call may be required.
- The backend is not reachable. A sleeping staging server, an IP allowlist or a geo block looks like a broken app. Apple's checklist says to keep backend services live during review.
- In-app purchases cannot be tested. For auto-renewable subscriptions, Apple asks for a demo account with an expired subscription so the reviewer can see the whole purchase flow.
- The business model is unclear. Section 3 of the guidelines says this delays the review.
- Limited review history. Apple lists apps with little or no prior review history among the submissions that need more verification time (review status).
How do I answer Guideline 2.1 Information Needed?
The order I work in. None of this needs a new build.

- Number your answers to match the message. Answer every point in Apple's order, even the ones that do not apply ("The app has no user-generated content").
- Make the demo account work today. Sign in on a fresh install on a real device with the exact username and password from App Store Connect. If you have several roles, put the extra accounts in the Notes field.
- Remove the OTP blocker. Give the reviewer account a fixed code (see the code below) and write it in the notes.
- Record the walkthrough on a physical iPhone. Use the built-in screen recording, start from the Home Screen, launch the app, and go through every flow the message lists. For hardware accessories, Apple asks for a camera video of the real device, not a screen recording (complete review).
- Update App Review Information. In the version page, fill Sign-in required with the demo username and password, the Notes field (up to 4000 bytes), the Contact details with the phone number in international format, and attach documents if your field is regulated.
- Reply to App Review. In the app, click the unresolved issues link, click Resolve, then Reply to App Review, type your answers, use Attach File for the video, and click Reply. The Account Holder, Admin or App Manager role is required.
A reply template for App Review
Keep it factual and replace every placeholder.
Hello App Review team,
Thank you for the review. Answers to each point:
1. Screen recording: attached (iPhone 16, iOS <latest>). It starts at app launch and shows
sign up, login, account deletion (Settings > Account > Delete account), the subscription
purchase in the sandbox, and the camera and location permission prompts.
2. Tested on: iPhone 16 (iOS <x>), iPhone 13 (iOS <y>), iPad Air (iPadOS <z>).
3. Purpose and audience: <one or two plain sentences on who it is for and what problem it solves>.
4. Access: Sign in with the demo account in App Review Information.
Phone login: +94 77 000 0123, code 482913 (fixed for this review account, no SMS sent).
Admin features: second account in the Notes field.
5. External services: Firebase Authentication, our API on AWS, Stripe for web invoices,
OpenAI API for summaries.
6. Regions: the app works the same in all regions where it is available.
7. Regulated content: not applicable.
The same details are now in the Notes field for future submissions.
Kind regards,
<name>, <role>, <phone with country code>How do I let a reviewer pass SMS OTP safely?
If you use Firebase Authentication, the console already supports this. Under the Phone provider, add a number in Phone numbers for testing with a fixed code. Firebase says no SMS is sent for those numbers (Firebase phone auth for Flutter).
With your own OTP backend, keep the check on the server, never in the app. This Node module accepts one configured phone number with a secret six-digit code and sends every other number through your normal SMS provider. I tested it on Node 24.22.1 with a mocked SMS provider.
// review-login.mjs: let App Review sign in with a fixed phone number and code,
// while every other number still goes through your normal SMS OTP provider.
import { timingSafeEqual } from 'node:crypto';
const cfg = {
enabled: process.env.REVIEW_LOGIN_ENABLED === 'true',
phone: process.env.REVIEW_PHONE ?? '', // E.164, for example +94770000123
code: process.env.REVIEW_CODE ?? '', // 6 digits, stored as a secret
};
const normalize = (p) => String(p).replace(/[\s()-]/g, '');
function safeEqual(a, b) {
const x = Buffer.from(String(a));
const y = Buffer.from(String(b));
return x.length === y.length && timingSafeEqual(x, y);
}
export function isReviewPhone(phone) {
return cfg.enabled && cfg.phone !== '' && normalize(phone) === normalize(cfg.phone);
}
// Step 1: request a code. Skip the SMS for the review number.
export async function sendOtp(phone, sms) {
if (isReviewPhone(phone)) return { sent: false, review: true };
await sms.send(normalize(phone));
return { sent: true, review: false };
}
// Step 2: check the code. The review number only accepts REVIEW_CODE.
export async function verifyOtp(phone, code, sms, log = console) {
if (isReviewPhone(phone)) {
const ok = cfg.code.length === 6 && safeEqual(code, cfg.code);
log.info?.(`review login attempt ok=${ok}`);
return { ok, review: true };
}
return { ok: await sms.check(normalize(phone), String(code)), review: false };
}Map that number to a seeded demo user, not a real customer, and keep REVIEW_LOGIN_ENABLED=true while the account is listed in App Store Connect, because updates are reviewed with the same details.
How is "Guideline 2.1 - Performance - App Completeness" different?
Here App Review tested the app and something failed: a crash, a dead button, placeholder text, a broken link, or a purchase that does not load. Fix it, upload a new build and resubmit. If the failure is a product that never appears on the paywall, my checklist in Flutter in-app purchase product not found covers the usual causes. Apple's sandbox guidance adds two hard requirements: the Paid Apps Agreement must be active, and the first In-App Purchase of each type has to be submitted with an app version.
| Rejection | What Apple wants | Fix | New build? |
|---|---|---|---|
| 2.1 Information Needed | Answers, demo login, OTP code, video, documents | Reply to App Review with text and attachments | No |
| 2.1 demo account not working | Credentials that work for the whole review | Reactivate or reset the account, update fields, reply | No |
| 2.1 App Completeness (crash or bug) | An app that works on a physical device | Fix the code and test on device | Yes |
| 2.1(b) In-app purchase not found | Purchases visible and working in the sandbox | Fix product setup, or submit products with the version | Only if code changes |
| Metadata issue (for example screenshots) | Accurate store listing | Edit metadata | No, resubmit the same build |
Checklist before you submit a new app
- Demo account signs in on a fresh install today, with sample data and an expired subscription if you sell subscriptions.
- OTP or 2FA code for the reviewer is written in Notes.
- Backend is live, reachable from outside your country and not behind an IP allowlist.
- Notes cover purpose, audience, business model, devices and OS versions tested, external services and regional differences.
- In-app purchases load in the sandbox, are added to the same submission, and the Paid Apps Agreement is active.
- Account deletion is reachable in the app if users can create accounts.
- Contact phone number is in international format.
- Privacy manifest warnings are cleared. See ITMS-91061 missing privacy manifest in Flutter.
How do I check it worked?
After you reply, the next message in App Store Connect is an approval, a follow-up question or a specific rejection. If the follow-up repeats a request, your reply missed that point, so answer only that point. If you are still stuck, request a call from the same message window and include your time zone. Only appeal to the App Review Board after you have replied and the decision still looks wrong.
If you are shipping to both stores, Google Play has its own launch gate for new personal accounts, covered in Google Play 12 testers for 14 days.
In short: Information Needed is a question, so answer it on the same build with a working demo account, a fixed reviewer code, a device recording and clear notes. App Completeness is a failure, so fix the build and resubmit.
Frequently asked questions
What does Guideline 2.1 Information Needed mean?
App Review paused your submission because it needs more from you to test the app, such as a working demo account, a login code, a screen recording or answers about the app. It is not a rejection of the app's quality, and the review continues once you reply.
Do I need to upload a new build for Guideline 2.1 Information Needed?
No, not if nothing in the app has to change. Apple says to reply to the message in App Store Connect, and that resubmitting starts a new review after which App Review can no longer reply to your previous message.
How do I reply to App Review in App Store Connect?
Open the app, click the unresolved issues link at the top, click Resolve next to the submission, then Reply to App Review. Type your answers, use Attach File for videos or documents, and click Reply. You need the Account Holder, Admin or App Manager role.
Can I send a Simulator recording when Apple asks for a screen recording?
No. The request developers receive asks for a recording captured on a physical device running the latest OS, starting from app launch. Use the iPhone's built-in screen recording, and for hardware accessories film the real device with a camera.
How do I give App Review access to an app with SMS OTP login?
Apple asks you to put any required authentication code in the Notes field in advance, otherwise a call may be needed. Set up a fixed test number and code, for example Firebase Phone numbers for testing or a server-side allowlist, that signs in to a seeded demo account.
What is the difference between Guideline 2.1 Information Needed and App Completeness?
Information Needed means App Review is missing details and you answer with a reply on the same build. App Completeness means the app crashed, had bugs, placeholder content or in-app purchases that did not work, so you fix the code and submit a new build.
Should I appeal a Guideline 2.1 Information Needed message?
No. Apple's appeal guidance says not to file an appeal for requests for additional information or documentation, because App Review needs that information to finish the review. Reply first, and appeal only if a rejection still looks wrong.
How long does App Review take after I reply?
Apple says it reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours, though apps with little review history can take longer. If a call is needed, Apple says calls are typically completed within three to five business days.
Sources
- App Review Guidelines (Apple Developer, 2026-10-16)
- Provide information for a complete review (Apple Developer)
- Track a submission's review status (Apple Developer)
- Reply to App Review messages (Apple Developer)
- Contact App Review for help with a submission (Apple Developer)
- Appeal to the App Review Board (Apple Developer)
- Platform version information (App Review information) (Apple Developer)
- App Review (Apple Developer)
- Configure In-App Purchases for review in the sandbox (Apple Developer)
- Submit an In-App Purchase (Apple Developer)
- Phone authentication (Flutter) (Firebase, 2026-11-12)
- Need advise - Guideline 2.1 - Information Needed - New App Submission (Reddit r/iosdev)
Keep reading
- Guideline 4.3 Design Spam: Fix White-Label App RejectionsWhat Apple's Guideline 4.3(a) and 4.3(b) spam rejections mean, and how to fix them by merging white-label apps, using 4.2.6, or replying and appealing.
- ITMS-91061 Missing Privacy Manifest in Flutter: How to Fix ItGot ITMS-91061 after uploading a Flutter iOS build? Find the SDK Apple names, upgrade Flutter, plugins and pods, and verify the IPA before re-uploading.
- Flutter In-App Purchase Product Not Found: Fix ChecklistFlutter in_app_purchase returning notFoundIDs or an empty paywall? Work through the App Store and Google Play setup checks in the right order.
Comments
Share a question or note about this article.
Loading comments…