Android `check` shows that Notifications can be requested, but it is not requestable about react-native-permissions HOT 2 CLOSED

Hi 👋 This is expected, it cannot be known on Android before requested.

If you check the Android permission flow, you see that there's no way it returns blocked before calling request. That's also why the builtin module (PermissionsAndroid) return a boolean for check, and a status for request.

Note that you have this warning in the check README documentation:

Consider this:

• Before showing the screen that require the permission, check it
• If it's granted, mount the screen that use it
• If it's blocked, display a screen that explain that the user will have to go to settings to enable it (+ show a button that call openSettings) (will never ne visible on Android, but could be on iOS)
• If it's denied, display a screen with a button to perform a request. After that, if it's granted -> mount the screen that use it. If it's blocked -> Display an alert or the blocked screen before encouraging going to the settings (using openSettings)

The UX is great on iOS, good enough on Android given the platform limitations

from react-native-permissions.

Thank you for the explanation!

from react-native-permissions.