Repository navigation
|
I ship an app to users in Google Play (Global). Do I need to do anything for Contacts Permissions, Location Permissions, and Foreground Service policy changes for apps targeting Android 17, API level 37 (Play Console Help answers 16909972 and 16965181), and by when? |
Replies: 1 comment
|
It applies if your app reaches users in Google Play (Global) and falls in scope of the requirement below. 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. Mandatory from. 2027-01-27 Where to read more in the playbook. docs/GOOGLE-PLAY.md 2026 policy rounds, references/rules/android.md Run This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
It applies if your app reaches users in Google Play (Global) and falls in scope of the requirement below.
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.
Mandatory from. 2027-01-27
Where to read more in the playbook. docs/GOOGLE-PLAY.md 2026 policy rounds, references/rules/android.md
…