Repository navigation
|
How can a team catch Background location without a qualifying core feature 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 'ACCESS_BACKGROUND_LOCATION' --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. ACCESS_BACKGROUND_LOCATION declared in AndroidManifest with no clear core feature or prominent disclosure. The fix. Use foreground location where possible, or justify background use with a core feature and a prominent disclosure and the permission 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-BACKGROUND-LOCATIONwith a coverage line and a proper exit code.What the hit means. ACCESS_BACKGROUND_LOCATION declared in AndroidManifest with no clear core feature or prominent disclosure.
The fix. Use foreground location where possible, or justify background use with a core feature and a prominent discl…