Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DeniedPermanently triggered when selecting Approximate instead of Precise location #22

Open
a0g83agbc84 opened this issue Sep 19, 2022 · 2 comments

Comments

@a0g83agbc84
Copy link

As stated in title.

Compile SDK: 33
Android version: 13
Image: https://i.imgur.com/FwdLvgh.png

CoroutineScope(Default).launch {
            val result = requestPermissionsAsync(
                Manifest.permission.ACCESS_COARSE_LOCATION,
                Manifest.permission.ACCESS_FINE_LOCATION
            )

            when (result) {
                is PermissionResult.Granted -> {Log.e("Activity", "GRANTED") } // woohoo, all requested permissions granted
                is PermissionResult.Denied.JustDenied -> {Log.e("Activity", "JUST DENIED") } // at least one permission was denied, maybe we forgot to register it in the AndroidManifest?
                is PermissionResult.Denied.NeedsRationale -> {Log.e("Activity", "NEEDS") } // user clicked Deny, let's show a rationale
                is PermissionResult.Denied.DeniedPermanently -> { Log.e("Activity", "DENIED PERM")} // Android System won't show Permission dialog anymore, let's tell the user we can't proceed
                is PermissionResult.Cancelled -> {Log.e("Activity", "CANCELLED") } // interaction was interrupted
            }
        }
@deva666
Copy link
Owner

deva666 commented Sep 20, 2022

Thanks for reporting this. I am not sure how to proceed with this.
One thing is that I can't capture or control the native dialog that Android presents.
Second thing is if I change the code responsible for this then DeniedPermanently logic will be also changed. This is a breaking change.
Let me think about this.

@deva666
Copy link
Owner

deva666 commented Nov 4, 2022

This should be fixed with the latest v3.0.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants