-
Notifications
You must be signed in to change notification settings - Fork 435
Handle Android media content URIs and gate READ_MEDIA permissions #4130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7ba32a4
Handle Android media content URIs and gate READ_MEDIA permissions
shai-almog cfda4ee
Document Android media fallback and fix device-runner test
shai-almog b971812
Refine media playback test for Codename One compatibility
shai-almog 2ec941a
Simplify media playback screenshot test
shai-almog bcc5b4b
Restore MediaStore permission prompt
shai-almog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new logic avoids requesting any runtime permission whenever the URI scheme is
content://. That works for document-picker grants, but it also suppresses the previousPermissionsHelper.checkForPermission()call for MediaStore URIs such ascontent://media/external/..., which still requireREAD_MEDIA_*/READ_EXTERNAL_STORAGEwhen no temporary grant was provided. Before this changecreateMedia()asked for the permission and playback succeeded; now it returns an error onceMediaPlayer.create()hits aSecurityException. Apps that pass a MediaStore URI without having asked for the permission themselves will silently regress.Useful? React with 👍 / 👎.