How can I serve files from the SECONDARY external storage using the FileProvider
?
The current implementation of the FileProvider
handles on
As workaround you can use absolute pathes:
<!-- secondary external storage with path /storage/extSdCard -->
<root-path path="/storage/extSdCard/Android/data/YOUR_PACKAGE/files/" name="extSdCard" />
<!-- secondary external storage with path /storage/sdcard1 -->
<root-path path="/storage/sdcard1/Android/data/YOUR_PACKAGE/files/" name="sdcard1" />
And the answer is... FileProvider
does not support that. With Android 7 this is even more an issue, due to deprecation of the file://
Uri scheme.
I issued a bug report.
To handle files located on external sdcards, I changed my provider_paths.xml to
<paths>
<external-path path="." name="external_files" />
<root-path path="." name="sdcard1" />
</paths>
FileProvider not support secondary storage because of the code below:
Code from support:support-core-utils:26.1.0 FileProvider
} else if (TAG_EXTERNAL_FILES.equals(tag)) {
File[] externalFilesDirs = ContextCompat.getExternalFilesDirs(context, null);
if (externalFilesDirs.length > 0) {
target = externalFilesDirs[0];// Code here, That's why!!!
}
} else if (TAG_EXTERNAL_CACHE.equals(tag)) {
However, there is a special TAG in FileProvider : root-path which is not covered in official reference.
if (TAG_ROOT_PATH.equals(tag)) {
target = DEVICE_ROOT;// DEVICE_ROOT = new File("/");
} else if (TAG_FILES_PATH.equals(tag)) {
So, root-path matches all the path.
Just type this code in your FileProvider xml, then FileProvider can handle File in secondary storage.
<root-path name="root" path="." />
Be aware, it may leak your directory structure.
So I ended up doing the following:
Try to create to Uri via FileProvider, If it fails due to:
java.lang.IllegalArgumentException: Failed to find configured root that contains
I'm just creating a regular Uri.
Here's my code:
try {
uri = FileProvider.getUriForFile(context,
MY_AUTHORITY_STRING,
imageFile);
} catch (Exception e) {
CLog.d(TAG, e);
uri = Uri.fromFile(imageFile);
}
I don't know why, but it's working, the FileProvider can't access the file (As it's in secondary external storage) and then the uri is created successfully in the catch clause.
Weird Google...very weird.