Fix request permission is not always resolving in Android 16 #53898
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.
Summary:
Fixes: #53887
Fixes: expo/expo#39480
In the latest Android 16 update, requesting permissions does not always change the app's state (the
onPause
andonResume
functions aren't called). For instance, when you deny permission 3 times, the last promise won't resolve until you move the app to the background. The current logic inside theReactActivityDelegate
assumes that Android will callonResume
after receiving permission state information from the system, which is no longer the case.Probably connected with this commit
Changelog:
[ANDROID] [FIXED] - Fix request permission not always resolving in Android 16
Test Plan: