Permission ask goes into a loop

[teolemon]

What

• Permission ask goes into a loop
• Probably related to #2742

Video

https://user-images.githubusercontent.com/1689815/183608551-d5af6edd-b53d-4034-b279-31edf3381d2a.mp4

[g123k]

There is also an issue on iOS devices, where even if the permission is granted, the screen continues to ask for it.

[teolemon]

https://user-images.githubusercontent.com/1689815/184495530-db9897af-4652-4833-9cd2-3c4dfee0ee39.mp4

[teolemon]

Android device, after the fix for iOS

[g123k]

I need reproducible steps please, because when I launch the app, the settings Activity launches as expected. And this not after the fix for iOS, as you've already mentioned this issue if I may

[teolemon]

Manually disabling permissions should suffice

[teolemon]

We might add a message on how to Reenable sibce after 3/4 denials, Android stops asking

[teolemon]

Also, not being able to open parameters screen is surprising

[g123k]

I'm able to reproduce the issue, but I don't really understand it. It seems the Flutter side is OK.

However the native part doesn't launch the screen. I will open an issue on the plugin's tracker

[monsieurtanuki]

Meanwhile, is there a solution to enhance the user experience? So we don't have to wait for the plugin fix?

[g123k]

Meanwhile, is there a solution to enhance the user experience? So we don't have to wait for the plugin fix?

You mean to create the dedicated screen to ask for the permission? Because here, it won't change anything

[monsieurtanuki]

I meant something like

• OK, if we use this plugin we are supposed to ask for permission this way.
• But it's not an obligation, we can call directly the standard 'ask permission' screen.
• Doing so, we use the standards (less likely to bug), and hopefully the plugin will acknowledge the permission state

But maybe this suggestion is not relevant.

[g123k]

This is what the plugin should do actually (they use the native Intent).

Calling the screen from our app would require developing the MethodChannel thing. Not that complicated, but since it's the goal of the permission, we should wait a little before taking any decision.

(From my understanding, it's a race condition in their code)

[monsieurtanuki]

For the record, there's a new version (10.0.0) of https://pub.dev/packages/permission_handler

[g123k]

This issue was fixed a few releases ago