App Store Rejection Guideline 2.1 App Completeness: Decoded

What guideline 2.1 app completeness actually checks

Guideline 2.1 sits under "Performance" in Apple's App Review Guidelines. Rule 2.1(a) says submissions "should be final versions with all necessary metadata and fully functional URLs included" and that "placeholder text, empty websites, and other temporary content should be scrubbed before submission." It asks you to test on a device, to provide demo account info if there is a login, and to "turn on your back-end service!" It ends plainly: Apple "will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems." Rule 2.1(b) covers in-app purchases. They must be "complete, up-to-date, visible to the reviewer and functional." In short, a 2.1 rejection doesn't judge your idea. It says the reviewer hit something broken, empty or blocked.

How to read a 2.1 rejection message

Before you touch any code, take the message apart. It usually has four useful pieces. Then match the issue sentence to one of the sections below.

• 1. The title. "Guideline 2.1 - Performance - App Completeness" confirms the rule, but not the cause.
• 2. The issue sentence. This is the line that matters. Copy it word for word into your notes.
• 3. The review device and OS version, when Apple includes them. If it says iPad and you only tested on iPhone, you have a lead.
• 4. Attachments. Screenshots or crash logs. A screenshot shows where the reviewer stopped, and a crash log shows what failed.

"Your app crashed" or "crash logs attached"

The build failed on Apple's device. Reviewers install a fresh copy, often on a different device or OS version, without your cached data or logged-in session.

• First check: symbolicate the attached crash log and find the exact line. Don't guess.
• Fix: reproduce it from a clean install on the device and OS named in the message. Test with no network and with a slow one, because a screen that crashes when a request fails will crash for the reviewer too.
• New build needed.

"We found bugs" with an error screenshot or an endless spinner

The app opened, but a screen couldn't load data. This is a frequent cause. Common reasons are a free-tier database paused for inactivity, an API key missing from the release build, an app still pointing to a staging or local server, or a rate limit hit during review.

• First check: run the exact release build on a phone with your laptop closed. If it only works while your dev server runs, you have found it.
• Fix: point the release build to production, add real error handling, and keep the backend on a plan that doesn't sleep during review.
• New build needed if the fix is in the app. If the server was simply off, turning it on and replying may be enough.

"Placeholder content" or "incomplete"

The reviewer saw lorem ipsum, "Coming soon" tabs, test users named "asdf", grey image boxes or empty lists. AI builders often leave generated demo data behind that looks finished until someone reads it.

• First check: search the codebase for "lorem", "TODO", "test", "coming soon" and "placeholder".
• Fix: remove unfinished tabs or hide them behind a flag set to off, and give every empty state a real sentence and a next step ("No bookings yet. Book your first session.").
• New build needed.

"Unable to sign in" or "demo account"

The reviewer never got past your login. The demo account expired, sent a one-time code to your own phone, required email verification, or was wiped in a database reset.

• First check: sign in with those exact credentials from a fresh install.
• Fix: create a dedicated reviewer account with no expiry and no two-factor step. If the app only works after onboarding (a team invite, a paid plan, a linked device), set that account up so it lands on a working home screen. If legal or security rules stop you from sharing an account, Apple accepts a built-in demo mode, but only "with prior approval by Apple."
• Usually no new build: update App Store Connect and reply.

"Support URL", "privacy policy" or "link"

A URL in your listing or in the app didn't work. Apple asks for "fully functional URLs."

• First check: open every listing URL in a private browser window.
• Fix: make sure the privacy policy has its own page, and that in-app "Terms" and "Help" buttons go somewhere real.
• No new build if only the listing URLs were wrong. New build if an in-app link is broken.

"Unable to locate" or "unable to access" a feature

Your description or screenshots promise something the reviewer couldn't trigger, because it needs hardware, a location, an invite code or a second user.

• Fix: explain in the review notes how to reach it, step by step, with an invite code or a short screen recording. If it can't be shown, remove it from the listing for this version.
• Usually no new build.

Anything mentioning in-app purchases

This falls under 2.1(b): the reviewer couldn't find or buy a product you configured. Apple asks you to explain in your review notes why any configured item isn't visible in the app. Purchases and subscriptions are a topic of their own, covered in our mobile app building guides. Matched your message to a code problem in an AI-built app? That usually means the prototype needs engineering, not another prompt. Book a call and we'll tell you whether to harden it or rebuild it.

Reply or resubmit: the quick decision table

For each phrase in the message, here is where the fix lives, whether you need a new build and who fixes it. When you don't need a new build, reply in App Store Connect with what you changed. That avoids a new upload.

• "crashed", crash log. Where the fix lives: code. New build: yes. Who fixes it: developer.
• "bugs", error screenshot, spinner. Where the fix lives: code or server. New build: often. Who fixes it: developer.
• "placeholder", "incomplete". Where the fix lives: code and content. New build: yes. Who fixes it: developer or founder.
• "unable to sign in", "demo account". Where the fix lives: App Store Connect. New build: usually no. Who fixes it: founder.
• "support URL", "privacy policy". Where the fix lives: listing or website. New build: no, unless in-app. Who fixes it: founder.
• "unable to locate feature". Where the fix lives: review notes or listing. New build: usually no. Who fixes it: founder.

How to fix guideline 2.1 performance app completeness before you resubmit

Fix the cause named in the message first. Then run this check, because a second reviewer can find a second problem. Then write review notes that name the fix in plain words, for example: "Fixed the crash on the Profile screen when the network is unavailable. Demo account updated: no expiry, no two-factor. To reach Bookings, log in and tap the calendar icon." Clear notes let the reviewer check your fix without starting from zero.

• 1. Install the release build from TestFlight on a clean device, plus an iPad if your app runs there.
• 2. Sign in with the reviewer account yourself, from a fresh install.
• 3. Go through every screen with the network on, off and slow.
• 4. Open every URL in the listing and in the app.
• 5. If you sell anything, make one sandbox purchase and one restore.

When the message keeps pointing at the app itself

Fix it yourself if the phrases are about sign in, links or unreachable features. Those are settings and notes. Get a developer if crash, bug or placeholder messages come back after you resubmit, or if each fix breaks something else. That pattern usually means the codebase isn't ready for real users yet, and the rejection is just the first symptom. Our web and mobile app development services include TestFlight + Play submission support and 2-week fixes, and you keep 100% of the source on your GitHub. For tool-specific problems, read our guides on Lovable and AI builders. Rejected with launch day getting close? Book a call, send us the rejection message, and we'll tell you where the fix lives.

How long does it take to fix a guideline 2.1 rejection?

That depends on what the message says. A demo account, a broken listing link or missing review notes can be fixed the same day with a reply. A crash or a backend issue needs a code fix, a new build and a new review.

Do I need to upload a new build after a 2.1 rejection?

Only if the problem is inside the app: crashes, placeholder screens, in-app links or code that can't reach the backend. For login details, listing URLs or review notes, update App Store Connect and reply to the reviewer.

What does "Guideline 2.1 - Performance - App Completeness" mean in plain English?

It means the reviewer found the app unfinished: something crashed, looked temporary, didn't load, or couldn't be reached. The sentence under the title tells you which one.

Can an AI-built app pass App Store guideline 2.1 app completeness?

Yes, once it is finished. AI-built apps often get flagged for leftover demo data, missing error handling and backends that only work in development. With those fixed, they go through the same review as any other app.

What if I'm rejected under 2.1 again?

Read the new message as carefully as the first, since it may name a different cause. If the decision isn't clear, ask for details in your reply, or file an appeal with the App Review Board.