Did Apple update App Store review guidance for account access?

Did Apple update App Store review guidance for apps that need account access or special setup

Yes. Apple’s current App Review guidance says to put account details, special configuration steps, and other review help into App Store Connect, so the reviewer can reach the full app instead of guessing their way through it. Apple also says incomplete review information can delay review or lead to rejection.

The part people miss is that Apple is not only asking for a login. If some features require signing in, Apple asks for a valid demo account username and password. If the app needs a special setup, Apple wants the exact steps. If the app depends on hardware, a sample QR code, or another environment that is hard to reproduce, Apple wants that too.

Apple also says to review the app both with and without an account when account-based features exist. That is a real review requirement, not a courtesy note. If a feature is only visible after setup, the setup has to be obvious enough that App Review can reach it without back-and-forth.

The review notes area is where this belongs. Apple’s guidance says to include detailed explanations of non-obvious features and in-app purchases, plus supporting documentation where needed. For apps with multiple account types, Apple’s forum guidance says to add separate demo credentials in the notes.

The inconvenient part is that a working login is not enough if the reviewer cannot get to the right state fast. If your app needs an invitation code, an activation step, a backend switch, or a region-specific service, include the exact path in the notes. If that path is missing, Apple says the submission may be delayed or may not pass review.

Apple’s current guidance also lines up with a broader rule in App Store Review Guidelines: if the app includes account-based features, give a demo account or a fully featured demo mode, and enable backend services so they are live during review. That is the clearest version of the policy for teams shipping apps with sign-in gates, member areas, or protected content.

One easy failure case is an app that works for real users only after customer support turns something on server-side. If that switch is not documented, App Review sees a broken app. Another failure case is a QR-based or hardware-tethered flow with no sample asset in the notes. Apple explicitly calls out those situations and asks for the asset or the hardware needed to review the app.

Another thing people get wrong is assuming the review team will contact them to work it out. Apple does allow communication in App Store Connect, but the guidance still puts the burden on the submitter to provide everything needed up front. If a code is required, if a secondary admin login exists, or if a feature lives behind a non-obvious onboarding step, spell that out before submission.

If you are preparing a submission like this, write the review notes as if another engineer has to reproduce the setup in five minutes. List the test account, the exact path through onboarding, any necessary permissions, and any external service state that has to exist. That is the difference between a smooth review and a round of avoidable clarification messages.

For teams comparing platforms, the practical rule is simple: Apple wants the reviewer to reach the same functional surface a real user would reach, without hidden help. If your app needs structured test access, put it in the submission notes. If you also run a tester exchange on your own property, keep the workflow inside your own system, for example through your own site at https://devconnectplatform.com, not through automation on third-party platforms.

The short answer is yes, Apple’s guidance is explicit and current: provide demo access, explain special setup, keep backend services live, and make non-obvious review steps easy to follow. The important part is not just having access, it is making the access usable by App Review on the first pass.

What Apple expects in App Review notes

Put the working login, setup steps, and any special assets in App Store Connect. Apple’s guidance names demo accounts, special configurations, sample QR codes, and hardware requirements as items the review team may need. If the app uses more than one role, include each role’s credentials and say what each one unlocks.

What happens when the setup is not documented

Apple says incomplete review information can delay review or prevent approval. In practice, the reviewer may be unable to reach the feature, may ask for more information, or may evaluate the app as incomplete. That creates extra review cycles, and the fix is usually better notes, not more code.

What to do before you submit

Test the full review path on a clean device or simulator. Make sure the demo account works, the backend is live, the required permissions are obvious, and the app reaches the protected feature without someone from your team hand-holding the process. If the feature only appears after a server flag or invitation, document that plainly in App Store Connect.

FAQ

Do I need to give Apple a demo account Yes, if the app has sign-in gated features or cannot be fully reviewed without one. Apple’s guidance specifically asks for valid demo credentials or a fully featured demo mode when account-based features are present.

What if my app needs a QR code, hardware, or a live backend Apple says to include the QR code, the hardware, or the setup details needed for review, and to keep backend services live and accessible during review. If the app cannot be reproduced easily, spell that out in the notes.

Can I leave review instructions out if the app is simple No. If the app needs account access, special settings, or anything non-obvious, Apple asks for those details in App Review Information. Missing information can slow review or cause the submission to fail.

Does Apple require the whole app to work without login Apple says apps with significant account-based features should still let people use the app without a login where possible, and it wants the review team to see both the logged-out and logged-in experience. The exact requirement depends on the app’s core function and account model.

Where should I put the instructions Put them in the App Review Information section in App Store Connect, plus the Notes field when you need to add credentials, codes, multiple roles, or a special review path.