Did Apple change App Review rules for account-based apps?

Did Apple change App Review rules about account-based apps needing demo access

No. Apple still expects account-based apps to give App Review a way through the logged-in experience, either with an active demo account or a fully featured demo mode. Apple’s current guidance also says to include any login credentials, sample QR codes, backend access, and special instructions the reviewer needs.

The part people get wrong is assuming that a login screen alone is enough. Apple says it reviews the whole app, including the experience with and without an account, and it wants up-to-date credentials in App Store Connect when account-based features are present. If the reviewer cannot get into the important flows, the submission can stall on completeness instead of on product quality.

Apple’s wording is not “send us anything that proves the app exists.” It is more specific: if your app includes account-based features, provide either a demo account or a demo mode, and make sure the demo path shows the app’s real features. That means the reviewer should be able to evaluate the product, not just see a splash screen, a dead-end login, or placeholder content.

The inconvenient part is that the requirement is broader than many teams plan for. If sign-in is part of the product, you need to think about account creation, test data, feature flags, backend availability, and any extra codes or hardware that a reviewer may need. Apple’s review guidance says to include those details in App Review Information, and to keep backend services live and accessible during review.

There is also a narrow exception path. If legal, security, or regulatory constraints make a shared demo account impossible, Apple says you may use a built-in demo mode, but that route needs prior approval. That is not a casual workaround, and it is not the same thing as leaving the reviewer to guess how to get past a locked screen.

The rule did not become looser just because some apps now require more sensitive access control. Apple still wants review to cover the account-based experience, and it still asks for the practical details that make that possible. If your app has multiple account types, App Review tips from Apple also recommend giving credentials for each role in the notes, so the reviewer does not get stuck in the wrong permission level.

A concrete example: if your app is a clinic portal, a team dashboard, or a private community tool, the reviewer still needs a working path that shows the core functionality. A demo account with representative content usually works. A demo mode can work too if it reproduces the real flow. What does not work is telling Apple to “use any account” when the product behavior changes based on role, region, tenant, or subscription state.

The safest submission checklist is simple. Put the login credentials or demo mode details in App Store Connect, explain anything non-obvious in the review notes, turn on the backend, and verify that the reviewer can reach the main features from a clean install. If a feature needs a code, a sample QR scan, or a special environment, say that plainly before review begins.

If you are building with account-heavy workflows and want a place to coordinate real testers, DevConnect is free to use and is built around reciprocal testing rather than paid shortcuts. That does not replace Apple’s review requirements, but it can help you find people who will actually run the app before submission. https://devconnectplatform.com

The bottom line is unchanged: Apple still wants a reviewer to get through account-based apps without friction. The rule is not “remove login,” it is “provide a review path.” If your app depends on sign-in, build that path into the submission process from the start.

FAQ

Do I always need a demo account? No. Apple allows either a demo account or a fully featured demo mode when account-based features are part of the app. The key requirement is that App Review can access the relevant experience without guessing.

Can I submit without giving any login details? Only if the app does not need them for review. When features require sign-in, Apple says to provide a valid demo account username and password, or a demo mode approved for review.

What should go in App Review notes? Put the steps, credentials, special settings, role-based logins, codes, and anything else the reviewer needs to see the core app flow. Apple explicitly calls out special instructions and extra access details in review information.

What if my app is behind a private system or regulated login? Apple’s guidance points to a demo mode when a demo account is not possible for legal or security reasons, but that path needs prior approval. In practice, you should explain the restriction and provide the closest reviewable experience.