Apple's new rule 2.5.19: can a feature flag get your app banned?
Short answer: On October 16, 2026, Apple updated its App Review Guidelines. The headline for app founders is a new rule, 2.5.19: you can't show App Review one app and then switch on different features after approval. Apple calls it a clarification of a "long-standing" policy on hidden, dormant, or undocumented features (it used to live in 2.3.1). The penalty is the scary part: removal from the App Store and from the Apple Developer Program. (Source: Apple Developer News, Oct 16, 2026)
The 30-second version
On October 16, 2026, Apple updated its App Review Guidelines. The headline for app founders is a new rule, 2.5.19: you can't show App Review one app and then switch on different features after approval. Apple calls it a clarification of a "long-standing" policy on hidden, dormant, or undocumented features (it used to live in 2.3.1). The penalty is the scary part: removal from the App Store and from the Apple Developer Program. (Source: Apple Developer News, Oct 16, 2026)
Apple's own words: the rule "clarifies our longstanding prohibition on 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." (Apple, Oct 16, 2026)
What it means for you, founder by founder
What changes: nothing new on paper. In our reading, changing a price or a paywall layout from your server is not the "new functionality" Apple describes. The rule targets apps that hide what they really do.
Should you worry? only if the paywall you test unlocks features the reviewer never saw.
What I'd do: make sure every paywall variant and everything it unlocks exists in the build you submit.
What changes: a feature that is in the binary but switched off during review is exactly what "dormant" means. Gradual rollouts are normal engineering; surprising the reviewer is not.
Should you worry? yes, if a whole new feature goes live later without an app update.
What I'd do: turn flagged features ON for review, or describe them in the review notes with how to reach them.
What changes: guideline 1.2 now explicitly covers nonconsensual intimate imagery, including AI-generated, as content you must proactively prevent and remove.
Should you worry? if users can upload or generate images, yes. "We didn't know" is not a defense after notice.
What I'd do: filter, add report and block buttons, and document your moderation before Apple asks.
What changes: Apple has not said server-driven UI is banned. What it bans is changing what the app does after review.
Should you worry? if your backend can turn the app into a different product, a reviewer may see it that way.
What I'd do: keep the core purpose identical to what was reviewed, and ship new purposes as reviewed updates.
What founders are actually saying
That last line is the real lesson. Platform risk isn't only about rules. It's about owning nothing outside the store: no email list, no way to reach your users if the app disappears tomorrow.
Your 5-minute checklist
- List every feature flag and remote-config switch that changes what users can DO, not just how things look.
- Make sure each of those features is in the build you submit, and reachable by the reviewer.
- Write review notes that explain flags, test accounts and how to reach gated features.
- If users can upload or generate content: filter, report, block, and keep a record of how you handle reports.
- Start collecting emails or another direct channel to your users, so one removal can't erase your business.
FAQ
What is App Store guideline 2.5.19?
A rule added on October 16, 2026 that clarifies Apple's long-standing ban on hidden, dormant or undocumented features: apps can't misrepresent what they do during review and then change after approval.
Are feature flags banned on the App Store?
Apple hasn't said so. The risk is using flags to switch on functionality the reviewer never saw. Keep flagged features visible to review or explain them in the review notes.
Can I A/B test my paywall?
Changing prices and layouts is normal. Make sure every variant, and anything it unlocks, is in the submitted build.
What happens if Apple finds a bait-and-switch app?
Apple says such apps are subject to removal from the App Store and removal from the Apple Developer Program.
How many developer accounts does Apple terminate?
Apple says it terminated over 193,000 developer accounts and removed over 150,000 apps with safety issues last year.
Written by Idan Waller, co-founder of BlueThrone. We buy and grow mobile apps, so we read every policy change from the founder's side of the table.
Keep reading
.webp)
Time for
your exit?
