Repository navigation
Contacts Permissions, Location Permissions, and Foreground Service policy changes for apps targeting Android 17, API level 37 (Play Console Help answers 16909972 and 16965181), Google Play (Global). Mandatory from 2027-01-27 #1228
mjmirza
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Law. Contacts Permissions, Location Permissions, and Foreground Service policy changes for apps targeting Android 17, API level 37 (Play Console Help answers 16909972 and 16965181)
Where. Google Play (Global)
What it requires. Apps targeting API 37 or later may request READ_CONTACTS only when the Android Contact Picker is insufficient for core functionality (declaration required), must implement the Android location button with the onlyForLocationButton manifest flag for location-button scope, and may no longer use a foreground service for geofencing (use the Geofence API). Pre-review checks flag contacts and location issues in Play Console from 27 October 2026.
Effective. 2026-10-27. Mandatory. 2027-01-27. Enforced. 2027-01-27. Priority. high.
The deadline checker flags this automatically when it falls within 90 days. Where it is covered in the playbook. docs/GOOGLE-PLAY.md 2026 policy rounds, references/rules/android.md
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 install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions