Skip to main content
App Review and submission Level: All 12 min read

Writing Effective App Review Notes: Demo Accounts and Reviewer Guidance

Prepare clear App Review notes, provide reliable demo credentials, avoid MFA pitfalls, and guide Apple reviewers through complex features.

Published: 2026-11-01 • Last Updated: 2026-11-01 • Author: Kip Lawrence
Key MCP Tools: release_readiness_checkapp_store_versions_listapp_store_version_get

Direct Answer: Guiding Reviewers to Fast App Approval

When an Apple App Review specialist evaluates your iOS application, they install the build on a physical test device, launch the app, and evaluate core features against the App Store Review Guidelines. Reviewers have only a few minutes per app. If they encounter a mandatory login without credentials, hit an empty screen requiring complex setup, or cannot test features gated behind hardware, your app will be rejected under Guideline 2.1 (App Completeness).

The App Review Information section in App Store Connect is your direct channel to guide the reviewer through your application.

To ensure a smooth review:

  1. Prepare Demo Credentials: If your app requires an account, provide an active test username and password pre-seeded with sample data. Never require physical SMS verification codes.
  2. Draft Scannable Notes: Provide concise, numbered testing steps covering primary features, demo toggles for hardware or location dependencies, and emergency contact details.
  3. Audit Submission Readiness: Use FlightDeck to verify that your App Review Information is attached to the version draft before submitting the app for review.

What You Need

Before configuring reviewer notes:

  1. Active Version Draft: An App Store version in PREPARE_FOR_SUBMISSION state.
  2. Dedicated Test Account: A pre-provisioned user account in your backend with pre-populated sample records.
  3. FlightDeck for Mac: Running and connected to your AI assistant to verify readiness checks.

Anatomy of App Review Information in App Store Connect

In App Store Connect under your active version page, scroll down to the App Review Information section:

TEXT
┌─────────────────────────────────────────────────────────────────────────────┐
│                        App Review Information Fields                        │
├─────────────────────────────────────────────────────────────────────────────┤
│ 1. Sign-In Required (Checkbox) & Demo Account (User Name & Password)        │
│ 2. Notes (Plain text instructions, up to 4,000 characters)                  │
│ 3. Attachment (PDF guide, test barcode/QR code, video demo link)            │
│ 4. Contact Information (First Name, Last Name, Phone Number, Email)         │
│ 5. Review Notes for In-App Purchases (Configured per IAP / subscription)    │
└─────────────────────────────────────────────────────────────────────────────┘

Designing Secure, Scoped Reviewer Access

If your application requires user authentication, providing active demo account credentials is mandatory. However, creating test access must not compromise production security.

[!CAUTION] Security Requirements for Reviewer Access: - Never create production backdoors: Do not hardcode universal bypass tokens or backdoors into mobile client binaries. - Do not disable MFA globally: Never disable Multi-Factor Authentication for all users to accommodate a review. - Do not use universal static OTP codes: Do not accept a fixed code (like 000000) for all accounts in production. - Never include production administrative passwords or master database connection strings in review notes.

Safe Reviewer Access Principles

  1. Dedicated, Isolated Reviewer Account: Create a dedicated user record (e.g., apple_reviewer@yourapp.example) used exclusively by Apple. Assign it standard end-user privileges—never admin or internal support roles.
  2. Never Require Real Phone Numbers or SMS OTP: Reviewers evaluate apps from Apple facilities worldwide and cannot receive real-time SMS verification codes sent to developer phones. For phone-based authentication, use your provider's official, isolated testing facility (such as Firebase Auth's designated "Phone numbers for testing" sandbox list or Twilio test credentials) configured with a static verification code strictly bound to that dedicated test number. Never create global backdoor bypasses, never accept static OTPs across general production accounts, and never disable MFA globally for real users. If your backend cannot securely sandbox SMS authentication, provide reviewers with an alternative pre-cleared email/password test account in your App Review notes.
  3. Pre-Seed Synthetic Data: A blank account with zero data makes the app look broken. Pre-populate the demo account with sample items, transaction history, or demo folders so the reviewer immediately experiences active functionality.
  4. Pre-Grant Premium Tiers: If your app gates features behind subscriptions or paid tiers, provision the demo account with an active Pro status so the reviewer can test premium features without completing a live payment.
  5. Keep Credentials Active Throughout Review: Review can take from several hours to multiple days. Do not expire the demo account password or purge test data until the app is officially approved and released.

Step 1: Draft App Review Instructions with Your AI Assistant (Prompt)

Use your AI coding assistant to draft clear, structured review notes tailored to your application:

[!CAUTION] Keep Sensitive Credentials Out of AI Chat: Never paste real production passwords, private keys, or personal credentials into AI chat prompts. Instruct your assistant to draft the notes structure using placeholder tokens (e.g., [REVIEWER_PASSWORD]). You will enter the actual dedicated test account password directly in App Store Connect or via a secured workflow.

TEXT
Help me prepare the App Review notes for [Your App Name]. Do NOT ask me for real passwords or production secrets; use placeholder tokens like [REVIEWER_PASSWORD] in the draft.

Ask me for any needed context regarding:
1. Whether sign-in is required and the non-secret username/email for the dedicated test account.
2. Core features to test in order of importance.
3. Subscriptions, in-app purchases, or gated tiers.
4. Any hardware dependencies, location requirements, or simulator demo modes.
5. Developer contact information for review emergencies.

Draft clear, professional instructions for Apple's reviewer, structured with numbered steps, staying well within Apple's 4,000-character limit. Show the drafted notes to me for review so I can paste them into App Store Connect alongside the real test password.

What Your Assistant Does:

  • Interviews you for necessary application specifics without soliciting private credentials.
  • Synthesizes instructions into a scannable, numbered format designed for rapid evaluation within 4,000 characters.
  • Uses placeholders for passwords and formats hardware workarounds clearly.

Example: Effective App Review Notes Template

Below is a realistic, structured example for an AI productivity app:

TEXT
Welcome Apple App Review Team!

Thank you for reviewing [Your App Name] version [1.2.0].

DEMO ACCOUNT CREDENTIALS:
- Username: reviewer_test@example.com
- Password: [SecureUniquePasswordEnteredInASC]
- Account Status: Pre-provisioned with 10 sample projects and active Pro subscription access.
- 2FA Note: Multi-factor authentication is pre-cleared for this dedicated test account.

STEP-BY-STEP TESTING GUIDE:
1. Launch the app and tap "Log In".
2. Enter the demo credentials provided above.
3. On the main Dashboard, tap "+ New Project" to open the AI generation assistant.
4. Tap "Generate Plan" to test streaming API responses.
5. Navigate to "Settings" -> "Manage Subscription" to verify the StoreKit paywall presentation (Sandbox mode).

HARDWARE / LOCATION NOTES:
- This app includes an optional Bluetooth sensor sync. Because hardware is not present during testing, we have provided a built-in Mock Data Mode: go to Settings -> Developer Options -> toggle "Simulate Bluetooth Sensor".

DEVELOPER CONTACT:
If you have any questions or encounter any issues during evaluation, please contact our team directly:
- Name: [Your Name]
- Email: [developer@example.com]
- Phone: [+1 (555) 012-3456]

Step 2: Applying Review Details to App Store Connect

Review details must be entered directly in the App Store Connect web portal, while FlightDeck verifies that required review fields are attached before submission:

Method A: Web Portal (Primary Setup for Credentials & Notes)

Apple's App Store Review Information fields (Sign-In credentials, reviewer notes, attachments, and emergency contact) are submitted via App Store Connect. Because of security considerations and Apple API scoping, enter your dedicated test account password directly in the App Store Connect web portal. FlightDeck does not generate production passwords or capture private credentials from chat.

  1. Log into App Store Connect and navigate to Apps $\rightarrow$ [Your App].
  2. Select your active version draft under iOS App (e.g., 1.2.0).
  3. Scroll down to the App Review Information section: - Check Sign-In Required if your app has a login screen. - Enter the User Name and Password (the real dedicated test account credentials). - Paste your structured instructions into the Notes box (up to 4,000 characters). - If hardware demonstration is required, upload an attachment (e.g., PDF guide or video link). - Provide your Contact Information (name, phone, email).
  4. Click Save in the top-right corner.

Method B: FlightDeck-Assisted Readiness Verification

While demo passwords and contact details are saved in App Store Connect, FlightDeck's MCP tools verify that review information is complete before you submit.

Instruct your AI assistant:

TEXT
Check if our App Review Information is properly attached and configured for [Your App Name] using FlightDeck.
Verify that demo credentials and reviewer notes are recognized on our active version draft, and confirm that release readiness checks pass.

What Your Assistant Does Behind the Scenes:

  1. It calls FlightDeck's release_readiness_check to verify that appStoreReviewDetail exists and is associated with the version draft.
  2. It inspects whether the demo account flag, notes, and contact phone/email are populated.
  3. It confirms that the app is ready for submission without triggering a "Need Demo Account" rejection.

Important: Drafting Notes vs. Submitting for Review

Important

Saving Review Notes Does NOT Submit the App:

Preparing reviewer notes and entering demo credentials updates your version draft. It does not send the application to Apple's review queue.

Once notes, binary builds, screenshots, and pricing are verified with release_readiness_check, your assistant prepares a formal review submission draft using review_submission_create_draft before final submission. See our companion guide on Creating and Submitting an App Review Draft via FlightDeck.


Verification Prompt: Read Back Submitted Information

After saving your review notes, verify that Apple's API has recorded your details:

TEXT
Inspect our active version draft in App Store Connect using FlightDeck. Confirm that App Review notes and contact details are attached, and verify that our submission container has no outstanding compliance warnings.

Expected Assistant Output:

TEXT
App Review Information Audit for [Your App Name] v1.2.0:
- Sign-In Required: Enabled
- Demo User Name: Configured (reviewer_test@example.com)
- Demo Password: Set (hidden)
- Notes Length: 1,142 / 4,000 characters
- Contact Details: Configured (Name, Email, Phone present)
- Release Readiness Gate: PASS (All review details attached)

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store