Repository navigation
|
How can a team catch Flutter plugin 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 -q 'permission_handler\|image_picker\|geolocator\|firebase_' pubspec.yaml 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. pubspec.yaml present, a plugin known to touch required-reason APIs (permission_handler, image_picker, geolocator, device_info_plus, package_info_plus, shared_preferences, sqflite, firebase_*) is a dependency, and no PrivacyInfo.xcprivacy exists anywhere in the project. The fix. Add an app-level PrivacyInfo.xcprivacy and confirm each Flutter plugin ships its own (Flutter 3.19+ plugins mostly do). A missing plugin-level manifest is invisible to Apple unless the app manifest also declares that plugin reason code. 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
FLUTTER-PRIVACY-MANIFEST-MISSINGwith a coverage line and a proper exit code.What the hit means. pubspec.yaml present, a plugin known to touch required-reason APIs (permission_handler, image_picker, geolocator, device_info_plus, package_info_plus…