Open janseris opened 2 years ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Description
this sample shows how to select and capture photo (and video).
It copies the selected file into
FileSystem.CacheDirectory
first (which is/data/user/0/{ApplicationID}/cache/
on Android) and then reads it. This results in this flow on Android:Copying file to
FileSystem.CacheDirectory
can be avoided and is in my opinion redundant. When copy toFileSystem.CacheDirectory
from the sample is used, the application cache (from application info in Android) grows by 2 × filesize per every different file selected. When "direct access" is used, the application cache (from application info in Android) grows by 1× filesize per every file selected.Btw. even when using "direct access", the application copies the original file into the application everytime it is picked. What is the point of the cache then? It generates a new GUID into the second GUID position in the
cache/{guid}/{-> here guid}/DSC_0296.JPG
path for every subsequent use ofMediaPicker
.I can do this:
With the following output:
Steps to Reproduce
MAUI (I am using MAUI Blazor) app Use MediaPicker example from MAUI Essentials sample code in the maui repo
Version with bug
Release Candidate 2 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android, Windows
Affected platform versions
Android 11, Windows all
Did you find any workaround?
No response
Relevant log output
No response
Sample code (.razor page):
Note: uses Blazorise
Span
andButton
components (they can be replaced with regularspan
andbutton
tags) andDivider
component can be removedEdit: sample code fixed