Repository navigation
|
How can a team catch Generic or empty permission purpose string 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; do v=$(plutil -extract "$k" raw */Info.plist 2>/dev/null); echo "$k = $v"; done # flag empty or generic values like 'required'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. An NSxUsageDescription key in Info.plist is empty or carries a generic value such as needs access or required. The fix. Write a specific purpose string naming the real feature that uses each permission. 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-VAGUE-PURPOSE-STRINGwith a coverage line and a proper exit code.What the hit means. An NSxUsageDescription key in Info.p…