← Back to BlogSaaS Growth

How to Fix App Store Rejection: Guideline 2.1 App Completeness

H
HowToApprove Editorial Team
2025-02-038 min read

How to Fix App Store Rejection: Guideline 2.1 App Completeness

Bottom line: Guideline 2.1 rejections happen because Apple's reviewer could not complete a core function in your app. The fix is always the same: identify the exact broken flow, fix it, provide a demo account in reviewer notes, and resubmit.

What Guideline 2.1 Covers

Apple Guideline 2.1 states that apps must be "complete, fully functional, and ready for App Store review." It is a catch-all for:

  • Crashes on launch or during core flows
  • Placeholder content (lorem ipsum, "TODO" screens)
  • Features requiring backend access that was not available to the reviewer
  • Login-gated apps with no demo account provided
  • Broken links or non-functional buttons
  • Most Common 2.1 Sub-Reasons

    2.1.0 — Crashes

    Your app crashed during the reviewer's session.

    Fix:

  • Run Instruments (Xcode) on a real device to capture the crash stack trace
  • Test cold launch, backgrounding, and resuming
  • Test on the oldest iOS version your app supports
  • Check for force-unwrapped optionals and missing nil checks
  • 2.1.1 — Incomplete User Interface

    Screens appear broken, text is cut off, or elements do not respond to touch.

    Fix:

  • Test on both small (iPhone SE) and large (iPhone Pro Max) screen sizes
  • Check all Auto Layout constraints for conflicts
  • Test in both light and dark mode
  • 2.1.2 — Server-Side Features Unavailable

    Your app requires a live backend, but the reviewer could not reach it.

    Fix:

  • Ensure your server is live and accessible (not localhost or VPN-only)
  • Provide test credentials that work without special setup
  • Add a note in the reviewer notes: "Please use the following test account: email / password"
  • 2.1.3 — Login Required With No Demo Account

    The app requires account creation or login and the reviewer could not proceed.

    Fix:

  • Add these to reviewer notes in App Store Connect:
  • - Test email address

    - Password

    - Any OTP or 2FA bypass instructions

  • Consider adding a "Continue as Guest" option
  • 2.1.4 — Placeholder Content

    The reviewer found screens with "Coming Soon," empty states, or lorem ipsum text.

    Fix:

  • Remove all incomplete screens before submitting
  • If a feature is planned but not built, remove all UI references to it
  • Use noindex routing to hide incomplete screens from navigation
  • How to Write Good Reviewer Notes for 2.1

    In App Store Connect → App Information → Review Notes, write:

    > "Test account: reviewer@example.com / Password123!

    >

    > Main flow: After logging in, tap 'New Project' to create a project. All core features are accessible from the dashboard. If you encounter a blank screen on first launch, please wait 3 seconds — initial data sync takes a moment on new accounts."

    Resubmission Strategy

    Do not make many changes at once. Fix only what the rejection message specifies. Making unrelated changes alongside the fix can introduce new issues and extend review time.

  • Fix the specific 2.1 issue
  • Write a clear note in the Resolution Center explaining what changed
  • Resubmit and wait
  • Frequently Asked Questions

    How do I know exactly what the reviewer tested?

    Apple's rejection message will describe the steps they took. Read it carefully — they often describe the exact tap sequence that caused the crash.

    Can I request a call with an App Store reviewer?

    No, but you can communicate via the Resolution Center. For critical launch situations, Apple Developer Support can escalate complex cases.

    Does fixing a 2.1 rejection reset my place in the review queue?

    Yes. Resubmissions re-enter the review queue. Typical wait time is 24–48 hours.

    If my app was approved before, can a new version get a 2.1 rejection?

    Yes. Every build is reviewed independently. A regression in a new version can trigger a 2.1 rejection even if previous versions were approved.

    #app store#apple#guideline 2.1#rejection

    Check Your Approval Chances

    Use our AI tool to get a personalized analysis and roadmap