thanks for replying.
This is basically what I do. I’m using the
juce::URL class though, which takes care of the
This is my function:
void shareFile(const File& path)
DBG("ContentSharer Path invalid: " << path.getFullPathName());
DBG("ContentSharer Path valid: " <<path.getFullPathName());
DBG("ContentSharer calling with URL " << files.toString(true));
And this is the Debug Output that’s coming from these prints:
> 2020-02-18 09:37:03.393 20912-20912/com.myCompany.myApp I/JUCE: ContentSharer Starting share...
> 2020-02-18 09:37:03.397 20912-20912/com.myCompany.myApp I/JUCE: ContentSharer Path valid: /data/user/0/com.myCompany.myApp/My Company/My App/Recordings/My Recording - 16 Feb 2020 13:33.flac
> 2020-02-18 09:37:03.397 20912-20912/com.myCompany.myApp I/JUCE: ContentSharer calling with URL file:///data/user/0/com.myCompany.myApp/My%20Company/My%20App/Recordings/My%20Recording%20-%2016%20Feb%202020%2013%3A33.flac
Could the spaces or symbols in the file path be a problem here? Thing is, these folder names/file names are user generated, so they can definitely include spaces and all that stuff… but URL shouldn’t have a problem with that…
//Edit: just tried sharing a path without any special symbols or spaces in the pathname… no success either.
Also as mentioned in my original post, the same function successfully works on iOS… so I’m pretty sure that I’m handling it right, but it still fails on all my Android devices and simulators…