DEV Community

Cover image for Google Play contacts permission policy: 5 fixes by Jan 27
ExtensionBooster
ExtensionBooster

Posted on Originally published at appranker.net

Google Play contacts permission policy: 5 fixes by Jan 27

Originally published on AppRanker.

The Google Play contacts permission policy turns READ_CONTACTS from a default into an exception once your app targets Android 17 (API 37). If your invite screen, referral flow or "share with a friend" button still reads the whole address book, you have until January 27, 2027 to move it to the system Contact Picker, and the same update changes how you ask for precise location. Here is what changes, which apps can keep the permission, and a five-step migration you can run this sprint.

What actually changed

Google announced the policy on April 15, 2026. For apps targeting API 37 or higher, the rule is simple: request READ_CONTACTS only when the Contact Picker (or an alternative such as the Sharesheet) cannot cover your core feature.

That rules out the most common reasons apps ask today:

  • invites and referrals
  • sharing a file or link with a contact
  • choosing one contact to send money or a message to
  • your own custom picker UI built on top of full contacts access

Private and enterprise device-management apps are exempt. Everyone else who keeps the permission needs a declaration in Play Console, and categories that can still qualify include contact managers, dialer and SMS apps, call history and call screening, CRMs, accessibility tools, personal assistants, friend matching, backup and restore, and auto-complete keyboards.

Location gets a parallel rule. On Android 17+, one-time precise location (nearby search, a single location share, tagging a post, filling in an address) should go through the new location button, which grants precise location for one session only. A persistent ACCESS_FINE_LOCATION grant is reserved for apps where location is the core feature, such as navigation or fitness tracking, and never for ads or analytics alone. For many features, coarse location is enough.

The timeline

Date What happens
Apr 15, 2026 Policy announced
Sep 2026 Play Console asks apps with READ_CONTACTS to declare or remove it
Oct 2026 Play policy insights in Android Studio flag affected apps
Oct 27, 2026 Pre-review checks start flagging issues
Nov 2026 Precise location declaration opens
Jan 27, 2027 Compliance required (30-day self-extension available in Play Console)

Pre-review checks are already running, so an app that still requests contacts access without a declaration can be flagged on its next upload, well before the January date.

Five steps to migrate

1. Audit the merged release manifest. Libraries add permissions you never typed. Build the release manifest and count what ends up in it:

./gradlew :app:processReleaseManifest
grep -rhoE 'android.permission.(READ_CONTACTS|WRITE_CONTACTS|ACCESS_FINE_LOCATION|ACCESS_COARSE_LOCATION)' \
  app/build/intermediates/merged_manifests/release/ | sort | uniq -c
Enter fullscreen mode Exit fullscreen mode

The output folder differs between Android Gradle Plugin versions; if the path is empty, search app/build/intermediates for AndroidManifest.xml. For each hit, write down which feature uses it and whether that use is one-time or ongoing.

2. Swap contacts access for the Contact Picker. On Android 17 the system picker is launched with ACTION_PICK_CONTACTS. Useful extras include EXTRA_USE_SYSTEM_CONTACTS_PICKER, Intent.EXTRA_ALLOW_MULTIPLE, EXTRA_PICK_CONTACTS_SELECTION_LIMIT and EXTRA_PICK_CONTACTS_REQUESTED_DATA_FIELDS (for example Phone.CONTENT_ITEM_TYPE or Email.CONTENT_ITEM_TYPE). You read only the rows the user picked through ContentResolver. The picker is not backported, so older devices keep the classic single-contact ACTION_PICK flow. For pure sharing, the Sharesheet needs no permission at all.

3. Use the location button for one-time precise location. Declare fine location as button-only:

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission
    android:name="android.permission.ACCESS_FINE_LOCATION"
    android:usesPermissionFlags="onlyForLocationButton" />
<uses-permission android:name="android.permission.USE_LOCATION_BUTTON" />
Enter fullscreen mode Exit fullscreen mode

In Compose, the experimental androidx.core:core-locationbutton library (1.0.0-alpha01) provides a LocationButton composable with an onPermissionResult callback and a textType such as LocationButtonTextType.NearMyPreciseLocation. Keep a manual fallback, like a city field, for users who decline.

4. Clean up cross-platform plugins. React Native, Flutter and Capacitor plugins often request contacts access for you (react-native-contacts is a common example). Update or replace them, then strip anything you no longer need with a manifest merge rule:

<manifest xmlns:tools="http://schemas.android.com/tools">
    <uses-permission
        android:name="android.permission.READ_CONTACTS"
        tools:node="remove" />
</manifest>
Enter fullscreen mode Exit fullscreen mode

Test the release build afterwards: any leftover code path that still queries contacts will throw a SecurityException at runtime.

5. Declare or remove. If a permission truly stays, file the Play Console declaration and make sure it matches your store listing and Data safety form. If it goes, ship a release without it before you dismiss the Play Console prompt.

A quick pre-release checklist

  • [ ] Merged manifest audited for contacts and location permissions
  • [ ] Invite, referral and share flows moved to the Contact Picker or Sharesheet
  • [ ] ACTION_PICK fallback tested on pre-Android 17 devices
  • [ ] One-time precise location moved to the location button, with a manual fallback
  • [ ] Coarse location used wherever precision is not needed
  • [ ] Plugins updated and unused permissions removed
  • [ ] Release build tested on Android 17 and older versions
  • [ ] Declarations filed for anything you keep
  • [ ] Pre-review results checked after each upload

Key takeaways

  • Targeting API 37 makes READ_CONTACTS an exception that needs a declaration; invites, referrals and sharing do not qualify.
  • The Contact Picker covers most cases, but it is Android 17 only, so keep ACTION_PICK for older devices.
  • One-time precise location moves to the location button with the onlyForLocationButton flag.
  • Audit the merged manifest, because third-party plugins are where forgotten permissions hide.
  • Compliance is required by January 27, 2027, and pre-review checks are already flagging apps.

The original post has the full use-case table, a Kotlin picker sample and an FAQ in its guide to the Google Play contacts permission policy and the Android 17 location button. Once the fix ships, you can also list your Android app on AppRanker's app leaderboard to get it in front of more users.

Has your app's invite or referral flow already been flagged by Play's pre-review checks, and did the Contact Picker cover everything you needed, or did you have to file a declaration?

Top comments (0)