Repository navigation
|
My app was flagged or rejected on Google Play for this. Background location without a qualifying core feature. 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. Permissions and APIs (Google Play) Severity in the playbook. critical What triggers it. ACCESS_BACKGROUND_LOCATION declared in AndroidManifest with no clear core feature or prominent disclosure. What to search your code for. How to fix it. Use foreground location where possible, or justify background use with a core feature and a prominent disclosure and the permission declaration. 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. Permissions and APIs (Google Play)
Severity in the playbook. critical
What triggers it. ACCESS_BACKGROUND_LOCATION declared in AndroidManifest with no clear core feature or prominent disclosure.
What to search your code for.
ACCESS_BACKGROUND_LOCATIONHow to fix it. Use foreground location where possible, or justify background use with a core feature and a prominent disclosure and the permission declaration.
The guard reports this as
GOOGLE-PERM-BACKGROUND-LOCATION. The full pattern is in data/rejection-patterns.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
bash scripts/install.sh in…