Apple updated its App Review Guidelines on 16 October 2026, and the change most developers should care about is a new rule, 2.5.19: no hidden, dormant or undocumented features. Apple calls it a clarification of long-standing policy, but it now has its own number and spells out the penalty, which is removal from the App Store and termination of your developer account. If your app uses feature flags, remote config or staged rollouts, it is worth half an hour to check how you describe them to App Review. Here is what changed and a practical way to stay on the right side of it.
Everything that changed on 16 October
Apple's developer news post lists these updates:
1.2 (User-generated content): clarified which apps and content types are covered, and that failing to put safeguards in place, or to fix violations after notice, can be treated as a Developer Code of Conduct violation. 9to5Mac reports the section now names nonconsensual intimate imagery among the challenges these apps must handle.
2.3.14 (new): rules for creative assets, the new marketing images that can appear in the product page header and search results.
2.5.19 (new): hidden, dormant or undocumented features, previously covered under 2.3.1.
3.1.1(a): the separate bullet on Music Streaming Services Entitlements was folded into the StoreKit External Purchase Link Entitlements bullet, with a clarification that links may point to a permitted destination.
5: apps that facilitate human trafficking or child exploitation will be removed and blocked from alternative distribution.
Apple also added documentation links to the "Before You Submit" and "After You Submit" sections. Translations follow within a month.
What 2.5.19 actually says
The full text, from the App Review Guidelines:
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.
Read it next to 2.3.1(a), which still requires that "all new features, functionality, and product changes must be described with specificity in the Notes for Review section of App Store Connect", and warns that generic descriptions will be rejected.
The target is clear from the coverage: "bait-and-switch" apps that pass review as one thing and later switch on something else, such as the AI nudification apps 9to5Mac describes. Most legitimate teams are nowhere near that. The grey area is ordinary engineering practice.
Where honest apps can trip: feature flags
Plenty of well-run apps ship code for a feature that is switched off, then turn it on from a server once it is ready. That is a sensible way to decouple deploys from releases. The guideline doesn't mention remote config by name, and Apple hasn't published a separate FAQ on it, so I'd read it conservatively:
Dormant code that a reviewer can't see or test is exactly what the words "hidden" and "dormant" describe.
The same code, described in the review notes and accessible to the reviewer, is a documented feature with a staged rollout.
The difference is disclosure, not architecture.
A practical checklist before your next submission
1. Inventory every flag in the binary
If your flags are scattered string literals, centralise them. A single registry makes the review note easy to write and keeps the list honest:
// FeatureFlags.swift
enum Feature: String, CaseIterable {
case newCheckout = "new_checkout" // staged rollout, 10% of users
case voiceNotes = "voice_notes" // built, not yet enabled
case darkIcons = "dark_icons" // A/B test
}
Feature.allCases then gives you the full list for your release checklist.
2. Describe them in Notes for Review
Specific beats generic. Something like:
This build contains three features controlled by server flags. new_checkout: redesigned checkout, rolling out to 10% of users. voice_notes: voice messages in chat, built but switched off, planned for December. dark_icons: alternate icon set, running as an A/B test. All three are switched on for the demo account above, so you can test them.
3. Make the features reachable for the reviewer
Switch the flags on for the demo account you provide. A documented feature the reviewer can't reach is only half documented.
4. Drop obfuscation that hides behaviour
2.5.19 names code obfuscation explicitly. Standard release optimisation is one thing; deliberately disguising what code does is what the rule targets.
5. If you host user-generated content, check 1.2
Apps with posting, uploading or AI generation should confirm their reporting, blocking and moderation tools are in place now, because failing to fix issues after notice is now framed as a conduct violation.
The creative assets rule, briefly
If your marketing team is excited about the new product page header assets, 2.3.14 says they must relate to your app's content, functionality or brand, follow standard metadata rules and be appropriate for all audiences. They can't include references to other apps meant to mislead, unverifiable product claims, or specific or discounted pricing. So "Now 50% off" in a header image is out.
How this fits the rest of your year-end checklist
This lands on top of a busy season for mobile teams. If you are still working through platform changes, our roundup of iOS 27 and Android 17 deadlines has the dates in one place, and React Native teams should check the SceneDelegate changes in React Native 0.88 before the next iOS submission. On the Android side, the developer verification requirement follows the same idea from a different angle: platforms want to know who ships an app and what it does.
The short version: if a reviewer can see it and your notes describe it, a feature flag is fine. If it is switched off, undescribed and waiting for after approval, 2.5.19 now gives Apple a numbered rule to remove the app over.



