79656065

Date: 2025-06-06 14:35:32
Score: 1
Natty:
Report link

MediaPicker the same way as FilePicker FullPath is returning a rather virtual path than the real path. Let me illustrate:

I have this file on my Android Emulator Downloads folder:

enter image description here

By using adb shell on my Android Adb Command Prompt I can see the physical path to my file is /storage/emulated/0/Download/ntk.p12.

Now let's try opening this file with FilePicker:

enter image description here

So the same file is showing in different paths.

But, what happens if I manually try to open the physical path I obtained via adb shell?

enter image description here

What about trying now with the FullPath obtained from FilePicker?

enter image description here

Or you can follow the documentation and just use OpenReadAsync:

enter image description here

I agree the documentation could be explained better. What they are trying to say is that you should be careful on your cross-platform solutions since FullPath has different behaviours.

Reasons:
  • Probably link only (1):
  • Long answer (-0.5):
  • Has code block (-0.5):
  • Contains question mark (0.5):
  • Low reputation (0.5):
Posted by: galex