# Guideline 2.1 - Information Needed - New App Submission

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

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-21-information-needed-new-app-submission

## Description

We need additional information to continue the review of this new app. To help us understand the app and conduct a complete review, app submissions should include relevant details in the App Review Information section in App Store Connect.

Apple uses this rejection when the App Review Information notes don't include the context reviewers need to evaluate a new app. The fix is informational, not technical — fill in the six items below in App Store Connect.

## Common variations

- First submission
- Updated submission missing notes
- New app on existing developer account

## Example rejection email

```
Guideline 2.1 - Information Needed - New App Submission

We need additional information to continue the review of this new app. To help us understand the app and conduct a complete review, app submissions should include relevant details in the App Review Information section in App Store Connect.

Next Steps

Reply in App Store Connect with all of the following information:

1. A screen recording captured on a physical device demonstrating the app's functionality. The recording must begin with launching the app and show the typical user flow through its core features. If the app has any of the following, include them in the recording:
- Account registration, login, and account deletion flows
- Accessing paid content or features within the app, including any purchase or subscription flows
- User-generated content, including content reporting and blocking mechanisms
- Any prompts requesting access to sensitive data or device capabilities (for example, location, contacts, camera, or microphone)
2. A description of the app's purpose, including the problem it solves and the value it provides its intended audience
3. Instructions for accessing and reviewing the app's main features, including any required test or login credentials
4. A list of the external services, tools, or platforms the app uses to deliver its core functionality (for example, data providers, authentication services, payment processors, or AI services)
5. Describe any regional differences in the app's features or content, or confirm that the app functions consistently across all regions.
6. If the app operates in a highly regulated industry, any relevant documentation or credentials to demonstrate you are authorized to provide these services

Include this information in the Notes field of the App Review Information section in App Store Connect for future submissions.
```

## Resolution steps

01. **Record a screen capture on a physical device**
Capture your app launching and walking through its core features on real hardware (Simulator recordings are rejected). The recording must include any of these flows that exist in your app: account registration, login, and account deletion; any purchase or subscription flows; user-generated content with reporting and blocking mechanisms; any prompts requesting access to sensitive data (location, contacts, camera, microphone). Upload to App Store Connect → App Review Information → Attachment.
## Quick prep checklist
- iPhone, not Simulator
- Start by launching the app from the home screen
- Show the typical user path through the main feature
- Trigger every permission prompt your app uses
- If you have IAP, complete a sandbox purchase on camera

02. **Write a clear app purpose statement**
Describe in 2-3 sentences: what problem your app solves, who it's for, and what the user actually does with it. Reviewers use this to understand what they're looking at before they tap anything. Avoid marketing copy.
## Example
"MealMate helps busy parents plan a week of family dinners in under 5 minutes. It generates personalized meal plans from saved family preferences and dietary restrictions, then builds a grocery list."

03. **Provide test credentials**
If your app requires a login, give the reviewer a working test account in the Notes field. Format: `Email: review@yourapp.com / Password: ReviewTest2025!`. If your app has no login, write "No login required." If access requires additional steps (invite code, MFA disabled for review account), spell those out.
## Quick checks
- Test credentials work right now (log in with them yourself before submitting)
- The account isn't restricted (paid tier, role-gated, or geo-locked)
- MFA is disabled or you've documented the workaround

04. **List external services**
Name every third-party service your app calls to deliver core functionality: backend (Supabase, Firebase, custom API), payments (Stripe, RevenueCat), auth (Auth0, Clerk), AI (OpenAI, Anthropic), analytics (PostHog, Mixpanel), error monitoring (Sentry). One line per service with what it does. Reviewers use this to understand data flows.

05. **Confirm regional consistency**
If your app behaves the same way in every country you ship to, write "App functions consistently across all regions. No region-locked features or content." If features or content differ by region (e.g., a feature only available in the EU, content blocked in certain countries), describe what changes where.

06. **Document regulated-industry credentials (if applicable)**
If your app operates in a regulated industry — health (HIPAA, FDA), finance (FINRA, money transmission), gambling, government services, telemedicine, alcohol/tobacco delivery — provide documentation of your authorization. Examples: HIPAA BAA, gaming license number, money transmitter license. If your app is NOT in a regulated industry, write "Not applicable — this app does not operate in a regulated industry."

## Before / after examples

**Before:** Test login: testuser@app.com / password123. Let me know if you have questions.
**After:** 1. Screen Recording: Attached. Recorded on iPhone 15 Pro running iOS 18, demonstrates app launch → onboarding → main feed → photo upload (triggers camera permission) → purchase flow (sandbox).

2. App Purpose: MealMate helps busy parents plan a week of family dinners in under 5 minutes. It solves the daily 'what's for dinner' decision by generating personalized meal plans from saved family preferences and dietary restrictions.

3. Test Credentials: Email: review@mealmate.app / Password: ReviewTest2025! No additional steps required.

4. External Services: Supabase (auth + Postgres), Stripe (subscription billing), OpenAI (recipe generation), Sentry (error monitoring).

5. Regional Differences: App functions consistently across all regions. No region-locked features or content.

6. Regulated Industry: Not applicable — this app does not operate in a regulated industry.
**Why it works:** The 'before' note gives reviewers credentials but no context — they have to discover what the app does on their own. The 'after' answers all six items Apple now requires, so the reviewer can complete the review without a back-and-forth.

## Common questions

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

Typical turnaround is 1 day (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-new-app-submission*