⚡️ [Android] Always declare READ_EXTERNAL_STORAGE on Android
#874
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlexV525
force-pushed
the
android-read-permission
branch
from
49e99eb
to
c4b4faf
Compare
AlexV525
changed the title
READ_EXTERNAL_STORAGE on Android 12+READ_EXTERNAL_STORAGE on Android
# Conflicts: # CHANGELOG.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Although the document says starting in API level 33, this permission has no effect, we still heard from many users that devices are unable to fetch assets. From the comment #852 (comment) the permission might affect the result. So until the permission is deprecated, we might continue to declare the permission as well.
Related issues: