Did Apple change App Store review details submission?

Did Apple change how App Store review details are submitted for contact and demo accounts

Yes. Apple’s current process puts contact information, demo account details, and review notes in App Store Connect’s App Review Information section for the app version. The review team expects those details there, not in a separate side channel.

Apple’s documentation for App Store review details says the resource manages the information required for App Review, including contact first and last name, phone number, email address, whether a demo account is needed, and demo account name and password when single sign-on is used. Apple also says you can create, read, and modify those details for a version.

The part people get wrong is assuming contact and demo credentials live in the same place forever. Apple splits the workflow by context. For App Store review, the details sit on the app version page in App Store Connect. For TestFlight external testing, Apple uses a separate Test Information area, and the fields can differ from the App Store submission details.

Apple’s review guidance is explicit about what belongs in App Review Information. If signing in is required, provide a valid demo account username and password. If there are multiple account types, use the Notes field for additional credentials. If an authentication code is also required, include it in advance in Notes, or App Review may need to call you.

That is the practical change that catches teams: the review package is now treated as structured submission data, not just an email thread with a reviewer. The update path also matters, because Apple’s documentation says you can modify App Store review details, including contact information, demo account, and notes, after creating them for the version.

If you are submitting a new build, the safe rule is simple, enter the current contact details, the demo account that actually works today, and any notes the reviewer needs before they can reach the full flow. Apple says to provide up-to-date demo account login credentials, and to include extra account types or special instructions in Notes when needed.

If your app uses a demonstration mode instead of a real login, Apple still wants the review team to be able to see the complete experience. Apple’s guidance says apps handling sensitive information or operating in regulated industries can use demonstration data, and that the Notes field should explain what App Review needs to know.

The inconvenient part is that incomplete review details can slow the review even when the app itself is ready. Apple says missing information, missing demo access, or missing special instructions can block a complete review. If the reviewer cannot reach the needed state, Apple may request a call or reject the submission until the review information is fixed.

A concrete example helps. If your app has one generic login for normal users and another for admins, the App Review Information section should include the main credentials, and Notes should identify the admin login and any extra step needed to reach admin-only features. If the app also requires a one-time code, put that code in Notes before submission.

For teams that also run beta testing, do not reuse the TestFlight fields as a substitute for App Store review details. Apple says TestFlight external testing requires separate test information, including a feedback email address, and that this information can be updated at any time. That is a different submission path from the App Store version review.

If you want to check the current product and review workflow in one place, use App Store Connect and the Apple developer help pages, then keep your App Review Information aligned with the build you are sending. For teams that also coordinate testers elsewhere, a lightweight exchange platform like https://devconnectplatform.com can help with testing work, but it does not replace Apple’s own review fields.

So the short answer is yes: Apple moved review submission toward explicit, structured App Store Connect fields for contact and demo access, and the details now need to be current, complete, and tied to the version under review. The old habit of treating review access as an informal afterthought is the part that fails.

What exactly goes in App Review Information

Apple says the required App Review details include the reviewer contact name, phone, email, whether a demo account is needed, and demo account credentials when applicable. Apple also allows notes for anything the reviewer needs to complete the review, including special instructions, extra account roles, or an authentication code.

Is this the same as TestFlight review information

No. Apple keeps them separate. TestFlight external testing uses Test Information, including a feedback email address for testers, while App Store review uses App Review Information on the app version page. Apple says the beta information can differ from the later App Store submission.

What happens if the reviewer cannot sign in

Apple may need to contact you, ask for more information, or reject the submission until the missing access is fixed. Apple’s guidance says to provide up-to-date credentials and to put extra account details or authentication codes in Notes so the reviewer can complete the review without a call.

Can you update review details after submission

Yes. Apple’s App Store review details documentation says you can create, read, and modify review details for a version. Apple’s help pages also say you can update test information at any time, but that is the TestFlight path, not the App Store review path.