App Completeness

2.1 covers 'we couldn't complete our review.' It is the most fixable rejection, but only if you reproduce what the reviewer saw. Reviewers test on current hardware, including iPad.

What it means

The reviewer hit a crash, a bug, a placeholder, a broken login, or couldn't test the app because something they needed was missing.

Common causes

• Crash on a specific device (often iPad) or iOS version
• Demo account missing or not working
• Placeholder content or links that go nowhere

How to fix it

1. 1.Read the rejection for the device and OS version. Reproduce on that exact setup or simulator.
2. 2.If it's 'Information Needed', add a working demo account and any special steps to App Review notes.
3. 3.Test the iPad layout even if you only built for iPhone; iPhone apps run there too.
4. 4.Remove placeholder text, dead buttons and broken links.
5. 5.Test a clean install, not just an update over your dev build.

Usually 1 to 2 rounds to fix. Rewording alone works sometimes. If the problem was missing info (demo login), a better reply alone can clear it.

What to write to App Review

Keep it short, factual and specific. Edit the brackets to match your build.

Hello,

Thank you for the report. We reproduced the issue on [device, iOS version] and fixed [cause]. The new build [build number] has been tested on [devices]. A demo account is provided in the review notes: [login].

Thank you.

Independent developer, not affiliated with Apple. Guidelines change, so check Apple's current App Review Guidelines.