The rejection guides

Apple found content in your app it considers offensive, discriminatory, violent, sexual, or false, including anything your AI features can generate.

Your app lets users post content but is missing Apple's required moderation features: filtering, reporting, blocking, and contact info.

Something in your app was broken, unfinished, or unreachable during review: crashes, placeholder content, or a login screen without a demo account.

Apple thinks you submitted a beta, demo, or trial, often just because 'beta' or 'v0.1' appears in your app's name or description.

Apple found features in your app that reviewers couldn't see or you didn't disclose. It's treated as dishonesty and can escalate to account termination.

Your App Store screenshots don't show the app actually being used. Concept art, mockups, or a login screen don't count. Usually a fast fix.

Your app's name, subtitle, or keywords include trademarks, other apps' names, prices, or stuffed search terms. Names are capped at 30 characters.

Your app calls Apple's internal, off-limits code, usually smuggled in by a package or plugin you never knew you were shipping.

You sold digital features through Stripe or another checkout inside the app. Apple requires its own in-app purchase system for digital goods.

Your auto-renewing subscription is missing required disclosures, usually clear pricing, or Terms of Use and privacy policy links.

Apple thinks your app doesn't do enough to justify existing: a repackaged website or thin wrapper. The classic AI web-app-to-iOS rejection.

Apple thinks your app looks like a duplicate of other apps on the store. This is the rejection that hits template and AI-built apps hardest.

Your app misuses push notifications, either requiring them to function or sending marketing pushes without explicit opt-in consent.

Your app offers Google or Facebook login but no privacy-focused option. Apple requires an equivalent choice, and Sign in with Apple satisfies it.

Your app collects data without the required privacy plumbing: a privacy policy, honest permission prompts, or the in-app account deletion Apple requires.

Your app sends user data somewhere without asking first, often via an analytics or ad SDK the founder never knew was in the build.

Your app uses a brand, character, image, or piece of music that belongs to someone else, and Apple wants proof you're allowed to.