Repository navigation
|
How can a team catch All files access without a qualifying use case 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 'MANAGE_EXTERNAL_STORAGE' --include='AndroidManifest.xml' .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. MANAGE_EXTERNAL_STORAGE declared in AndroidManifest. The fix. Use scoped storage. Request all files access only for a qualifying use case with the required declaration. 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
GOOGLE-PERM-ALL-FILESwith a coverage line and a proper exit code.What the hit means. MANAGE_EXTERNAL_STORAGE declared in AndroidManifest.
The fix. Use scoped storage. Request all files access only for a qualifying use case with the required declaration.
Recipe source. data/detection-recipes.json
This is a maintainer FA…