Clarify Contact complication requires Full Access to contacts#41
Merged
Conversation
The contacts permission prompt on iOS 18 and later (including iOS 26) is a two-step prompt that lets the user choose between Full Access and Limited Access (Select Contacts). LoopFollow needs Full Access so it can create and maintain its own LoopFollow - BG contact, so the setup instructions now spell this out explicitly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The watch Contact complication setup just told users to tap "Allow." The contacts prompt now lets users pick Full Access or Limited Access ("Select Contacts…").
LoopFollow needs Full Access to create and keep its LoopFollow – BG contact updated; Limited Access breaks the complication. The setup steps now say this and warn against choosing Limited Access.