Apple rejected my AI-built app. What now?
If Apple rejected your AI-built app, read which guideline the message names, fix that one thing, and reply or resubmit from App Store Connect; most rejections are fixable and a second round is normal. Apple does not reject apps for being built with AI. It rejects them for the same reasons as any other app, and AI-built apps hit three of those reasons more than most: 4.2 Minimum Functionality (the app is only a website in a shell), 2.1 App Completeness (something is broken, unfinished, or the reviewer could not log in) and 4.3 Spam (the app looks like many others already in the store).
Apple says 2.1 alone accounts for over 40% of unresolved issues, and that 90% of submissions are reviewed in under 24 hours. So the waiting is rarely the problem. Going back and forth on a fix that missed what the reviewer meant is.
Below: what each guideline means in plain words, the fix for each, the other rejections AI-built apps get, when to reply, resubmit or appeal, and what is different on Google Play.
In founders’ words
“I'm a non-technical founder. Electrician by trade, I have been building a marketplace on Lovable in my spare time for the last 8 months.”
“Then I ported to iOS and hit the wall. 10+ rejections over 3 months, and not one of them was about code quality.”
“I feel like every time I fix one thing they find something else. Why not list everything at once?”
Read the rejection message first
Open the app in App Store Connect and go to the App Review section. The message names one or more guidelines by number and usually describes the screen or feature the reviewer looked at. Copy the exact text somewhere you can share it, because everything below starts from it.
Then sort the rejection into one of three kinds. A metadata rejection is about the listing (screenshots, description, privacy links, review notes); Apple's help pages say you can fix it and resubmit the same build. A binary rejection is about the app itself and needs a new build. An information request (often "2.1 Information Needed") is a question: answer it in a reply, with screenshots or a short screen recording, and no new build may be needed.
App Store rejected under 4.2 Minimum Functionality
Guideline 4.2 says an app "should include features, content, and UI that elevate it beyond a repackaged website". Apple's App Review page is more direct: "Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not make a quality app." Guideline 4.2.2 adds that apps should not be mainly marketing, web clippings or a collection of links.
This is the rejection most AI-built apps get, because most of them start as web apps. Lovable has no built-in way to submit to the App Store; its docs point to a PWA or a Capacitor wrapper made outside Lovable. Base44's App Store route is, in its own words, a "lightweight native wrapper around your web app". Both can pass, but only if the app does things a website cannot.
- Use the phone: camera, push notifications, Face ID, haptics, share sheet, widgets, offline use. Make each one visible in the first minute of use, not buried in settings.
- Make it feel like an app: native navigation and tab bars, no browser bars, no pinch-zoom on text, no links that open your website.
- Show the reviewer. Name every native feature in the review notes, and add a short screen recording that shows them. A non-technical founder who had built several of these in a Capacitor app was still rejected twice; the reviewer has to see them.
- If the app is truly small, it may need more to do, not more polish. "Not particularly useful, unique, or app-like" is a judgment about substance.
Guideline 2.1 App Completeness rejected
Guideline 2.1 asks for final versions with "all necessary metadata and fully functional URLs", no placeholder text, and no crashes or obvious technical problems. Apple says this guideline is behind over 40% of unresolved issues. For AI-built apps the usual causes are specific:
- The reviewer could not log in. Guideline 2.1 asks you to "include demo account info (and turn on your back-end service!)". Give a working demo account with sample data, and make sure the backend is not paused, out of credits, or asleep when the review happens.
- Something is unfinished. A button that does nothing, a "coming soon" screen, lorem ipsum, a settings page with dead links. Coding agents leave these behind; go through every screen yourself.
- In-app purchases the reviewer cannot find or buy. Guideline 2.1(b) says they must be "complete, up-to-date, visible to the reviewer and functional", or explained in the review notes.
- A crash on the reviewer's device, often an iPad or an older iOS version you did not test.
Write review notes that describe every feature specifically. Guideline 2.3.1(a) says "generic descriptions will be rejected".
Guideline 4.3 Spam, and apps made from templates
Guideline 4.3 covers two things. 4.3(a): do not submit several copies of the same app under different bundle IDs. 4.3(b): do not submit apps "indistinguishable from what's already widely available"; Apple names categories it has enough of, including dating, flashlights, wallpapers, simple timers and fortune telling, and says repeated submissions can lead to removal from the developer program.
AI builders make similar-looking apps easy to produce, so a generic habit tracker or AI chat app can land here even if you built it yourself. The fix is to make the difference obvious: a specific audience, a feature nobody else has, and a listing and screenshots that say so. Guideline 4.2.6 is a related trap: apps created by a "commercialized template or app generation service" are rejected unless the owner of the content submits them, so submit from your own developer account, under your own name or company, never through a service's account.
The other rejections AI-built apps get
- Privacy, 5.1.1. A privacy policy link in the listing and inside the app. If the app creates accounts, it must let people delete them inside the app (5.1.1(v)).
- Third-party AI, 5.1.2(i). If personal data goes to an AI provider, you must "clearly disclose" that and get permission first. Many AI-built apps send user text to a model without saying so.
- Payments, 3.1.1. Features unlocked inside the app must be bought with Apple's in-app purchase. Apple's guidelines let apps on the United States storefront link out to your own website to buy; elsewhere that link needs an entitlement from Apple. Base44's own docs warn that an app taking Stripe payments for digital content is rejected.
- Sign-in, 4.8. If you offer Google or another third-party login, Apple also requires an equivalent private option such as Sign in with Apple.
- Metadata, 2.3. Screenshots must show the app in use, not the login screen. Rork's docs list iPad screenshots, permission text in the app settings and subscription setup as the most common rejection reasons for its apps.
- Downloaded code, 2.5.2. Apps may not download code that changes what they do. This mostly hits apps whose job is generating and running code.
Reply, resubmit or appeal
Reply when the reviewer missed something or asked a question. In App Store Connect you can reply with screenshots and documents until you resubmit. Be specific and polite; guideline 5.6 asks for respect when you communicate with Apple. Resubmit when you changed something: fix exactly what the message names, check the rest of this page for the next likely issue, and describe the change in the review notes. Apple warns that an app "repeatedly rejected for the same guideline violation" takes longer to review.
Appeal to the App Review Board only when you are sure the app complies and the reviewer is wrong. Apple's rules: give specific reasons, one appeal per submission, and answer any request for information first. If you are stuck on the same guideline after two rounds, Apple also offers 30-minute Meet with App Review sessions over Webex to discuss its guidelines. If a launch date is at risk or you are fixing a critical bug, you can request an expedited review.
One useful rule: if a live app is rejected for an unrelated issue when you submit a bug fix, Apple says "bug fixes will not be delayed over guideline violations" except for legal or safety issues. Reply to the offer in App Store Connect and fix the other issue in the next version.
Google Play rejected my app built with AI
Google Play has its own version of minimum functionality: it does not allow apps that crash or "do not have the basic degree of adequate utility as mobile apps", nor apps that are only a webview of a website you do not own. If your app was rejected rather than removed, Google says the last version you published stays live. Fix the issue before submitting again; for removals and suspensions you can submit one appeal per action.
New personal developer accounts (created after November 13, 2023) must first run a closed test with at least 12 testers opted in for 14 days in a row before they can publish to production. That is not a rejection, but it often feels like one. Start the test as soon as you have a build.
When you may not need help, and when you do
If the rejection is metadata, a missing demo account, a placeholder screen, or a missing privacy link, you can fix it yourself in an afternoon. Most first rejections are that kind. Replit's own docs put it plainly: "rejections are common and you can resubmit right away."
Bring someone in when the same guideline comes back after two fixes, when 4.2 means the app needs native features your builder cannot add, when payments have to move to in-app purchase without breaking your web subscribers, or when a launch is waiting on the store. Those are product and architecture decisions, and a free call is a reasonable place to start.
| Guideline | In plain words | The usual fix |
|---|---|---|
| 4.2 Minimum Functionality | It is a website in an app shell | Native features the reviewer can see in the first minute, named in the review notes |
| 2.1 App Completeness | Broken, unfinished, or the reviewer could not log in | A working demo account, backend on, no placeholder screens |
| 4.3 Spam | Looks like many apps already in the store | A clear difference in audience or features, shown in the listing |
| 4.2.6 Templates | Submitted by a template or generator service | Submit from your own developer account |
| 5.1.1 Privacy | Missing privacy policy or account deletion | Policy link in app and listing; delete account inside the app |
| 5.1.2(i) Third-party AI | Personal data sent to an AI provider without saying so | Disclose it and ask permission first |
| 3.1.1 In-app purchase | Digital goods bought in the app outside Apple | Apple in-app purchase for subscriptions and unlocks; a link out only where Apple allows it |
| 2.3 Metadata | Screenshots or description do not match the app | Screenshots of the app in use, for every device size |
Questions
Does Apple reject apps for being AI-built?
No. Nothing in Apple's guidelines is about how the code was written. AI-built apps are rejected under the same guidelines as any app, mostly 4.2 (a website in a shell) and 2.1 (broken or unfinished). The one guideline that touches AI coding is 2.5.2, which bars apps that download or run code that changes what they do. That affects apps whose job is generating and running code for their users, not an app you built with one.
How long does App Store review take after a rejection?
Apple says 90% of submissions are reviewed in under 24 hours on average. Repeat rejections for the same guideline take longer, and a reply in App Store Connect can sit for days with no status change. If a launch date is close, request an expedited review.
My Rork app was rejected. What should I check?
Rork's docs list the most common reasons as permission text in Info.plist, subscription setup and iPad screenshots (a stretched iPhone screenshot is rejected), and say a hard paywall must be stated in the App Store description. Rork also has a paid AI reviewer that flags likely problems before you submit; Apple still makes the final decision.
Can a Lovable or Base44 app pass 4.2?
Yes, but not as a plain wrapper. Lovable leaves packaging to you (a Capacitor shell built outside Lovable), and Base44's mobile app is a web view of your published app. Either passes when the app uses the phone in ways a website cannot and the reviewer can see it.
Should I appeal or just fix it?
Fix it if the reviewer has a point, even a small one; it is faster. Appeal to the App Review Board only when you can say specifically why the app complies, once per submission, after answering any questions Apple asked.
First look, $750. After a free call, we read your whole product and tell you what is finished, what is not, and what to do first.
Setup, $3,000 fixed. We make it ready for real customers, in accounts you own.
Partner, $2,500 a month. We review what your coding agent writes and keep the checks and tests current. Month to month.