Repository navigation
|
My app was flagged or rejected on Google Play for this. READ_CONTACTS requested where the Contact Picker is sufficient. 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. Contacts Permissions policy for apps targeting Android 17, API level 37 (Play Console Help answer 16909972) (Google Play) Severity in the playbook. high What triggers it. Apps targeting API 37 or later may only request READ_CONTACTS when the Android Contact Picker is not sufficient for core functionality, and must complete the Play Console declaration. Enforcement 27 January 2027, pre-review checks from 27 October 2026. What to search your code for. How to fix it. Replace READ_CONTACTS with the Contact Picker for one-off selection. Keep the permission only for a genuine core use (a dialer, a contacts manager) and file the 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. Contacts Permissions policy for apps targeting Android 17, API level 37 (Play Console Help answer 16909972) (Google Play)
Severity in the playbook. high
What triggers it. Apps targeting API 37 or later may only request READ_CONTACTS when the Android Contact Picker is not sufficient for core functionality, and must complete the Play Console declaration. Enforcement 27 January 2027, pre-review checks from 27 October 2026.
What to search your code for.
READ_CONTACTS,targetSdk 37,targetSdkVersion 37How to fix it. Replace READ_CONTACTS with the Contact Picker for one-off selection. Keep the permission only for a genuine core use (a dialer, a contacts manager) and file the declara…