App Store rejection guidelines, explained

Guideline 2.1(a): App Completeness

The reviewer hit a crash, a dead button, placeholder text, or a login wall with no working demo account. Usual next move: fix, new build, then reply.

Guideline 2.1: Information Needed

Nothing is broken. The reviewer wants more context, often a screen recording on a physical device, who the app is for, and how it makes money. Usual next move: reply, usually no new build.

Guideline 2.1(b): In-app purchases not found

The reviewer could not find or buy one of your in-app purchases. Usual next move: fix, new build, then reply.

Guideline 2.3: Accurate Metadata

Something in your listing does not match the app or breaks a metadata rule. Usual next move: fix the listing, then reply.

Guideline 2.3.10: Other platforms in metadata

Your app or listing mentions Android, Google Play, or another platform. Usual next move: fix the listing, then reply.

Guideline 2.3.14: Creative assets

New in the Oct 16, 2026 revision: creative assets must relate to your app, suit all audiences, and avoid claims, competitor references, and pricing. Usual next move: fix the listing, then reply.

Guideline 2.5.2: Downloading or executing code

The reviewer believes your app can change its features after review, for example via an over-the-air update system. Usual next move: fix, new build, then reply.

Guideline 2.5.19: Hidden or undocumented features

New number since Oct 16, 2026: anything the reviewer cannot see but the binary can switch on. Usual next move: fix, new build, then reply.

Guideline 3.1.1: In-App Purchase required

You sell digital content with a method other than In-App Purchase, or link to one, outside permitted cases. Usual next move: fix, new build, then reply.

Guideline 3.1.2: Subscriptions

The paywall or listing does not clearly show what subscribers get and the required subscription information. Usual next move: fix, new build, then reply.

Guideline 4.0: Design

The UI looks unfinished: clipped text, broken iPad layout, or odd controls. Usual next move: fix, new build, then reply.

Guideline 4.2: Minimum Functionality

The app is a thin web wrapper, one static screen, or a brochure. Usual next move: change the product, not the wording.

Guideline 4.3(a): Spam: similar binary, metadata, or concept

Your app looks too similar to other apps, your own or someone else's. Common with templates, starter kits, AI-generated apps, and studios that ship many small apps. Usual next move: change the product, not the wording.

Guideline 4.3(b): Spam: saturated category

Your category is one Apple calls saturated, and the reviewer does not see a meaningfully different experience. Usual next move: change the product, not the wording.

Guideline 4.8: Login Services

You offer a social login without an equivalent privacy-focused option. Usual next move: fix, new build, then reply.

Guideline 5.1.1: Privacy: data collection and storage

Privacy policy, permission purpose strings, access scope, forced consent, or account deletion. Usual next move: fix, new build, then reply.

Guideline 5.1.2: Data use, sharing, tracking, third-party AI

Tracking without App Tracking Transparency, gating features on permissions, or sending personal data to a third party (including AI) without clear permission. Usual next move: fix, new build, then reply.

Guideline 1.2: User-generated content

Users can post or generate content, but the app lacks filtering, reporting, blocking, or contact info. Usual next move: fix, new build, then reply.

Guideline 1.5: Developer information

The support URL has no way to contact you, or it is the same as your terms page. Usual next move: fix the listing, then reply.

Guideline 5.6.1: App Store Reviews: custom rating prompts

Your app asks for a rating with its own prompt instead of Apple's system review prompt. Guideline 5.6.1 says to use the provided API, and custom review prompts are not allowed. Usual next move: fix, new build, then reply.