Repository navigation
|
My app was flagged or rejected on Google Play for this. Location requested without the Android location button scope. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Location Permissions policy for apps targeting API 37 (Play Console Help answer 16909972) (Google Play) Severity in the playbook. high What triggers it. 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. What to search your code for. How to fix it. 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. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Location Permissions policy for apps targeting API 37 (Play Console Help answer 16909972) (Google Play)
Severity in the playbook. high
What triggers it. 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.
What to search your code for.
ACCESS_FINE_LOCATION,ACCESS_COARSE_LOCATION,targetSdk 37How to fix it. Scope one-shot location use to the location button with the onlyForLocationButton flag and keep the broad permission only f…