OTA or hot code push does not materially change app functionality

Apple's guideline 2.5.2 prohibits apps from downloading executable code after approval. Using OTA updates (Expo Updates, CodePush) combined with remote feature flags to silently enable entirely new functionality — gambling, payments, adult content, cryptocurrency — after passing review is treated as deception and results in account termination, not just app rejection. The line Apple draws is between bug fixes and UI changes (permitted) and new features that would require re-review (prohibited). The combination of OTA + remote config is the mechanism most commonly exploited to bypass review — reviewers know what to look for.

Configure Expo Updates to apply only on error recovery, and ensure no remote flag can enable a feature category that wasn't present and reviewed at submission time.

// app.json
"updates": {
  "enabled": true,
  "fallbackToCacheTimeout": 0,
  "checkAutomatically": "ON_ERROR_RECOVERY"
}

Audit every LaunchDarkly/Statsig/GrowthBook flag in the codebase. For any flag that controls a payment flow, adult content, gambling mechanic, or cryptocurrency feature — verify that feature was present and reviewable at the last App Store submission. Disable the flag permanently or submit a new app version before enabling it.