Feature Request / Policy Compliance
Google Play recently announced a new "Contacts Permissions" policy. Apps that do not require "broad access" to contacts must now use the Android Contact Picker to minimize data collection.
Problem
Current implementation of flutter_contacts relies heavily on READ_CONTACTS and WRITE_CONTACTS permissions. With the new policy, Google may reject apps that use these permissions if the primary goal is just selecting a specific contact.
Suggested Changes
- Lightweight Mode: Provide a way to use the native Contact Picker without requiring the
READ_CONTACTS permission in the Manifest.
- Documentation Update: Add a guide on how to comply with Google Play’s 30-day deadline using this package.
- Internal Picker: Ensure that
openExternalPick() can function as a standalone intent that doesn't trigger permission-related rejections during Google Play's automated review.
Are there any plans to provide a "Permission-less" picker implementation to align with these privacy updates?
....
Google Policy Announcement
Feature Request / Policy Compliance
Google Play recently announced a new "Contacts Permissions" policy. Apps that do not require "broad access" to contacts must now use the Android Contact Picker to minimize data collection.
Problem
Current implementation of
flutter_contactsrelies heavily onREAD_CONTACTSandWRITE_CONTACTSpermissions. With the new policy, Google may reject apps that use these permissions if the primary goal is just selecting a specific contact.Suggested Changes
READ_CONTACTSpermission in the Manifest.openExternalPick()can function as a standalone intent that doesn't trigger permission-related rejections during Google Play's automated review.Are there any plans to provide a "Permission-less" picker implementation to align with these privacy updates?
....
Google Policy Announcement