Repository navigation
feat(ios): declare the privacy manifest in app.json - #28
Merged
Merged
Conversation
Apple does not reliably read the PrivacyInfo.xcprivacy files inside static CocoaPods (Expo modules, React Native), so the app-level manifest has to repeat every required-reason API they declare. The prebuild default only had UserDefaults, SystemBootTime and FileTimestamp C617.1; it was missing DiskSpace (E174.1, 85F4.1, from expo-file-system) and FileTimestamp 0A2A.1 / 3B52.1. ios.privacyManifests now lists the union of all dependency manifests plus SystemBootTime 35F9.1 for the ClockSnapshot module, with no tracking and no collected data. tests/iosPrivacyManifest.test.ts re-reads the dependency manifests from node_modules, so an upgrade that adds a reason fails the test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Declares the iOS privacy manifest in
app.json(ios.privacyManifests), so every build produces a complete one.Why
Expo's privacy manifest guide says Apple does not reliably read the
PrivacyInfo.xcprivacyfiles inside static CocoaPods, such as Expo modules and React Native. The app-level manifest therefore has to repeat every required-reason API those pods declare. The manifest prebuild generated by default was missing:NSPrivacyAccessedAPICategoryDiskSpaceE174.1,85F4.1(expo-file-system)NSPrivacyAccessedAPICategoryFileTimestamp0A2A.1,3B52.1(expo-file-system)What it declares
The union of the 11 dependency manifests in
node_modules, plus SystemBootTime35F9.1for the ClockSnapshot module (kern.boottime,mach_continuous_time). It also declares no tracking and no collected data.How it was tested
tests/iosPrivacyManifest.test.tsre-reads every dependency manifest and fails ifapp.jsonis missing a reason. With85F4.1removed it fails on expo-file-system (checked).npx expo prebuild --platform ioswritesios/Birthmark/PrivacyInfo.xcprivacycontaining all four categories (checked withplutil).npm run typecheckandnpm run lintare clean.Not verified: Apple's own check. That runs only on an App Store Connect or TestFlight upload, which emails within minutes if anything is missing.
🤖 Generated with Claude Code