Skip to content
Get a quote

App Store rejectionGuideline 2.1 - Performance - App Completeness

App Review couldn’t use part of your app, so it sent the build back. The message in App Store Connect says which part. Here’s what each cause means in Apple’s own words and how to fix it, or hand it over at a fixed price.

Short answer

Two common causes of 2.1 rejections are a reviewer who couldn’t sign in and a build that crashed on their device. Add a demo account that works to the review notes, keep your back end running during review, and test the exact build on a real device before you resubmit.

What the reviewer hit, and the fix

  1. 01

    The reviewer couldn’t sign in

    “include demo account info (and turn on your back-end service!) if your app includes a login.” Apple, Guideline 2.1(a)

    Add a demo account that works on the build under review to the App Review Information in App Store Connect, and check that the server it signs in to is the one that build uses. Check that your back end doesn’t block the network or country the reviewer connects from.

  2. 02

    The app crashed or didn’t work

    “We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.” Apple, Guideline 2.1(a)

    Open the crash log if one is attached to the rejection, or the crash reports in Xcode Organizer, and fix the crash. Then test the release build on a real device, including on a slow network, since the reviewer’s conditions may differ from yours.

  3. 03

    Placeholder content was left in

    “placeholder text, empty websites, and other temporary content should be scrubbed before submission.” Apple, Guideline 2.1(a)

    Search the app and its App Store listing for lorem ipsum, "coming soon" screens, empty pages and links that go nowhere. Replace them with the real content, or remove the feature from this version.

  4. 04

    In-app purchases weren’t there

    “If any configured in-app purchase items cannot be found or reviewed in your app, explain the reason in your review notes.” Apple, Guideline 2.1(b)

    Make each in-app purchase visible and buyable in the build under review, and submit the products for review with it. If a product can’t be shown, say where it is and why in the review notes.

Checked against the vendor’s docs on : Apple: App Review Guidelines, 2.1 App Completeness (last updated October 16, 2026); Apple: App Review (replying and appeals); Apple Developer Forums: Guideline 2.1 rejection threads.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: App Store Guideline 5.1.1 · App Store Guideline 4.3

Questions

More on this rejection

Should I reply to App Review or appeal?

Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.

The reviewer found a bug I can’t reproduce. What now?

Ask for details in your reply in App Store Connect: the device, the OS version and the steps. Test on that device and OS, and on a slow or unreliable network, since a loading screen that never ends often means the app couldn’t reach its server.

Can I resubmit the same build?

If nothing in the binary was wrong, for example the demo account had expired, fix the account, explain it in your reply and resubmit. If the build crashed, upload a new build with the fix.

Can you fix it for me?

Yes, through the App Fix Ticket: you send the rejection message and access to the app, Simon writes a diagnosis of what App Review hit and how to fix it, then fixes the code so you can resubmit. Each step has a fixed price, paid upfront. Approval stays Apple’s decision; the ticket covers the fix.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes