Repository navigation
|
How can a team catch Entitlements declared but not used 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 e in $(find . -name '*.entitlements'); do echo "== $e"; plutil -p "$e"; done # then grep the codebase to confirm each capability is actually usedRead 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 entitlements file declares a capability the app does not use. Apple requests justification for any entitlement with no matching functionality, which blocks review. Temporary exception entitlements draw extra scrutiny. The fix. Remove any entitlement the app does not actively use. Cross check each entitlement against real code usage. Source. truongduy2611 unused_entitlements rule. 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-2.4.5-UNUSED-ENTITLEMENTSwith a coverage line and a proper exit code.What the hit means. An entitlements file declares a capability the app does not use. Apple requests justification for any entitlement with no matching functionalit…