# Guideline 2.1 - Information Needed: Invalid Demo Account Credentials

**Guideline:** 2.1 · **Store:** Apple App Store · **Difficulty:** easy · **Typical turnaround:** 30 minutes - 2 hours

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-21-information-needed-invalid-demo-account-credentials

## Description

Apple was unable to sign in with the demo account credentials you provided in App Store Connect. Every submission that requires authentication must include working demo credentials so the review team can access the app's full features and functionality. This is one of the most common and easily preventable rejections.

## Common variations

- Demo account credentials are invalid or expired
- Demo account requires two-factor authentication Apple can't complete
- Demo account has been locked or deactivated
- Demo account doesn't provide access to all features
- No demo credentials provided for an app that requires login
- Demo account requires a phone number or device Apple doesn't have
- Demo account subscription has expired

## Example rejection email

```
We were unable to sign in with the following demo account credentials you provided in App Store Connect. To avoid delays, it is essential to provide access to the app's full features and functionality with every submission. Provide the username and password for a valid demo account in App Store Connect that provides full access to the app's features and functionality or include a demonstration mode that shows all of the features and functionality available in the app.
```

## Resolution steps

1. **Create a dedicated review account** — Set up a permanent test account specifically for App Review. Never use a personal or production account that might get modified or deactivated.

2. **Disable two-factor authentication** — Apple's reviewers cannot complete 2FA, SMS verification, or CAPTCHA challenges. Ensure the demo account can log in with just a username and password.

3. **Pre-populate the account with data** — The account should show the app in a realistic state with sample data, active subscriptions, and all features unlocked. An empty account may trigger further questions.

4. **Verify credentials before every submission** — Log in with the exact credentials you provide in App Store Connect immediately before submitting. Accounts can expire, passwords can be reset by teammates, or backend changes can invalidate sessions.

5. **Handle region or phone-based accounts** — If your app requires a phone number for sign-up, create an account in advance and provide the login credentials. Include any necessary country/region info in the reviewer notes.

6. **Grant full access** — The demo account must have access to ALL features, including premium/paid tiers. If your app has a subscription, ensure the demo account has an active subscription that won't expire during review (which can take several days).

7. **Add reviewer notes** — In App Store Connect under "App Review Information," include step-by-step login instructions, especially if the flow is non-standard (e.g., phone number login, magic link with fallback, SSO).

8. **Resubmit** — Update the demo credentials in App Store Connect and resubmit. This rejection type is resolved instantly once valid credentials are provided.

## Appeal guidance

This rejection type rarely needs an appeal — it's resolved by providing working credentials. If you believe the credentials are correct, try logging in yourself from a different device and network. If the issue is that Apple can't reach your server (e.g., geo-blocking or IP restrictions), mention this in your reply and whitelist Apple's IP ranges.

## Before / after examples

**Before:** Demo account password was changed by another team member after the last submission, causing Apple's sign-in attempt to fail
**After:** Created a dedicated 'applereview@company.com' account with a stable password, documented in a shared vault, and verified login immediately before each submission
**Why it works:** Use a dedicated, stable review account that no one else modifies

**Before:** App requires SMS verification on first login, which Apple's reviewer cannot complete
**After:** Added a bypass flag for the review account that skips SMS verification, or pre-verified the account so it doesn't trigger 2FA on the reviewer's device
**Why it works:** Ensure the demo account can authenticate without any interactive verification steps Apple can't perform

## Common questions

**Can you appeal a 2.1 rejection?**

This rejection type rarely needs an appeal — it's resolved by providing working credentials. If you believe the credentials are correct, try logging in yourself from a different device and network. If the issue is that Apple can't reach your server (e.g., geo-blocking or IP restrictions), mention this in your reply and whitelist Apple's IP ranges.

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

Typical turnaround is 30 minutes - 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-information-needed-invalid-demo-account-credentials*