Repository navigation
|
How can a team catch React Native native module touches required-reason APIs with no PrivacyInfo.xcprivacy 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 -qE '"react-native"|"expo"' package.json 2>/dev/null && grep -rn 'Firebase\|AsyncStorage\|expo-file-system' --include='*.ts' --include='*.tsx' . 2>/dev/null && ! find . -name 'PrivacyInfo.xcprivacy' | grep -q .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 What the hit means. package.json depends on react-native or expo, native modules with required-reason API usage are present (Firebase, AsyncStorage, expo-file-system), and no PrivacyInfo.xcprivacy exists. The fix. Add an app-level PrivacyInfo.xcprivacy. Native modules bundled transitively via JS deps each need their own manifest aggregated in the final IPA. 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-PRIVACY-MANIFEST-MISSINGwith a coverage line and a proper exit code.What the hit means. package.json depends on react-native or expo, native modules with required-reason A…