Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork924
Fix: location permission returns denied when user selects approximate#1504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
HasanAlqaisi wants to merge1 commit intoBaseflow:mainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
+21 −3
Conversation
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
…ied when user selects approximate
KingkanB commentedDec 12, 2025
I want this fix too. |
quyenvsp commentedDec 18, 2025
I can't reproduce the bug. What device are you using? What uses-permission you declared in AndroidManifest.xml? |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
3 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.
Uh oh!
There was an error while loading.Please reload this page.
Issue: On Android 12 (API 31) and higher, users have the option to grant "Approximate" location (Coarse) instead of "Precise" location (Fine). When a user selects "Approximate", the system grants ACCESS_COARSE_LOCATION but denies ACCESS_FINE_LOCATION.
Currently, permission_handler incorrectly reports the status as PermissionStatus.denied in this scenario. This prevents apps from functioning that are capable of working with only approximate location.
It is also reported as anissue here
Expected Behavior: If the user grants "Approximate" location, the permission status should be reported as PermissionStatus.granted, as the app does have access to location data (with lower accuracy).
Pre-launch Checklist
pubspec.yamlwith an appropriate new version according to thepub versioning philosophy, or this PR is does not need version changes.CHANGELOG.mdto add a description of the change.///).main.dart format .and committed any changes.flutter analyzeand fixed any errors.