Apple blocked updates for Replit and Vibecode, invoking App Store rule 2.5.2 that bans apps from downloading or executing code that changes their functionality. The move halted the latest versions of two AI‑powered coding assistants that let users generate websites and iOS apps from natural‑language prompts. Developers received notices that the updates violated the self‑contained requirement of the App Store.
Driving the news: Apple required Replit to open generated projects in an external browser instead of an embedded WebView, and forced Vibecode to remove the ability to create iOS‑targeted software entirely. Both decisions arrived through messages from App Review teams, citing platform‑security standards.
Why it matters: Developers reported that their prototype pipelines stopped, delaying product launches and increasing engineering costs. Startups that relied on rapid AI‑assisted iteration now must redesign workflows or shift to desktop environments. The enforcement shows how platform rules can reshape entire development categories overnight.
What they're saying: Apple's App Review team cited user security and platform integrity as the rationale, referencing the official guideline that "apps must remain self‑contained." The guideline is published on the Apple Developer site. The Information first reported the block and quoted Apple's statement about protecting against malicious code execution.
By the numbers: Apple blocked updates for two major AI coding apps—Replit and Vibecode—affecting developers who rely on these platforms for rapid prototyping and app generation.
Between the lines: Vibe coding, which generates functional code from conversational prompts, lets users describe an app feature and receive ready‑to‑run source files. The restriction forces tools to abandon the "write once, run anywhere" model that bypasses Xcode and the traditional App Store distribution model, where developers submit apps as compiled binaries that run without fetching new code. This architectural change affects how AI coding tools approach mobile development and reflects Apple's concern about maintaining control over its platform ecosystem.
What's next: Developers building AI‑assisted code generators must embed all execution logic locally or provide external web portals for code preview. Apple is expected to publish clearer technical criteria for what triggers a 2.5.2 violation. Other AI coding platforms are already re‑architecting their apps to stay compliant, shifting toward static‑generation models or web‑based alternatives that keep code execution outside the iOS sandbox. Developers should monitor Apple's Developer documentation for updated guidelines and watch for precedent-setting reviews of similar AI‑assisted development tools.



















