Apple's New App Store Rule 2.5.19 Bans Bait-and-Switch Apps: What Changed on Oct 16, 2026
TL;DR: On October 16, 2026, Apple added new App Review Guideline 2.5.19, formally banning apps that hide, disable, or undocument features during review and then activate them after approval. The rule — confirmed by Apple's own developer newsroom and corroborated by independent outlets including AppleInsider and ppc.land — targets "nudification" and other harmful capabilities concealed from reviewers, but it applies to any app that behaves differently after launch than it did in the submitted build. Violators face app removal and termination from the Apple Developer Program.
Apple's App Review team published the update on October 16, 2026, under the heading "Strengthening App Review Guidelines against nonconsensual intimate imagery and bait-and-switch apps." The announcement pairs a new content-moderation requirement in Section 1.2 covering AI-generated nonconsensual intimate imagery with a new Section 2.5.19 aimed squarely at apps that misrepresent their functionality to pass review. If your roadmap includes an iOS or cross-platform release this quarter, it's worth having a mobile development team review your build pipeline against the new language before you submit — the guideline is retroactive in spirit, not just forward-looking.
Here's exactly what changed, why Apple made the move now, and what app teams need to check before their next submission.
What Guideline 2.5.19 Actually Says
The new guideline reads, in Apple's own words: "Don't include any hidden, dormant, or undocumented features in your app; your app's functionality should be clear to end users and App Review. Attempting to hide undocumented features in your app binary, such as through code obfuscation or other methods, is grounds for removal of your app from the App Store and termination of your developer account."
Apple's announcement frames this as a clarification of a longstanding policy that previously lived under the broader Guideline 2.3.1, rather than an entirely new restriction. What's new is the explicit, standalone citation — which means App Review can now flag and reject a submission under 2.5.19 by name, instead of folding it into a vaguer "misleading app description" rejection.
The "Bait-and-Switch" Pattern Apple Is Targeting
Apple's own language describes the violation plainly: apps "misrepresenting what they do during the App Review process and then changing after approval — for example, adding features or functionality that weren't included in the version of the app that was submitted to App Review." The company specifically calls out apps that "misrepresent their purpose during review and only reveal harmful capabilities — such as 'nudification' — after approval," tying the rule to a wave of AI image-manipulation apps that reviewers had been catching inconsistently.
Why This Update Landed Now
The timing is not incidental. Apple's announcement bundles 2.5.19 with a tightened Section 1.2 that explicitly covers AI-generated nonconsensual intimate imagery, requiring apps to "proactively prevent and remove" such content or risk violating the Developer Code of Conduct. Independent coverage from AppleInsider and other outlets framed the update primarily as a response to so-called "nudify" apps that passed review with innocuous functionality, then flipped on harmful features via a server-side toggle or a disguised in-app purchase — a pattern code obfuscation and feature flags made easy to hide from reviewers.
Apple also published fresh enforcement numbers alongside the policy change: the company says it "prevented over 150K apps with safety issues from reaching customers and terminated over 193K developer accounts for engaging in fraud and abuse" in the preceding year — context meant to show the scale of the problem the new guideline is meant to close.
It's Not Just About Nudify Apps
The guideline's wording is broad enough to cover any app using feature flags, remote config, or A/B-testing infrastructure to activate functionality that wasn't present — or wasn't disclosed — in the build Apple reviewed. That is common, legitimate practice across mobile product teams: a feature ships dark, gets enabled for a cohort post-launch, and rolls out wider over following weeks. Apple's new language doesn't ban progressive rollouts outright, but it does mean that functionality materially different from what reviewers saw needs to be documented in your App Review notes, not just staged silently behind a flag.
What App Teams Should Check Before Their Next Submission
| Area | Risk Under 2.5.19 | What to Do |
|---|---|---|
| Feature flags / remote config | Server-toggled features reviewers never saw are grounds for rejection or removal | Disclose staged rollouts explicitly in App Review notes |
| Code obfuscation | Explicitly called out as a violation, not just a gray area | Avoid obfuscating logic that changes app behavior post-approval |
| In-app purchases unlocking new functionality | Can read as "hidden" capability if not described at submission | Document any purchase-gated feature in your review notes |
| AI-generated content features | Direct scrutiny under the paired Section 1.2 update | Confirm moderation and takedown workflows for AI-generated imagery |
None of this is exotic engineering — it's App Review documentation discipline, and it's exactly the kind of process gap that shows up when a team is moving fast without someone dedicated to App Store compliance. Teams working with an experienced iOS development partner that tracks Apple's guideline changes as a matter of course tend to catch this kind of shift before it becomes a rejected build.
Frequently Asked Questions
When did Apple's Guideline 2.5.19 take effect?
Apple published the update on October 16, 2026, as part of a broader App Review Guidelines revision addressing nonconsensual intimate imagery and bait-and-switch apps.
Does Guideline 2.5.19 ban feature flags and staged rollouts?
Not outright. It bans hiding or undocumenting functionality from App Review that then activates after approval. Progressive rollouts are still viable if the functionality and its staged activation are disclosed to reviewers.
What happens if an app violates Guideline 2.5.19?
Apple states violations are grounds for app removal from the App Store and termination of the developer's account — the same penalty structure as other serious Developer Code of Conduct violations.
Was this guideline entirely new, or does it replace an older rule?
Apple describes it as a clarification of policy previously covered under the broader Guideline 2.3.1, now given its own explicit citation so App Review can reference it directly.
Does this only affect apps with AI image-generation features?
No. While the announcement was driven in large part by AI "nudify" apps, the guideline's language applies to any app whose behavior changes materially after approval without having been disclosed during review.
