Run a free ShipCheck before you reply or resubmit. Paste a public GitHub link or upload a zip, no account needed. ShipCheck reads allowlisted config files and names each issue with the guideline, a short label, how serious it is, and how many places. Its 2.1 checks look for placeholder copy, sample links (example.com, localhost, and similar hosts), and a missing reviewer-notes document when the project has sign-in. It also flags a missing encryption declaration. It does not read or print account details. The same scan also checks account deletion, privacy manifests, In-App Purchase, and Sign in with Apple. A fix is $9, or 3 for $19, paid first. Run a free ShipCheck

It can't see your App Review Information, demo accounts, or the questions in your message, and it can't record a review video. Those stay on you.

Guideline 2.1 Information Needed: demo accounts, review notes, and how to reply

A Guideline 2.1 Information Needed message looks like a rejection in App Store Connect, and it can land on a first submission. Usually the reviewer has started, then stopped because they couldn't finish with what you sent. If you answer what they asked for, and you don't accidentally start a brand-new review, you can get the same submission moving again.

Guideline 2.1 is App Completeness. It also covers crashes, placeholder content, and broken links. An Information Needed message is a request for access or context. A crash or placeholder problem is in the build. Read your message and treat those as different paths.

What Apple's rule says

From Apple's App Store Review Guidelines, 2.1 App Completeness (page marked "Last Updated: October 16, 2026", fetched Nov 18, 2026):

(a) 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.

(b) 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.

The same guidelines page, under Before You Submit, also says:

Provide App Review with full access to your app. If your app includes account-based features, provide either an active demo account or fully-featured demo mode, plus any other hardware or resources that might be needed to review your app (such as login credentials or a sample QR code).

Enable backend services so that they're live and accessible during review.

Include detailed explanations of non-obvious features and in-app purchases in the App Review notes, including supporting documentation where appropriate.

Apple's App Review page adds this: "On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more." Apple's help pages usually say the reviewer "requested more information." The message in App Store Connect is often titled Guideline 2.1 - Information Needed. The status you'll see is commonly Unresolved Issues.

Reply first, and don't start a new review by mistake

Apple's review status page is explicit about this:

It's not necessary to resubmit when: App Review requested more information and there are no other issues to resolve. Instead, you can reply directly to the message in App Store Connect. Resubmitting starts a new review, after which App Review can no longer reply to your previous message.

The same page says you also don't need a new submission when the fix is metadata or a server-side change, "such as providing or activating demo credentials." Reply once those changes are in place. Resubmit when the problem is in the build and you've uploaded a new binary. Don't resubmit until every issue in the message is resolved; Apple says that delays review and leads to the same outcome.

Apple's appeal help page also says: "Don't file an appeal for requests from App Review for additional information or documentation about your app. This information is necessary for App Review to complete the review."

So the usual path for an Information Needed message is: update App Review Information if needed, reply in the App Review section, attach what they asked for, and wait. Upload a new build only if they asked for a change in the binary, or if you found a real bug that blocked the review.

Set up the demo account

Do this in the App Review Information section of App Store Connect before you submit, and again if a reviewer says they couldn't sign in.

Apple's complete review help page and App Store Connect field reference ask for:

  1. A username and password that work at the time of submission. The field reference says the demo account "must not expire." The complete review page says credentials that expire or change before review starts may get the submission rejected. Don't rotate the password while the build is in review.
  2. Extra credentials in Notes if the app has more than one account type, such as admin and regular user.
  3. A demo account with an expired subscription if the app offers auto-renewable subscriptions, so the reviewer can walk the whole purchase flow.
  4. Any authentication code the app needs, also in Notes, in advance. Without it, Apple says a call may be required, and calls are typically completed within 3 to 5 business days.
  5. Demo login information for a single sign-on service if that's how the app signs in. Put additional accounts in Notes.
  6. Backend services left on for the whole review.

If you can't give a demo account because of legal or security obligations, guideline 2.1(a) allows a built-in demo mode "with prior approval by Apple," and that mode has to show the app's full features. The complete review help page also says a demonstration mode is appropriate for sensitive data or a highly regulated industry, and that it should use demonstration data.

Test the demo sign-in yourself on a fresh install, on a real device, before you send it. If the app uses email magic links, SMS codes, or an authenticator app, put a fixed, reusable way in and write the steps in Notes.

What to put in review notes

App Review Information is not visible to customers, and Apple's field reference says it can be edited at any time. The Notes field can contain up to 4000 bytes, in any language.

Apple's complete review help page says to tell App Review:

  • For a new app, the concept and business model. For an update, what changed and where to find it.
  • The app's purpose and target audience.
  • The device models and OS versions you tested on.
  • External services used for core functionality, for example auth, payments, or AI services.
  • Regional differences, or a confirmation that the app works the same in every region.
  • Required hardware, with a video (not a screen recording) of the app running on a physical Apple device as it pairs with that hardware.

If a feature is behind a hidden gesture, a storefront, or a flag, say so and give the steps. If some in-app purchases shouldn't appear, 2.1(b) says to explain why in the review notes. Apps in regulated fields may also need documentation attached here; the complete review help page has a table of typical documents by guideline. Include contact details too: a name, email, and phone number in international format.

How to answer in App Store Connect

People still call this the Resolution Center. In current App Store Connect, it's the App Review section. Apple's reply help page lists the steps:

  1. In Apps, select the app.
  2. At the top of the page, click the link that indicates there are unresolved issues.
  3. In the In Progress section, click Resolve next to the submission.
  4. Click Reply to App Review.
  5. Enter the reply. Attach a file if they asked for a video, a screenshot, or a document.
  6. Click Reply.

Answer every item in their message, in their numbering, in plain sentences. If they asked 6 questions, send 6 answers. If they asked for a screen recording on a physical device, record that on a real iPhone or iPad, not the Simulator, and attach it. We have a separate guide for that request: Guideline 2.1 Information Needed: Apple wants a screen recording.

A reply template you can adapt when they couldn't sign in, or they asked how the app works:

Thanks for the review. Here's the information you asked for.

1. Demo account: username review@example.com, password in the Sign-in required fields and repeated here. This account stays active and does not use a one-time code. A second account (admin) is in Notes. 2. The app is a [one-sentence concept] for [audience]. There's no digital purchase in the iOS app; any billing happens outside the app as described in Notes. 3. Sign in on the welcome screen, then open [tab] to reach [feature]. The backend is live. 4. Third-party services: [auth, API, payments, AI], used for [reason].

Please let us know if you need anything else to finish the review.

(That's a template. Use the real username, the real services, and the path a reviewer can follow. Don't put a live customer account here.)

Apple's contact help page says to be specific, and not to use this reply field to file an appeal or request an expedited review. If you need more help after they reply, you can request a call and include your time zone.

Timelines

Apple's review status page and App Review page say App Review works around the clock, "with the goal of reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." That's a goal, not a promise. The status page also says some reviews take longer, including apps with little or no prior App Review history, apps that need documentation checked, and apps with complex or novel issues.

Apple does not publish a separate timeline for how quickly a reviewer comes back after you answer. If you resubmit a new build, you're starting a new review.

If a feature is blocked on an authentication code you didn't include, the call Apple may schedule is typically 3 to 5 business days. Putting the code in Notes up front avoids that wait.

You can check status any time in the App Review section. Waiting for Review means they have the submission and haven't started. In Review means a reviewer has it. Unresolved Issues means they found something, including a request for more information. Don't pull the submission to "bump" it. If you have a critical bug or a real event deadline, Apple's expedited review help page explains that path, and says to reserve it for genuine urgency.

Common mistakes

  • Resubmitting the same build after an information request, which starts a new review and closes the previous thread.
  • Filing an appeal of an Information Needed message. Apple says not to do that.
  • A demo password that expires, a shared inbox nobody watches, or a 2-factor prompt the reviewer can't pass.
  • Leaving the backend off, or using a staging host the reviewer can't reach.
  • Notes that describe a feature the reviewer can't find, with no steps.
  • Adding extra product changes to a reply-only request, then hitting a new guideline on the next review of that new build.
  • Skipping an expired-subscription demo account, so the reviewer can't see the paywall or restore flow.
  • Ignoring 2.1(b): in-app purchases that aren't visible, aren't in the sandbox, or aren't explained in Notes.

What about Google Play?

Play has a similar requirement, under a different name. Google's sign-in details page says you must provide what the review team needs "to log in and access all app functionality," which can include a demo username and password, a QR code, or instructions for restricted areas. Those details must stay accessible, reusable, and valid from any location, and they must work without an error. If the app normally uses 2-Step verification or a one-time password, Google asks for reusable credentials that can bypass those requirements. If the password expires, "the app may be rejected." Sign-in details must be provided in English.

Enter all of that in Play Console (App access / sign-in details), not only in a reply after a rejection.

When ShipCheck helps vs when it doesn't

ShipCheck helps with the 2.1 problems it can see in project files: placeholder copy in screens, links to example.com, localhost, or another sample host, and a missing reviewer-notes document when the project has sign-in. It also flags a missing encryption declaration. It does not read or print account details. Those file checks are completeness issues, and placeholder copy and sample links are a common reason for a 2.1 rejection. The same scan also checks other config issues, including account deletion, privacy manifests, In-App Purchase, and Sign in with Apple. See the guidelines we check.

It can't read your App Review Information, Notes, or demo credentials. It can't tell whether a reviewer could sign in, record the video Apple asked for, answer the questions in the message, or speed up the queue.

Run a free ShipCheck

FAQ

Is Information Needed a rejection? It blocks approval until you respond. The reviewer is asking for access or details so they can finish. If the message also cites a crash, placeholder content, or another guideline, fix those too.

Can I reply without uploading a new build? Often yes. If they only asked questions, a demo account, or a video, Apple's review status page says to reply in App Store Connect rather than resubmit.

Do I need a new build? Only if the binary has to change: you fixed a crash, removed placeholder content, or changed a flow the reviewer couldn't use. Activating a demo account or editing Notes does not need a new build.

Why did this happen on my first app? Apple doesn't publish criteria for when it sends an Information Needed message. It does say apps with little or no prior App Review history may take longer to verify, and that providing complete information up front can make review faster and more predictable.

The reviewer still can't sign in. Test the same username and password on a fresh install, confirm the backend is up, and put any extra step (an invite code, a sample QR code, a fixed verification code) in Notes and in your reply. Then reply again. Don't resubmit unless you also changed the build.

Related guides

Ready to reply or resubmit? Run a free ShipCheck first. Paste a public GitHub link or upload a zip, no account needed. It names each issue with the guideline, a short label, how serious it is, and how many places. A fix is $9, or 3 for $19, paid first. Run a free ShipCheck

It still can't see your demo account, review notes, or App Review questions.