Repository navigation
|
How can a team catch Capacitor/Cordova plugin wrapping a native SDK 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 -rq '@capacitor/\|Capacitor\.' --include='*.ts' . 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. Capacitor/Cordova plugins are present and no PrivacyInfo.xcprivacy exists anywhere in the project. The fix. Capacitor plugin manifest support is less standardized than Flutter's. Verify each plugin wrapping a native SDK (camera, geolocation, ads) ships PrivacyInfo.xcprivacy, and add the app-level one. 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
IONIC-PRIVACY-MANIFEST-MISSINGwith a coverage line and a proper exit code.What the hit means. Capacitor/Cordova plugins are present and no PrivacyInfo.xcprivacy exists anywhere in the project.
The fix. Capacitor plugin manifest support is less standardized than Flutter…