export shouldShowRequestPermissionRationale
for Android 13
#20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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