Repository navigation
|
How can a team catch Sensitive runtime permissions requested without validation 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 -rn 'requestPermissions\|checkSelfPermission\|shouldShowRequestPermissionRationale' --include='*.kt' --include='*.java' . && ! grep -rn 'permission explanation\|showPermissionRationale\|explainPermission' .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. Requesting critical permissions (camera, contacts, storage) without dynamic checks or explicit explanation/rationale to the user. The fix. Check permissions dynamically at runtime, show a clear rationale if denied, and handle denials gracefully. 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
ANDROID-RUNTIME-PERMISSIONSwith a coverage line and a proper exit code.What the hit means. Requesting critical permissions (camera, contacts, storage) without dynamic checks or e…