Skip to content
Discussion options

You must be logged in to vote

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 GOOGLE-PERM-BACKGROUND-LOCATION with 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…

Replies: 1 comment

Comment options

mjmirza
Nov 6, 2026
Maintainer Author

You must be logged in to vote
0 replies
Answer selected by mjmirza
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant