Repository navigation
|
How can a team catch Location requested without the Android location button scope 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 -rqn 'ACCESS_FINE_LOCATION\|ACCESS_COARSE_LOCATION' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' . && grep -rqE 'targetSdk(Version)?[[:space:]=]+3[7-9]' --include='*.gradle' --include='*.kts' . && ! grep -rqn 'onlyForLocationButton' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' .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. Apps targeting API 37 or later must implement the Android location button using the onlyForLocationButton permission flag in the manifest when location is only needed at a user-triggered moment. A blanket ACCESS_FINE_LOCATION request for a tap-to-locate feature is a policy violation from 27 January 2027. The fix. Scope one-shot location use to the location button with the onlyForLocationButton flag and keep the broad permission only for continuous features that justify it. 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-LOCA…