# Guideline 2.1 - App Completeness: Demo Account Not Working

**Guideline:** 2.1 · **Store:** Apple App Store · **Severity:** low · **Fix difficulty:** easy · **Typical turnaround:** 1-2 hours

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-21-app-completeness-demo-account-not-working

## Description

Apple is rejecting your app because the demo account credentials you provided in the Review Notes are not working. This might mean the credentials are expired, the account was deleted, the server is down, or the credentials were entered incorrectly in App Store Connect. This is surprisingly common and incredibly frustrating because the fix is trivial but the re-review adds days to your timeline. If your app requires authentication to access core functionality, Apple requires working demo credentials. They will not create their own account, and they will not debug your login flow. If the credentials fail on the first attempt, they reject immediately. Common root causes: (1) the demo account password expired or was changed after you submitted, (2) 2FA/MFA is enabled on the demo account, (3) the account was banned or rate-limited by your own anti-fraud system, (4) a server deployment between submission and review broke the auth flow, (5) the credentials in App Store Connect have a typo or trailing whitespace.

## Common variations

- Demo account credentials did not allow us to sign in
- We were unable to access the app with the provided credentials
- The demo account appears to be expired or invalid
- Two-factor authentication prevented us from signing in with the demo account
- The demo account does not have access to the app's core features

## Example rejection email

```
Guideline 2.1 - Performance - App Completeness

We were unable to review your app as the demo account credentials provided in App Store Connect did not allow us to sign in to the app.

Specifically, the username and password provided in the Review Notes did not work when we attempted to log in.

Next Steps:
To help us proceed with the review, please provide working demo account credentials in the App Review Information section of App Store Connect. Ensure the account:
- Has full access to all app features
- Does not require two-factor authentication
- Is not subject to any geographic restrictions
```

## Resolution steps

## Quick Assessment
- **Risk level:** Low
- **Resolution path:** Update credentials and reply in Resolution Center
- **Typical turnaround:** 1-2 hours (no new binary needed)

## The Fix

1. **Test the credentials yourself, right now** -- Open the App Store version of your app (or TestFlight build) and log in with exactly the credentials in your Review Notes. Copy-paste them to check for typos or trailing spaces.

2. **Disable 2FA/MFA on the demo account** -- Apple reviewers cannot complete 2FA. Create a dedicated review account with 2FA disabled.

3. **Check for rate limiting or fraud blocks** -- Your own security systems may have flagged the Apple reviewer's IP (Apple reviews from Cupertino). Whitelist the demo account from rate limiting and fraud detection.

4. **Set a non-expiring password** -- If your system enforces password rotation, exempt the review account. Or set the password to something that won't expire before review completes.

5. **Update credentials in App Store Connect** -- Go to App Store Connect > Your App > App Review Information > Sign-in Information. Update the username and password, then reply in the Resolution Center.

6. **Pre-populate the account with data** -- Make sure the demo account has sample content so the reviewer can see core features without having to create data from scratch.

## Prevention
- Create a permanent, dedicated Apple Review account that bypasses 2FA, password rotation, and rate limiting
- Test the credentials from a clean device after every server deployment
- Set a calendar reminder to verify credentials are working 24 hours after each submission
- Include step-by-step login instructions in Review Notes, not just credentials

## Appeal guidance

No appeal needed. Update the credentials in App Store Connect and reply in the Resolution Center that the credentials have been refreshed. Apple will typically re-review quickly without requiring a new binary.

## Before / after examples

**Before:** Review Notes: 'Username: demo@app.com Password: Test123!' -- but the password was changed during a server migration last week
**After:** Review Notes: 'Username: applereview@app.com Password: ReviewAccess2024! -- This is a permanent review account with 2FA disabled. After login, tap the Explore tab to see sample content.'
**Why it works:** Create a dedicated, permanent review account that won't be affected by password rotations, deployments, or security systems.

## Common questions

**Can you appeal a 2.1 rejection?**

No appeal needed. Update the credentials in App Store Connect and reply in the Resolution Center that the credentials have been refreshed. Apple will typically re-review quickly without requiring a new binary.

**How long does this typically take to fix?**

Typical turnaround is 1-2 hours (difficulty: easy). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-21-app-completeness-demo-account-not-working*