Repository navigation
|
How can a team catch QUERY_ALL_PACKAGES without a permitted 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 'QUERY_ALL_PACKAGES' --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. QUERY_ALL_PACKAGES declared in AndroidManifest. The fix. Declare specific packages with a queries element, or qualify for a permitted use case. 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-QUERY-ALL-PACKAGESwith a coverage line and a proper exit code.What the hit means. QUERY_ALL_PACKAGES declared in AndroidManifest.
The fix. Declare specific packages with a queries element, or qualify for a permitted use case.
Recipe source. data/detection-recipes.json
This is a maintainer FAQ for app-store-compliance,…