Apple requires that all app functionality be described in your app's metadata and visible during review. Features that only activate after a remote flag, a specific date, or a hidden gesture violate this even if they're legitimate.
Why apps actually get flagged
Most often triggered by a soft-launch pattern — shipping a build with a feature flag that's off during review and turned on later — or by not fully explaining a complex feature's behavior in the App Review notes.
A real example
"Your app includes hidden or undocumented features that are not accessible during the standard review process. Please ensure all features are described..."
The short version, in more detail
Guideline 2.3.1 requires that everything the app can do is visible and explained to App Review. Features that switch on later through a remote flag, a date, a hidden gesture or a special account break this rule even if they are legitimate. The rule exists so that the version reviewed matches the version users end up using.
What this guideline covers
Features activated after approval by remote configuration or date.
Hidden gestures, codes or accounts that unlock functionality.
Functionality not described in the review notes.
Any behaviour that differs between the reviewed and the live app.
What usually triggers this rejection
A soft-launch pattern where a feature flag is off during review and turned on afterward.
A feature that appears only in certain regions or on certain dates.
A complex feature that is not explained in the App Review notes.
Hidden screens reachable by a special action.
Switching the app's core behaviour remotely after approval.
How reviewers evaluate it
Reviewers rely on what they can see and on the notes provided.
They compare the described functionality with what is present.
Evidence of hidden behaviour found later can lead to removal.
Apple treats this as a trust issue, not only a technical one.
Common misunderstandings
Feature flags are not banned. The issue is changing behaviour in ways the review did not see.
Good intentions do not change how undisclosed functionality is treated.
Being unfinished is different from being hidden, but hidden code still counts.
Common questions
Can I use remote configuration at all?
Yes, for ordinary content and settings. The concern is activating substantially new functionality that was not reviewed.
Do I need to explain every feature in the notes?
Anything non-obvious or hard to reach should be explained.
What happens if hidden features are discovered later?
The app can be pulled and the account can be affected.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.