TL;DR. App Review Information — contact name, phone, email, a demo account username/password, and a free-text Notes field — sits on the same version screen you submit from, and Apple’s own submission page states it plainly: “Required role: Account Holder, Admin, or App Manager.” Marketing, the role that can edit your keyword field and subtitle, isn’t on that list. Unlike the keyword field, this section can be edited any time, not just at version submission — which is exactly why a stale demo account is such a common, avoidable rejection: nobody remembers to check it until App Review already has.

What actually goes in the App Review Information section?

Apple’s App Store Connect API documentation lists the same fields the App Store Connect UI collects: contact first and last name, contact phone number, contact email address, whether testing the app requires a demo account, a demo account username and password if it does, and an optional Notes field for anything else the reviewer needs to know. None of this is customer-facing — it exists purely to get a human through your app during review.

The demo account fields are a single username/password pair. If your app has more than one account type — a free tier and a paid tier, an admin view and a member view — there’s nowhere else to put the second set of credentials. Apple’s own guidance for this case is to use the Notes field for the additional accounts, and to include any second-factor or authentication code in advance, since a reviewer who hits a 2FA wall without one is liable to open a call before finishing the review.

Who can actually edit the App Review Information section?

Account Holder, Admin, or App Manager — that’s it. Apple’s help page for submitting an app states this exact line: “Required role: Account Holder, Admin, or App Manager.” The Marketing role, which can edit the keyword field, subtitle, description, and screenshots, is absent from that list.

That’s a narrower set than the four roles (Account Holder, Admin, App Manager, or Marketing) that can touch your actual store listing. If you’ve handed ASO work to a contractor under the Marketing role specifically so they can’t submit builds or change pricing, that same scoping means they also can’t update the demo account password or add a submission note — someone with a broader role has to do that part, even on a day when the only thing that changed is a test account’s login.

Why does a version get rejected when nothing in the code changed?

The most common reason is a demo account that no longer works. App Review Information isn’t locked to the build the way your keyword field is locked until the next version submission — it can be edited at any time, which means it’s easy to assume it’s “already set” and skip checking it. Apple’s own pre-submission guidance is direct about this: provide demo accounts or a working account-demonstration mode before you submit, because reviewers test the app both signed in and signed out, and a dead test login is enough on its own to stall a submission that has nothing wrong with its binary.

This shows up most often on a resubmission weeks or months after the original one — a staging password rotated, a seeded test account got cleaned out of the database, a backend the demo account depended on got decommissioned. None of that touches your app’s code, but all of it produces the same rejection message about being unable to sign in.

Same-day checklist before your next submission

  1. Sign in with the exact demo account currently saved in App Review Information — not from memory, from what’s actually saved — before you click Submit.
  2. If your app has more than one account type, confirm the second set of credentials is still in the Notes field and still works, not just the primary pair.
  3. If sign-in requires a 2FA or one-time code, put a currently valid one in the Notes field in advance rather than leaving a reviewer to request it.
  4. Confirm contact email and phone are current — that’s how Apple reaches you if the reviewer needs something mid-review, and there’s no separate reminder if it’s out of date.
  5. If the person doing this check only holds the Marketing role, hand it to whoever holds Account Holder, Admin, or App Manager — Marketing can’t save changes here even though it can save a keyword change ten minutes earlier in the same session.