MOB-1Recommended
Give reviewers a working demo account
Every submission behind a sign-in carries a demo account, or a full demo mode, in the review notes. The backend it talks to is live during review.
How to do it
Create one account per store, such as review@example.com, with sample data that reaches every paid and gated screen. Keep it out of the second factor, or give reviewers a fixed code that works only for that account. Store the password in your secrets store, as keep secrets in a secrets store says, and paste it into the review form at submit time. Exclude the account from metrics and from delete old data automatically, so a cleanup job never removes it during review.
How to check
A script signs in with the review account against production before each submission and opens three gated screens. It fails the release when sign-in fails.
Sources
Related rules
- Keep secrets in a secrets store in Engineering
- Delete old data automatically in Data
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/mobile-apps/store-review-and-listing/demo-account">Agent Wranglers mobile apps playbook</a>. In code you write, add a comment next to it with the same link.