Demo accounts for an app behind a login
If the first screen of your app is a login, a reviewer who has no credentials sees a login screen and nothing else. Apple rejects that under Guideline 2.1 as an incomplete app. It is a rejection about access, not about quality, and the app is usually fine.
What to provide
- A username and password that work right now, in the build you submitted.
- An account with realistic data in it. An empty account shows a reviewer a series of empty states and invites a different rejection.
- Any second factor pre-disabled, or a note explaining exactly how to get past it.
How it usually fails
The credentials expired between submission and review. The account was reset by a cleanup job. The app points at a staging server the demo account does not exist on. Or two-factor authentication sends a code to a phone the reviewer does not have — which is the single most common version.
Regional and hardware requirements
If your app only functions in one country, or needs specific hardware, say so in the review notes. A reviewer testing from elsewhere on a device you did not anticipate is not going to guess.
Where this comes from: the Play side is measured on our own submissions; the Apple side is Apple’s published guidelines, which we have not tested against a real submission.
Source: Apple App Review Guideline 2.1 App Completeness (demo account for login-walled apps); Play Console review access instructions, verified 2026-09-15
Check your own listing against this and everything else we check. App Store checks are free; a Google Play report is $19.