Review demo accounts and login-path notes: let reviewers finish once
Login rejections often mean unclear paths. Template demo accounts, OTP, skip-onboarding, and paywall notes; link TestFlight/closed testing. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
“Unable to log in / unable to verify core functionality” shows up constantly in rejection letters. Usually the account is fine—the notes never say where to find the OTP, whether first-run onboarding can be skipped, whether paid content has a sandbox path, or that a region/IP block was left on. Goee (goee.cc) treats Review Notes as a second main-path manual, as important as in-app UX. For beta handoff see TestFlight review tips; full materials: App Store materials. Note length and attachment support follow the current official UI.
What this guide solves
- Demo password expired or deleted by a teammate.
- 2FA tied to a personal phone; nobody answers during review hours.
- Five forced onboarding screens after login; reviewer never reaches core value.
- Paywall blocks everything with no sandbox Apple ID / “Reviewer unlock” path.
- WeChat-only or region lock with no alternate demo path.
- Vague English notes that do not match Chinese UI labels.
Who should read
| Role | Deliverable |
|---|---|
| QA | Reproduce step-by-step on a clean device; screen-record |
| Client | Stable Review / Staging switch (not a hidden cheat switch) |
| Backend | Demo data, OTP policy, allowlists |
| Listing ops | Paste formatted notes into ASC / Play |
Any app that needs login to show value should freeze a “review-only” credential set 24 hours before submit.
Core practice
Demo account checklist
| Item | Standard |
|---|---|
| Account type | Regular user; document admin separately if needed |
| Password | Strong but readable; do not change during review |
| Verification | Fixed test code or 2FA off (review build only) |
| Data | Prefill orders/content—avoid empty home |
| Validity | At least two weeks past expected review end |
| Concurrency | Multi-device OK or state the limit |
Blocks the notes must cover
| Block | Content |
|---|---|
| Login | Username, password, which third-party option |
| Verification | OTP 000000 or test number range |
| Navigation | Tab/menu steps to core features |
| Paid | Sandbox Apple ID / test card instructions |
| Region | If VPN is required, lawful reason and use |
| Delete / privacy | Link to policy and a demoable delete path |
| Contact | Support email in a stated timezone |
TestFlight vs production review
After closed testing, update notes to match production-build behavior. If the test build had an extra menu, do not silently remove the demo entry from the production build. Scope and evidence: TestFlight review tips.
Copy-paste templates
App Review notes skeleton
Thank you for reviewing [App Name].
LOGIN
- Tap "Sign In" on launch.
- Email: review+demo@yourdomain.com
- Password: [Redacted pattern — share securely in notes field]
- No 2FA on this account.
CORE FLOW
1. After login, tap Home → [Feature].
2. To create content: + → [steps].
SUBSCRIPTION (if any)
- Use Sandbox Apple ID: [instructions only — use sandbox per Apple docs]
- "Restore Purchases" at Settings → [path].
ACCOUNT DELETION
- Settings → Account → Delete Account (demo completes step 3).
NOTES
- Push: allow on first prompt for notification demo.
- If empty state appears, pull to refresh once.
Support: support@yourdomain.com (UTC+8 business hours)
Internal freeze sheet
Build number:
Demo account owner:
Last successful walkthrough date:
Deltas vs last version: onboarding / login method / paywall
Pasted into ASC: Y / N
Play closed-test notes: Y / N/A
Common mistakes
- Password in Slack, not in Review Notes—reviewers only see the console.
- Demo account is VIP and diverges from real purchase logic.
- Hidden gesture opens a backdoor—high risk; Goee will not help deceive review.
- Long unstructured notes—use numbers and short headings.
- EN/CN paste chaos—terms must match the UI.
- New account every submit without telling collaborators.
FAQ
Can we skip providing an account?
If core value requires login, skipping raises rejection odds. Guest mode that covers every review concern must be proven in the notes.
Can OTP be hard-coded to 888888?
Common on a test tenant; the review build must actually behave that way without weakening real-user security.
Third-party login is Apple-only—still need email?
If the review path must use Apple, write the steps; see third-party login review.
Rejected for login failure—what next?
Keep the account, check logs, fix notes or the bug, then resubmit per rejection fix.
Where do Play notes go?
Field names change with Console—follow the current official page; the principle is reproducible steps.
Third-party login and enterprise SSO
If you offer Apple, Google, WeChat, and email, say which one to use for this review. Without overseas social apps available, a backup email path is safer. If enterprise SSO cannot be reproduced in Apple’s office, provide an equivalent demo tenant or state that review scope excludes the corp IdP—and do not lock core value behind SSO only. For magic-link login, note email delay, spam-folder hint, and link TTL.
Video, attachments, and secrets
Some consoles accept review attachments or video. Keep under two minutes, point at UI elements; English captions OK without voiceover. Never put real user data in a public video. Passwords only in the review-notes field; share internal secrets via a one-time channel—notes can say “same as yesterday’s freeze sheet” to cut leak surface.
Multi-region builds and remote config
If one build toggles features by region, say which region the reviewer account lands in and which modules appear. Do not expect reviewers to switch regions for a disabled illegal market—default so US (or your storefront country) can test the main path. Wrong config → empty home is a common real cause of “login” rejections.
Cadence
QA drafts login notes on freeze day; listing ops proofreads and pastes into ASC. Any login-method change—even a “small” one—needs a full walkthrough again. With rejection fix: if the reason is login, check lockouts and IP limits before rewriting notes or the binary. Dual-platform: write Play internal notes and ASC notes separately—do not paste fields into the wrong place. Before event builds, confirm demo content (coupons, campaign pages) has not expired.
Handoff security
Once a demo password is in the review console, treat it as semi-public. Rotate after review; never use a production admin account. If you must show real payment sandbox, do not put a production Apple ID in the notes.
If the app supports guest browse, open the notes with “Skip login via Continue as Guest on splash” and state what guests can see so reviewers do not assume signup is required. Document guest vs signed-in IAP paths separately.
Internal review vs external boundary
Listing is a delivery gate, not final legal review. These steps help teams finish checkable items before submit; platform policy and store enforcement change—follow official pages. In retros, separate real defects (fix code) from unclear wording (fix notes, policy, or screenshots). Materials sent to Goee on Telegram @hagee66 should include build number and checklist results. We do not promise approval and will not help hide features, dual binaries, or anti-review tricks. Client acceptance against a handoff checklist beats “please take a look.”
| Acceptance type | Goee can help | Client provides |
|---|---|---|
| Path and note readability | Yes | Working demo account |
| Policy URL reachable | Yes | Certs and DNS |
| Form vs binary consistency | Check | Frozen SDK list |
| Legal conclusions | No | Counsel opinion |
Next steps
Attach finalized notes to the precheck “demoable” row. Need notes drafted or a login-path walkthrough: Telegram @hagee66. No approval promise—acceptance is account availability and readable notes.
Back to guide library · Apple listing · Google listing