The Rejection Reason (Guideline 2.3.1 - Hidden or Undocumented Features)
Every feature in your app must be visible, testable, and documented. If Apple discovers that you have hidden a feature (which activates, for example, via a remote server update after validation), your developer account risks suspension.
What is considered hidden
- Remote switches (Feature Flags): Activating an alternative payment system (e.g., Stripe) remotely once the app is validated (bypassing Apple's 30%).
- Major Easter Eggs: A hidden mini-game or an entire module not mentioned in the description.
- Invasive code updates: Downloading critical new JavaScript features via the web without going through App Store updates (while tools like Capacitor Updater or Ionic Appflow are tolerated for minor bug fixes, they must not change the app's purpose).
The Solution
- Be transparent: If you use a Feature Flags system (e.g., LaunchDarkly), ensure they are enabled for the Apple tester so they see the app in its entirety.
- Don't play with payments: Never try to hide a link to an external payment platform. Apple conducts regular audits of apps even after publication.