This simply exports the function so that it can be used directly in client apps.
Nothing was changed with the manner in which shouldShowRequestPermissionRationale is currently being used in the plugin. However, that usage does not seem to really match with the Android docs. It seems that when shouldShowRequestPermissionRationale returns true, the permission check returns GRANT_RESULTS.DENIED. This does not make it possible to distinguish between a truly denied permission and one that simply needs to show a rationale before requesting the permission.
As per Android docs*, the flow should be:
check for permission
check for shouldShowRequestPermissionRationale
request permission (after showing rationale if indicated by step 2)
This simply exports the function so that it can be used directly in client apps. Nothing was changed with the manner in which
shouldShowRequestPermissionRationale
is currently being used in the plugin. However, that usage does not seem to really match with the Android docs. It seems that whenshouldShowRequestPermissionRationale
returns true, the permission check returns GRANT_RESULTS.DENIED. This does not make it possible to distinguish between a truly denied permission and one that simply needs to show a rationale before requesting the permission.As per Android docs*, the flow should be:
shouldShowRequestPermissionRationale