Rejection guides / Guideline 2.1: Information Needed
Guideline 2.1 - Information Needed: what it means and how to reply
This isn't a verdict on your app yet. The reviewer couldn't finish the review without more information, and the submission waits until you answer.
"Submissions to App Review ... should be final versions with all necessary metadata and fully functional URLs included ... and include demo account info (and turn on your back-end service!) if your app includes a login."App Review Guideline 2.1(a), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
What "Information Needed" means
Guideline 2.1 is App Completeness. When the message is titled "Information Needed", the reviewer has questions about how your app works, or couldn't reach part of it, and has stopped until you reply. Nothing in your binary has necessarily been judged against the guidelines yet.
Because the reviewer has paused, the fastest path is a complete answer to every question in one reply. A partial answer usually brings a second round of questions.
Questions reviewers often ask
- How to sign in: a demo account that works, or steps to reach features behind a login, paywall or invitation.
- Who the app is for and how it makes money, when the listing doesn't make that obvious.
- Whether you have the rights to content, brands or data the app shows.
- What data the app collects, why, and where it goes.
- How a feature that depends on hardware, a location or a third-party account works, sometimes with a request for a screen recording on a real device.
These are common patterns, not an official list. Your message says exactly what this reviewer needs.
How to reply
- Reply in the App Review message thread for the submission in App Store Connect, not with a new build, unless the reviewer asked for a change.
- Answer every question, numbered in the same order the reviewer asked them. Short and specific beats long.
- If they asked for a demo account, test it yourself right before sending, from a fresh install. Turn on any backend service it needs.
- If a screen recording would show the feature faster than words, attach one recorded on a physical device.
- Put the same details in App Review Information (review notes and demo account) so the next reviewer has them too.
If your reply sits unanswered
Apple doesn't publish a timeline for replies. On Apple's developer forums, developers report waits from about a day to two or three weeks after answering a 2.1 request, and several advise against cancelling and resubmitting an identical build, which can restart the wait without fixing anything.
If it has been more than a week, check that your reply actually sent in the thread, then use Contact Us in your developer account to ask App Review about the submission.
Developer report: stuck 18 days after replying · Developer report: no response for 12 days · Developer report: stuck 7 days after replying
How to avoid it next time
- Fill in App Review Information on every submission: a working demo account, and notes for anything a reviewer can't discover alone.
- Explain non-obvious features and the business model in the review notes before they ask.
- Test the exact build you submit on a real device, with your backend in its production state.
Common questions
- Is "Guideline 2.1 - Information Needed" a rejection?
- Not a final one. The review has paused because the reviewer needs answers. Reply in App Store Connect and the review continues from there.
- Should I upload a new build?
- Only if the reviewer asked for a change. If they asked questions, answer them in the message thread. Developers on Apple's forums report that resubmitting an identical build can add to the wait.
- How long after replying will App Review respond?
- Apple doesn't publish a timeline. Developer reports on Apple's forums range from about a day to two or three weeks.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 2.1: App Completeness (crashes, bugs, placeholders)
- App Review Board: How to appeal a rejection
- Guideline 4.3: Spam
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)