Fix #1912 - if coarse is provided instead of fine location, returned … #1937
Conversation
This file contains 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
…restricted, not denied
|
|
5 tasks
jfversluis
approved these changes
Jan 14, 2022
|
Thanks for your patience @aritchie and even more thanks for your time and effort on this! |
|
Anytime. Glad I could help |
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Change
Android 11/12 allow for coarse location permission to be returned without precise/fine. Essentials should return "Restricted" in this case, not denied. This PR works for older versions of Android as well.
Note that there is some shifting of code to fix this as well as preparation to also fix 1936
Bugs Fixed
Fixes #1912
API Changes
None
Behavioral Changes
None
PR Checklist
mainat time of PR