Repository navigation
|
We ship to users in Google Play (Global). What does Contacts Permissions, Location Permissions, and Foreground Service policy changes for apps targeting Android 17, API level 37 (Play Console Help answers 16909972 and 16965181) actually require from a mobile app, and by when? |
Replies: 1 comment
|
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. Dates. In force 2026-10-27, mandatory 2027-01-27, enforced 2027-01-27. Where to start. docs/GOOGLE-PLAY.md 2026 policy rounds, references/rules/android.md in the playbook explains the app-side work. The guard's deadline checker warns when this falls inside 90 days. Source data. data/regulatory-deadlines.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 |
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.
Dates. In force 2026-10-27, mandatory 2027-01-27, enforced 2027-01-27.
Where to start. docs/GOOGLE-PLAY.md 2026 policy rounds, references/rules/android.md in the playbook explains the app-side work.
The guard's deadline checker warns w…