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.
Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
What the reviewer hit, and the fix
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.
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.
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.
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.
Resubmit before Apple’s holiday slowdown
Pay for the Diagnosis and send the rejection and access to the app by (US Eastern). The Diagnosis is back by . Pay for the Fix that day and it arrives as a pull request by , in time to build and resubmit before .
In past years Apple said reviews may take longer around the holidays: December 20 to 26 in 2024 (opens in a new tab), December 22 to 27 in 2023 (opens in a new tab), December 23 to 27 in 2022 (opens in a new tab). Apple hasn’t posted its 2026 dates yet (checked ). Approval stays Apple’s decision.
“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
Related: App Store Guideline 5.1.1 · App Store Guideline 4.3 · App Store Guideline 2.2 beta testing · App Store Guideline 2.3.1 Notes for Review