After a user declines the contacts permission, there is no in-app affordance to turn recipient autocomplete on later — it is silently off forever, and on Android a permanently-denied permission can only be re-granted via system Settings.
Proposal
Add a Settings entry (e.g. under a Compose/Contacts section) to enable contact autocomplete. When the permission is grantable, request it in-app; when it is permanently denied, deep-link the user to the app's system permission settings with a brief explanation. Reflect the current state (on / off / blocked-in-settings).
Notes
Independent of where the initial request happens (compose today, onboarding after the move ticket).
Keep it optional and clearly labeled as on-device-only autocomplete.
Related: the move-to-onboarding and rationale tickets.
After a user declines the contacts permission, there is **no in-app affordance to turn recipient autocomplete on later** — it is silently off forever, and on Android a permanently-denied permission can only be re-granted via system Settings.
## Proposal
Add a Settings entry (e.g. under a Compose/Contacts section) to enable contact autocomplete. When the permission is grantable, request it in-app; when it is permanently denied, deep-link the user to the app's system permission settings with a brief explanation. Reflect the current state (on / off / blocked-in-settings).
## Notes
- Independent of where the initial request happens (compose today, onboarding after the move ticket).
- Keep it optional and clearly labeled as on-device-only autocomplete.
Related: the move-to-onboarding and rationale tickets.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After a user declines the contacts permission, there is no in-app affordance to turn recipient autocomplete on later — it is silently off forever, and on Android a permanently-denied permission can only be re-granted via system Settings.
Proposal
Add a Settings entry (e.g. under a Compose/Contacts section) to enable contact autocomplete. When the permission is grantable, request it in-app; when it is permanently denied, deep-link the user to the app's system permission settings with a brief explanation. Reflect the current state (on / off / blocked-in-settings).
Notes
Related: the move-to-onboarding and rationale tickets.