In March 2026, Apple quietly blocked updates to popular vibe-coding platforms Replit and Vibecode, citing Guideline 2.5.2 — the rule barring apps from downloading, installing, or executing code that changes their features or functionality after Apple has reviewed them. Both platforms had to change how they worked to stay on the store: opening AI-generated apps in an external browser instead of an in-app web view, or dropping the ability to generate installable software for Apple devices at all.
The distinction Apple has drawn since is narrower, and more useful, than “AI apps get rejected.” AI-assisted coding tools built into Xcode — including OpenAI and Anthropic integrations professional developers use to write code that then goes through normal review — are explicitly fine. What isn’t fine is an app that ships as a shell for generating and running new code live, on-device, bypassing the review process entirely. As one detailed account of the policy put it: using AI to help professional developers write code is fine; shipping AI-generated apps that bypass review is not.
Why this is a build-decision issue, not just a compliance footnote
The apps most likely to hit this wall are exactly the ones an “AI app builder” pitch produces by design — a lightweight wrapper that lets end users generate and run their own mini-apps or scripts inside your app. If that’s anywhere near your product concept, Guideline 2.5.2 isn’t a theoretical risk, it’s a design constraint you need upfront, not something to discover at submission. Separately, Apple has flagged the quality bar directly: AI-generated code still needs review, refactoring and hardening by experienced developers before submission, with missing error handling, exposed API keys, weak input validation and inconsistent architecture cited as common, avoidable rejection triggers.
So what
If you’re commissioning a build on top of an AI app builder or considering AI-generated components as end-user-facing functionality, get the App Store review implications checked before the architecture is locked in — retrofitting around Guideline 2.5.2 after launch is expensive. If you want a build reviewed for exactly this kind of risk, see our iOS & Android development work or get in touch before you submit.