Guideline 2.1
Guideline 2.1 - Information Needed - New App Submission
Our Take
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.
Resolution Guide
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
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."
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
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.
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.
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."
Example Rejection Email
Before & After
Test login: testuser@app.com / password123. Let me know if you have questions.
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.
What changed: 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.
Community Solutions · 0
Sign in to share your solution.
More Guideline 2 (Performance) rejections
- Guideline 2.1 - App Completeness: App Crashes During Review
- Guideline 2.1 - App Completeness: App Requires External Hardware Not Provided for Review
- Guideline 2.1 - App Completeness: Crashes on Launch
- Guideline 2.1 - App Completeness: Demo Account Not Working
- Guideline 2.1 - App Completeness: IAP Products Not Found in Binary
- Guideline 2.1 - App Completeness: Missing App Icon