Skip to content
Discussion options

You must be logged in to vote

Guideline. 2.5.19 (App Store)

Severity in the playbook. critical

What triggers it. The binary carries functionality App Review cannot see or that the user is not told about, such as a server flag that turns on a different app after approval, a secret gesture or menu, or code obfuscated to hide a feature. Guideline 2.5.19, added 16 October 2026, moves this policy out of 2.3.1 and names bait-and-switch (misrepresenting functionality during review, then adding features after approval). Checked by hand, a remote flag alone is not a violation.

How to fix it. Ship every feature visible to review, describe each one in Notes for Review, keep remote configuration to tuning and staged rollout of re…

Replies: 1 comment

Comment options

mjmirza
Nov 6, 2026
Maintainer Author

You must be logged in to vote
0 replies
Answer selected by mjmirza
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant