Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
fileProvider - Any specific reason to use "root-path"? #129
I was in a situation where I had to use the fileProvider to get a file without NoNonsense-FilePicker (gallery image picker).
I realized that this library advise to use the nnf_provider_paths xml file, which uses the root-path tag. The Utils.getFileForUri() method also check for that tag specifically.
In the official documentation, the root-path tag doesn't seem to exist, so I am curious of the reason behind that usage. All of the examples of using fileProvider I found use file-path:
<paths xmlns:android="http://schemas.android.com/apk/res/android"> <files-path path="images/" name="myimages" /> </paths>
Wouldn't there be a way to use
of course you can. It all comes down to what you put in your manifest. You can specify multiple filepickers (if you want) that each use their own filepicker/metadata-xml.
The only limitation is that you can't use the built-in
This could probably be an interesting alternative to the existing way to override