Open MichaelMaenner opened 1 year ago
Hello Michael!
The triple slash comes from the OS and I think it is correct. Please have a look at this thread: https://superuser.com/questions/352133/why-do-file-urls-start-with-3-slashes
Looks like this is following the URL specification (didn't know that either). I wonder why your app can't handle this. For me the following code works (with @capacitor/filesystem):
var content = await Filesystem.readFile({ path: decodeURIComponent(result.url) });
I will remove the extra slash in front of the filename - thanks for the hint!
Best regards
Again what learned with the triple slash - it joust doesn't look correct đŸ˜„
Tbh i have no idea why my app wasn't able to process the URL with the ///
in the first place.
I reworked the complete file handling on our part of the app and now it works as expected with the decodeUriComponent()
Greets & thanks, Michael
Describe the bug If i share a file, e.g. an image, the function
createSharedFileUrl
of the ShareViewController passes to many/
So, i get
file:///
and//filename.PNG
I can remove the
+ "/" +
from inside thecreateSharedFileUrl
which helps with the//
in front of the filename, but i cant figure out how to remove one of the///
without manipulating the file url itself.To Reproduce Steps to reproduce the behavior:
/
Expected behavior The shared file url should look like that:
Additional context Currently working with
"send-intent": "^3.0.12"
Inside of my Capacitor/Angular App i have added some sort of Workaround for that. Its definitely not pretty, but it works. But i also want to get rid of it.