AI app builders get you from idea to a working build fast. Then you submit to the App Store, and the rejection email arrives. It's frustrating, but it isn't personal: Apple doesn't reject apps for being AI-built. The App Review Guidelines don't mention AI-assisted development at all.
What happens is that AI-generated apps run into the same rules every app faces, more often and all at once. Here are the rejections we see most, and how to fix each one.
Apple App Store rejections
Guideline 2.1: App Completeness
What it looks like: the app crashed during review, a button does nothing, there's placeholder text, or the reviewer couldn't log in.
Why AI-built apps hit it: AI-generated code works on the happy path and on the simulator. Review uses real devices, sometimes iPads, and fresh installs with no cached data.
Fix:
- Test a fresh install on a real iPhone and an iPad, including with no network.
- Remove every "Lorem ipsum", "Coming soon" and dead link.
- If the app needs a login, give review a working demo account in App Store Connect, with sample data.
- Add crash reporting before submitting, so you can see what the reviewer saw.
Guideline 4.2: Minimum Functionality
What it looks like: "Your app provides a limited user experience" or "is primarily a repackaged website."
Why AI-built apps hit it: many web-first AI builders produce web apps, and wrapping one in a WebView is the shortest path to "an app." Apple treats a thin wrapper around a website as not enough.
Fix: use real native capability, such as native navigation, push notifications, offline support, device features or widgets, so the app does something the website can't. If your builder produced a web app, rebuilding the client in Expo is often faster than fighting 4.2. See exporting code from an AI app builder.
Guideline 4.3: Spam
What it looks like: "Your app duplicates the content and functionality of other apps."
Why AI-built apps hit it: generic AI templates produce similar-looking apps in saturated categories like habit trackers, AI chat wrappers, to-do lists and calculators. In June 2026, Apple added language against apps that are indistinguishable from what's already widely available, and said apps in oversaturated categories that aren't updated or don't attract customers may be removed.
Fix: make the difference obvious, in a specific audience, workflow, data source or feature, and show it in your screenshots and review notes. If you publish several apps, don't ship near-identical versions from one template.
Guideline 2.5.2: Running downloaded code
What it looks like: rejection or a blocked update for apps that download and execute code that changes their features.
Why it matters in 2026: Apple has blocked updates to vibe-coding apps that generate and run other apps inside themselves. This affects apps that are AI app builders, not apps built with one.
Normal OTA updates are fine. Shipping JavaScript fixes with EAS Update is widely used and accepted, as long as updates don't change the app's primary purpose or sneak in features review didn't see.
Guideline 5.1.1: Privacy and data collection
What it looks like: missing privacy policy, vague permission prompts, or no way to delete an account.
Fix:
- Account deletion: apps that let users create an account must let them delete it from inside the app.
- Permission purpose strings: explain specifically why you need the camera, location or photos ("to scan receipts," not "the app needs access"). In Expo, set these in your app config.
- Privacy manifest: apps and SDKs that use certain system APIs must declare why in a privacy manifest. Keep Expo and native SDKs up to date so their manifests are included.
- App Privacy details in App Store Connect must match what the app and its SDKs actually collect.
Guideline 4.8: Login services
If you offer sign-in with Google or another third-party service, Apple requires an equivalent privacy-focused login option as well. Sign in with Apple is the usual answer. Our Expo authentication guide covers it.
Guideline 3.1.1: In-app purchases
Digital goods and subscriptions sold inside the app generally have to use Apple's in-app purchase system. AI-generated apps often drop in a Stripe checkout for a subscription, which gets rejected. Since a 2025 US court ruling, apps on the US storefront can also link out to web checkout, but the in-app purchase flow itself still has to follow the rules. See our RevenueCat guide.
Google Play rejections and blockers
The 12-tester closed test
New personal developer accounts must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. Organization accounts are exempt, which is one reason to register as a company with a D-U-N-S number.
Target API level
Since August 31, 2026, new apps and updates must target Android 16 (API 36). Older Expo SDKs and AI builder exports often target lower levels. See our API 36 migration guide.
Data safety and account deletion
The Data safety form must accurately describe what you collect, including data collected by SDKs. Apps with accounts must also provide a way to request deletion, both in the app and through a web link listed in Play Console.
Sensitive permissions
Google restricts broad access to photos and videos, background location and some other permissions to apps with a core need for them. If you only need users to pick an image, use the system photo picker rather than requesting full media access.
AI-generated content
If your app generates content with AI, Google Play's policy requires a way for users to report or flag offensive output, and the content must follow Play's content rules.
A pre-submission checklist for AI-built apps
- Fresh install tested on real iPhone, iPad and Android devices
- No placeholder content, dead buttons or broken links
- Demo account with sample data in review notes
- Clear, specific permission purpose strings
- In-app account deletion that actually deletes data
- Privacy policy URL, App Privacy details and Data safety form match reality
- Sign in with Apple alongside any third-party login
- Digital purchases through store billing
- Current target API level on Android
- Screenshots and description that show what makes the app different
Our step-by-step guide to publishing an Expo app on the App Store and Google Play covers the full submission process. Rejections are also a good moment to check the parts reviewers don't test, like database access rules and payment verification. Run through our AI-built app security checklist before you resubmit.