Guideline 2.1: "App Completeness"

What this rejection means

A reviewer tried to use your app on a real device and something stopped them. Unlike Guideline 4.2, this is not a judgment about your idea. It is a report that the app, as submitted, was not finished or did not work in their hands.

2.1 covers several different problems, and the message tells you which one you got:

• Crashed on launch or crashed during use. Apple usually attaches crash logs.
• A bug. A button did nothing, a screen stayed blank, a form never submitted.
• Placeholder content. "Lorem ipsum", "Coming soon", sample users, test data, empty pages.
• "Information needed": demo account. The app needs a login and the reviewer had no working account to use. This one often arrives with the words "Information Needed" instead of "Rejected".
• Incomplete app. Parts of the app were clearly not built yet.

The good news: Apple is telling you exactly what broke. The bad news: it often breaks only on the reviewer's device, not yours.

Why apps built with AI tools get this so often

AI builders are great at making something that works in a preview window. Review happens somewhere else: on an iPad, on a fresh install, with no saved login, sometimes with a slow connection.

• It was only ever tested on one phoneReviewers often use an iPad. Layouts and wrappers that were fine on your iPhone can crash or show a blank screen there.
• The backend was asleep or unreachableFree hosting tiers pause, preview links expire, and a paused database makes the app open to nothing at all.
• Placeholder text and sample data shippedAI tools fill screens with example content so they look complete. Reviewers read it.
• No demo account, or one that didn't workThe app needs a login, but the reviewer was given nothing, or the account was never activated.
• Links that only worked in the builderButtons pointing at a preview address, a local address, or a page that was never built.

What Apple is actually asking for

"Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission."App Store Review Guidelines, 2.1(a) — developer.apple.com

In plain English: send the finished app, make sure it works on a real device, and make sure a stranger can get through it. If part of the app needs an account, give the reviewer one that works. If something is not ready yet, it should not be in the app.

What we fix

We start by reproducing the problem on a real device, including iPad, the same way a reviewer would. Then we fix what we find. The most common issues:

We work inside your own project and your own developer account. When it is ready, the new build is resubmitted from your account with the notes a reviewer needs, including a working test login if your app has one.

How long it takes

2.1 is usually the quickest of the common rejections to resolve, because the problem is specific. The store's own review time is the slow part.

1. Day 0
   You share your project and the rejectionInclude the crash logs or screenshots Apple attached, if any. It all goes in your dashboard.
2. Day 1
   We reproduce it on a real deviceYou get a plain-English note: what broke, where, and what we will do.
3. Days 1–3
   We fix and test itMost 2.1 fixes are done within a day or two. We test on iPhone and iPad before anything goes back.
4. Then
   Resubmitted from your accountApple reviews it again, usually within one to three days.
5. Done
   Approved, or we go againUnlimited resubmissions are included. Full refund if it is never approved.

What happens if you ignore it

Nothing dramatic. Your submission stays rejected and the app stays off the store. If Apple asked for information, such as a demo account, the request simply waits for your reply. There is no penalty for taking your time.

What you should avoid is resubmitting without changing anything, hoping a different reviewer gets a different result. Crashes are reproducible, and the next reviewer will hit the same one. Each round costs you a few days of review time.

Often rejected together with 2.1

Built with an AI tool?

Each builder has its own patterns. See what we usually find for yours:

Questions about Guideline 2.1