Apple rejected my AI-built app. What does it mean and what do I change?
Short answer: Apple's rejection message names a guideline number, and that number tells you what to change. Apple judges what your app does, not which tool built it, so an AI-built app is held to the same rules as any other. Common problems for apps made from a website are guideline 4.2 (the app is too close to a repackaged website), 2.1 (bugs or missing demo login), 5.1.1 (privacy policy and account deletion) and 4.8 (login options). Fix the exact point, reply in App Store Connect, and resubmit.
Apple rejected your AI-built app and you want to know what the code in the message means, what to change, and how long it will take.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A rejection feels like a verdict on the whole app. It is not. It is a short list of specific things Apple's reviewer could not accept, each tied to a numbered rule in the App Review Guidelines, the public rulebook Apple's reviewers use. In my experience, rejections of AI-built apps tend to come down to a handful of rules, and many are fixable in days rather than months. This guide maps each common code to a concrete change, with a rough effort estimate, a resubmission checklist, and a rule for when your web app needs real native work.
A quick note on what is an "AI-built app" here: an app made largely by an AI app builder such as Lovable, Bolt or Replit (tools where you describe an app in chat and get working code), or by a coding assistant such as Cursor. Those tools often produce a web app first. Getting it onto the App Store means wrapping it for iPhone, and that wrapping is where most problems start. Before you submit, see how to publish a Lovable or Bolt app on the iOS App Store.
Are AI-built apps allowed on the App Store?
Yes. Apple's rules are about what an app does, how it handles data and how complete it is. They do not ban an app because AI wrote the code. Two rules are worth knowing because they touch how AI-built apps are made. Guideline 2.5.2 says apps must be self-contained and may not download, install or execute code that introduces or changes the app's features. Guideline 4.2.6 says apps created from a commercialized template or app-generation service are rejected unless the provider of the app's content submits them. If your app is a generic app produced by a template tool and submitted on behalf of many clients, that is the one to read.
Guideline 5.1.2 also now asks you to clearly disclose where personal data is shared with third parties, including third-party AI, and to get explicit permission first. If your app sends user text to an AI service, tell users and ask.
Step one: read the rejection message properly
Open App Store Connect (Apple's dashboard for managing your apps) and go to the App Review page. Apple says you manage your submissions and communicate with App Review there. Copy the exact wording of each point into a list. A message can cite more than one guideline. Fix all of them in one go, because each resubmission has to be reviewed again. Apple also says that over 40 percent of unresolved issues relate to guideline 2.1 (App Completeness: crashes, placeholder content, incomplete information), so check that one even if it is not cited. Apple says App Review typically reviews at least 50 percent of submissions in less than 24 hours and 90 percent in less than 48 hours, so a resubmission that fixes everything can come back quickly. Stores reject apps without these; see the privacy policy and terms an AI-built app needs before launch.
Code by code: what it means and what to change
The effort figures below are my own rough estimates for a developer who already has the project open. They are not Apple's, and they will be higher if the app has many screens or the problem runs deep.
| Guideline | What Apple means | What to change | My rough effort |
|---|---|---|---|
| 4.2 Minimum Functionality | The app should include features, content and design that go beyond a repackaged website. | Add real app features (see the next section), not just a wrapper around your site. | 2 days to 3 weeks |
| 2.1 App Completeness | Bugs, placeholder text, empty links, no demo login, or the back end switched off. | Test on a real iPhone, remove placeholders, give a working demo account and keep your back end running during review. | Half a day to 2 days |
| 5.1.1 Data Collection and Storage | Missing privacy policy link, no in-app account deletion, or asking for personal data the app does not need. | Add the policy link in App Store Connect and in the app, add a delete-account button, remove unneeded fields. | 1 to 3 days |
| 4.8 Login Services | You offer Google or other social login but no equivalent privacy-focused option. | Add another login service that meets those conditions (Apple's own, Sign in with Apple, is one option), or remove third-party login. | 1 to 2 days |
| 3.1.1 In-App Purchase | You unlock features or digital content with your own payment, a code or a card form. | Use Apple's in-app purchase for digital features, or remove the paywalled part. | 3 days to 2 weeks |
| 2.3 Accurate Metadata | Screenshots or description do not match the app, or release notes are vague. | Show the app in use in the screenshots, and describe new features specifically in the Notes for Review. | Half a day |
| 4.3 Spam | Duplicate apps, or an app indistinguishable from what is already widely available. | Combine apps into one, or make the app meaningfully different. | Depends |
| 4.1 Copycats | The app copies another app or impersonates a service. | Change the name, icon and design, and the idea if needed. | Depends |
Two points about this table. First, the 4.3 and 4.1 rows are the only ones where more code does not help. They are about what the app is. Second, "login" and "privacy" problems are worth checking in an AI-built app because the builder can add login and data collection quickly without any thought for the phone store's rules.
The 4.2 problem: when a web view app needs real native work
A wrapped website is at high risk of a 4.2 rejection. A web view is a window inside an app that just shows a web page. Apple's own list of common rejections describes this exactly: websites served in an iOS app, web content not formatted for iOS and limited web interactions do not make a quality app.
Here is a rule you can use. Open your app and cover the web address in your mind. Ask what the app does that a browser bookmark on the home screen does not. If the answer is "nothing", expect a 4.2 rejection. If the answer is a short list, you may be fine. Features that make an app feel like an app include push notifications that matter to the user, working with the camera or photo library, offline access to key data, saved login with Face ID, and a layout built for a phone screen with native navigation. Do not bolt on gimmicks. A reviewer will see through a feature that exists only to pass review, and your users will too.
If your real answer is "it is a web service and always will be", consider that a mobile website, added to the home screen, may be the right product. That costs nothing in review. See how to move an AI-built app to production for the wider picture of what a live app needs.
The privacy fixes most apps need
An AI-built app with accounts is likely to need at least one of these.
- Privacy policy. Guideline 5.1.1 requires a link in App Store Connect and inside the app. It must say what data you collect, how, and what you use it for, and it should cover any third parties, such as analytics tools.
- Account deletion. If your app lets people create an account, it must let them delete it inside the app.
- Privacy labels. Apple's App Privacy Details page explains you must tell the store what data you or your third-party partners collect. "Third-party partners" includes analytics tools and software kits you added. The answers must stay accurate, and you can update them at any time without a new app version.
- Purpose strings. If the app asks for the camera, location or contacts, the permission prompt carries a short sentence on why (Apple calls it a purpose string), and Apple's guideline 5.1.1 says purpose strings must clearly and completely describe your use of the data. Write yours in plain words for the user.
- AI sharing. If user data goes to an outside AI service, disclose it and ask for permission (guideline 5.1.2).
This overlaps with security. If your app stores customer records, run the AI-built app security checklist before you resubmit, since a privacy label that says one thing and an app that does another is its own risk.
Resubmission checklist
- List every guideline the message cites and write the change next to each.
- Test the final build on a real iPhone, not only a simulator, and on a bad connection.
- Provide a working demo account with sample data, and keep your back end running.
- Remove placeholder text, dead links, test banners and "coming soon" screens.
- Check that the privacy policy link works in App Store Connect and inside the app.
- Add or confirm in-app account deletion and, if you offer social login, an equivalent login option.
- Match screenshots to the real app. They should show the app in use, not just a title or login screen.
- Write specific Notes for Review: how to log in, what each new feature does, and anything unusual.
- Reply to the reviewer in App Store Connect with a short note on what you changed.
- Submit once, after everything is fixed.
If you think the reviewer misunderstood the app, Apple allows an appeal to the App Review Board: give specific reasons you comply with the guidelines and submit only one appeal per rejected submission. Apple also offers 30-minute video appointments to discuss the guidelines and common rejection reasons. For an app that is already on the store, Apple's guidelines say bug fixes will not be delayed over guideline violations except for those related to legal or safety issues, and you can use App Store Connect to ask for that route.
When a developer is quicker than doing it yourself
- You have been rejected twice for the same guideline.
- The 4.2 fix means adding native features and you do not have the skills to build them.
- The rejection involves payments, because moving to Apple's in-app purchase changes how money flows and how you report it.
- The app stores customer data and you are unsure what the privacy label should say.
- You are using the AI builder's credits to chase one rejection after another and the code is getting messier.
In those cases, a developer who has shipped apps before will usually be quicker than trial and error, because they know what each guideline looks for. The guides on hiring a Bolt developer and prototyping with AI and finishing with a developer explain how that works, and what makes a vibe coded app production ready lists the other gaps to check. If your app was already shaky before the rejection, see why AI-built apps break.
How I'd approach this
I would not resubmit the same build with a hopeful note. I would read the message, fix every cited guideline at once, and test on a real device. For a wrapped website I would decide first whether the product should be an app at all. If the real answer is "a website people use occasionally", I would skip the store and keep it a web app. If it truly needs to be an app, I would pick the two or three native features that serve a real user need and build those well, rather than many shallow ones.
If you want a second pair of eyes before you resubmit, a short review of the build against the guidelines is cheap compared with losing another week. Blur Studio's fixes and finishes start around $1,500, with the price agreed in writing first. I will tell you plainly if the quicker route is to cancel the app and ship the website.
Questions people ask
Are vibe coded apps allowed on the App Store?
Yes. Apple's guidelines judge the app's function, privacy handling and completeness, not the tool that wrote the code. Two rules matter for AI and template tools: 2.5.2 on downloading executable code, and 4.2.6 on apps made from a template or app-generation service. See what makes a vibe coded app production ready.
What does guideline 4.2 mean for my app?
It says an app should include features, content and design that go beyond a repackaged website. If your app is a website inside a wrapper with nothing that uses the phone, expect a rejection. Add real native features, or keep it as a web app.
How long does it take Apple to review a resubmission?
Apple says App Review typically reviews at least 50 percent of submissions in less than 24 hours and 90 percent in less than 48 hours. The time you control is how long it takes to fix every cited guideline, so fix them all before you resubmit.
Do I need Sign in with Apple?
Only if you use a third-party or social login, such as Google, to set up the main account. Guideline 4.8 then requires an equivalent option that limits data collection to name and email, lets users hide their email and does not track interactions for ads without consent. If you only use email and password, 4.8 does not apply.
Can I appeal if I think the reviewer got it wrong?
Yes. Apple lets you submit one appeal per rejected submission to the App Review Board, with specific reasons your app complies. Answer any requests for more information first. You can also book a 30-minute appointment with App Review.
Should I use Bolt, Lovable or Replit to build the iPhone version?
They can produce the web app quickly, but getting a store-ready phone app usually needs a developer for wrapping, native features, privacy settings and payments. Read hiring a Bolt developer and prototype with AI, finish with a developer to see what the handover looks like.
More in this topic: Problem solving: AI-built and no-code apps (26 guides) →