Repository navigation
|
How can a team catch Undisclosed over-the-air JS bundle updater automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'react-native-code-push\|CodePush\.\|expo-updates' --include='*.ts' --include='*.tsx' --include='*.js' . 2>/dev/nullRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. package.json depends on react-native or expo, and an OTA updater (react-native-code-push, expo-updates, react-native-ota-hot-update, Stallion) is present with no App Review disclosure of bug-fix-only scope. The fix. Name the OTA mechanism in App Review notes and restrict it to bug fixes that do not change purpose, UI, or features beyond what was reviewed (Apple 3.3.2, 2.5.2). An undisclosed update path that adds features after approval is the bait-and-switch Apple names under 2.5.19 since 16 October 2026. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
RN-OTA-UNDECLAREDwith a coverage line and a proper exit code.What the hit means. package.json depends on react-native or expo, and an OTA updater (react-native-code-push, expo-updates, react-native-ota-hot-update, Stallion) is present with no App Review disclosure…