Status of permission is Denied after choose approximately location in request permission dialog

[thao-vu-0106]

🐛 Bug Report

In android 12 or higher, when request both ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION will show dialog to choose precise location or approximate location.

when choose approximate location, the apps will grant only ACCESS_COARSE_LOCATION.

But the constant Permission.location in permission_handler will be "isGranted" only both ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION are allowed.

link reference: https://developer.android.com/training/location/permissions

After request permission location, i will get current location when granted and show dialog for user when the permission is denied. Because of above problem, when i choose approximate location, the app always show the dialog rather than requesting permission.

Expected behavior

• The value of Permission.location should be granted

Reproduction steps

• choose approximate location when request location then observe the status of Permission.location

Configuration

• Android 12 or higher
  Version: 10.0.1

Platform:

• 📱 iOS
• 🤖 Android

[enricocaliolo]

I am having the same issue. I noticed that, when choosing approximate location, the permission returns as PermanentlyDenied, which is not the expected behaviour, as, at least my app, could still work with only approximate location.

Also, I don't see a way, in this package, to handle the dialog that asks you to change to precise location or to change to approximate location, after choosing approximate location in the first permission dialog. Choosing to keep approximate location still leaves the permission as PermanentlyDenied. This dialog appears two times before not appearing anymore, so there is not a rationale for it either.

[Robbinb1993]

I have the same problem for coarse (approximate) location. Any update on this issue?

[kostov]

There is need to know which location (approximate or precise) was selected due to some functionality depends on it. For example, network_info_plus will do not work correctly if approximate location permission is granted.
Right now, if approximate location permission is granted by end-user, Permission.locationWhenInUse.status == PermissionStatus.denied on Android, but == PermissionStatus.granted on iOS.

[JeroenWeener]

Related to #559

[wojciechzahradnikdeviniti]

Hi, any updates?

[idealgeek007]

Any update on this ?
I'm facing the same issue

[wujek-srujek]

There is need to know which location (approximate or precise) was selected due to some functionality depends on it.

@kostov Interesting, I've just opened a feature request asking for exactly this, see #1356 and vote ;>

[Hoai-Phong]

@idealgeek007 same

[akadatsky]

any update?