Apple Is Blocking Updates to Vibe Coding Apps on the App Store

Apple has been blocking App Store updates for at least two vibe coding apps since January 2026. The Information broke the story today, and it was quickly picked up by 9to5Mac, MacRumors, and The Decoder.

The two apps affected are Replit and Vibecode. Both remain available on the App Store, but Apple has refused to approve any new updates for roughly two months. Apple conducted three phone calls with the developers during that period, spelling out what they’d need to change to get back in good standing.

The short version: Apple says these apps violate existing rules about executing dynamic code. The longer version is more complicated and, frankly, more interesting.

What Apple Is Actually Objecting To

Apple’s primary concern centers on App Store Review Guideline 2.5.2, which states that apps “may not download, install, or execute code which introduces or changes features or functionality of the app.” There’s a narrow exception for educational coding apps where the source code is “completely viewable and editable by the user.”

The second provision in play is Section 3.3.1(B) of the Developer Program License Agreement, which allows interpreted code downloads only if the code doesn’t “change the primary purpose of the Application.”

The argument from Apple’s side is straightforward: vibe coding apps let users generate and execute arbitrary code inside the app. That code can fundamentally change what the app does after it passes review. Today it’s a coding tool, tomorrow the user has generated a fully functional shopping app running inside a web view. Apple’s review process is built on the assumption that what gets reviewed is what users get. These tools break that assumption.

An Apple spokesperson told MacRumors that Apple doesn’t have any rules specifically against “vibe coding” and that the App Review Guidelines are “designed to encourage innovation while preserving safety for users.” The company frames this as enforcement of existing policy, not a new crackdown.

The Specific Compromises Being Demanded

According to reporting from The Information and 9to5Mac, each app faces different requirements to get updates approved again.

Replit must open generated app previews in an external browser instead of displaying them in an in-app web view. Replit had argued that its generated code runs in a separate virtual machine and displays via a web view, similar to how social media apps open links. Apple’s review team rejected that comparison. Developers close to the situation describe the external browser requirement as “burdensome,” since it forces users to constantly switch between the browser and the app.

Replit, which just raised $400 million at a $9 billion valuation on March 11, has seen its App Store ranking drop from first to third place in free developer tools since the freeze began in January.

Vibecode faces a harsher requirement: remove the ability to generate software specifically for Apple devices. That guts one of the app’s core use cases.

Both apps were reportedly close to reaching agreements with Apple as of today.

Who Else Is (and Isn’t) Affected

This crackdown is narrower than the initial headlines suggest.

v0 (by Vercel) has continued publishing App Store updates without issues. The likely reason is that v0’s architecture already handles code previews in a way that satisfies Apple’s requirements, possibly rendering output through external browser views rather than in-app execution.

Rork operates on a completely different model. Rork generates native React Native/Expo apps from text prompts. Users then submit those generated apps through their own Apple Developer accounts via TestFlight and App Store Connect. Rork itself isn’t an in-app code execution environment in the way Replit is, so Guideline 2.5.2 doesn’t apply to it directly. That said, the individual apps Rork generates can still face rejections under other guidelines, particularly 4.2 (Minimum Functionality) if they’re too thin, or 4.3 (Spam) if they’re derivative.

Bolt and Lovable are web-based platforms. They don’t distribute through the App Store, so this particular enforcement doesn’t touch them. Apps built with those tools, however, can still face standard App Store rejections on their own merits.

The Hypocrisy Problem

Here’s where Apple’s position gets awkward.

In February 2026, Apple released Xcode 26.3 with full agentic coding support. The update added integration with OpenAI’s Codex and Anthropic’s Claude Agent, along with support for the Model Context Protocol (MCP) standard. Apple had already added ChatGPT integration to Xcode at WWDC 2025 in June.

So Apple is actively building AI coding tools into its own development environment while restricting third-party apps that offer similar capabilities to a broader audience.

Gene Burrus, Global Policy Counsel at the Coalition for App Fairness, told The Information that Apple “has a history of blocking apps or features that create competition on its platform.” The Coalition for App Fairness counts companies like Spotify and Epic Games among its members and has been critical of Apple’s App Store practices for years.

The competitive dynamics are real. Vibe coding tools don’t just compete with Xcode. They also enable the creation of progressive web apps that bypass the App Store entirely, threatening Apple’s commission revenue. When developer Stu Maschwitz had his vibe-coded BAC calculator app rejected under Guideline 1.4 (Physical Harm), despite identical apps already existing on the store, he rebuilt it as a progressive web app using Lovable and skipped Apple’s review process altogether. That outcome is exactly what Apple should want to avoid if it cares about keeping developers in its ecosystem.

The Bigger Picture: Apple’s Spam Problem Is Real

It would be dishonest to frame this purely as anticompetitive behavior. Apple does have a legitimate problem.

In 2024, Apple reviewed 7.77 million app submissions and rejected 1.93 million of them. Over 320,000 of those rejections were for being copies, spam, or misleading. Apple’s review team handles roughly 150,000 submissions per week. The flood of AI-generated apps is making those numbers worse, not better.

Vibe coding tools make it trivially easy for someone with no technical background to generate a functional app and submit it to the App Store. Most of these won’t be high-quality. Many will be clones or slight variations of existing apps. Some will be outright scams wrapped in AI-generated polish. Apple’s review team is the last line of defense, and that team is already overwhelmed.

The question is whether blocking platform-level tools is the right way to address app-level quality problems. Banning Replit from updating because some of its users might submit junk apps is like banning Photoshop because some of its users make bad advertisements. The tool isn’t the problem. The output is.

What Happens Next

Apple appears to be reaching individual agreements with each affected app rather than publishing new blanket guidelines. That approach gives Apple maximum flexibility but creates uncertainty for every other vibe coding tool considering an iOS app.

Adalo published a guide aimed at helping developers get vibe-coded apps through App Store review, focusing on meeting minimum functionality requirements and avoiding common rejection triggers. The fact that such guides are already circulating tells you how widespread the concern has become.

For now, the standoff has practical implications for the vibe coding ecosystem:

• If you use Replit on iOS, you’re stuck on a January build until Apple approves the next update. The desktop and web versions are unaffected.
• If you use Rork, Bolt, or Lovable to build apps, Apple isn’t targeting these platforms directly, but the individual apps you submit still need to clear standard review guidelines. Low-effort apps will get rejected regardless of what tool built them.
• If you’re building a vibe coding tool and considering an iOS app, Apple’s current position is that in-app code execution and preview rendering need to happen in an external browser, not in-app web views. Design your architecture around that constraint from the start.

The November 2025 App Review Guidelines update added nine changes, including anti-copycat rules and AI data-sharing disclosure requirements. None of those changes specifically mentioned vibe coding. The next round of guideline updates will be worth watching closely.

Apple is trying to maintain control over what runs on its platform while the tools for creating software are being democratized at an accelerating rate. Those two forces are going to keep colliding. The Replit and Vibecode cases are the first skirmishes, not the last.