Repository navigation
|
How can a team catch READ_CONTACTS requested where the Contact Picker is sufficient automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rqn 'READ_CONTACTS' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' . && grep -rqE 'targetSdk(Version)?[[:space:]=]+3[7-9]' --include='*.gradle' --include='*.kts' . && ! grep -rqn 'ACTION_PICK\|ContactPicker' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. 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. The fix. 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. Recipe source. data/detection-recipes.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 |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
GOOGLE-CONTACTS-PICKER-REQUIREDwith …