Repository navigation
|
How can a team catch Sensitive framework linked without a usage description automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. for k in NSCameraUsageDescription NSLocationWhenInUseUsageDescription NSPhotoLibraryUsageDescription NSContactsUsageDescription NSMicrophoneUsageDescription; do echo "$k"; plutil -extract "$k" raw */Info.plist 2>/dev/null || echo ' MISSING or empty'; doneRead 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. A sensitive framework or API is referenced in code but the matching NSxUsageDescription key is absent from Info.plist. The fix. Add the matching usage description key with a specific reason for every sensitive framework used. 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
APPLE-5.1.1-MISSING-USAGE-DESCRIPTIONwith a coverage line and a proper exit code.What the hit means. A sensitive framework or API is …