This repository has been archived by the owner on May 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 505
[Bug][Android] MediaPicker permission for storage read doesn't work as intended on Android #1656
Labels
bug
Something isn't working
Comments
McFlemchSoda
changed the title
[Bug] MediaPicker permission for storage read doesn't work as intended on Android
[Bug][Android] MediaPicker permission for storage read doesn't work as intended on Android
Jan 26, 2021
This was fixed in the new 1.6.1 release. Duplicate of #1649 |
@mattleibow When I look at that issue, and looking at the PR changes, it only changes it for FilePicker, not for MediaPicker. The same needs to be done for MediaPicker. Or am I missing something? PR files changed: https://github.com/xamarin/Essentials/pull/1651/files |
We can just pretend this did not happen... |
mattleibow
added a commit
that referenced
this issue
Jan 27, 2021
CartBlanche
pushed a commit
to CartBlanche/Essentials
that referenced
this issue
Sep 21, 2021
I'm still finding this issue as well. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I found this closed issue which exactly represents the issue with MediaPicker now: #1537
Recap and quoting the closed issue:
"When using the MediaPicker on Android (Android 8 & 10) I noticed that the permission prompt for the storage read permission didn't work properly: When choosing "Deny" from the prompt the file system is still opened, even though it shouldn't. From reading the source code it seems that the permission is only asked, but nothing is done with the result (line 25): await Permissions.RequestAsync<Permissions.StorageRead>();."
Feels like an unfortunate copy/paste bug.
Steps to Reproduce
Expected Behavior
Photo system doesn't open.
Actual Behavior
Photo system opens, even though it shouldn't have the right permission. User is still able to navigate the file system and pick files from it.
Basic Information
Workaround
I'm working around this issue by prompting the permission request myself before we use the MediaPicker. If the user denies, the user won't be able to use this functionality.
The text was updated successfully, but these errors were encountered: