Repository navigation
|
My app was flagged or rejected on App Store (react-native) for this. React Native native module touches required-reason APIs with no PrivacyInfo.xcprivacy. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. 5.1.1 (App Store) Severity in the playbook. critical What triggers it. 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. What to search your code for. How to fix it. Add an app-level PrivacyInfo.xcprivacy. Native modules bundled transitively via JS deps each need their own manifest aggregated in the final IPA. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. 5.1.1 (App Store)
Severity in the playbook. critical
What triggers it. 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.
What to search your code for.
@react-native-firebase,AsyncStorage,expo-file-systemHow to fix it. Add an app-level PrivacyInfo.xcprivacy. Native modules bundled transitively via JS deps each need their own manifest aggregated in the final IPA.
The guard reports this as
RN-PRIVACY-MANIFEST-MISSING. The full pattern is in data/rejection-patterns.json.This is a maintainer FAQ for app-store-compliance, an open playbook and pre…