React-native-document-picker: Different uri when selected directly from download panel and when selected from download folder from phone.

[shubhnik]

• #### When I select a file from Downloads straight from the drawer then I get this uri:
  content://com.android.providers.downloads.documents/document/raw%3A%2Fstorage%2Femulated%2F0%2FDownload%2FBittrexv1.csv
• #### But when I select file from OnePlus 5T/Downloads then I get this uri:
  `content://com.android.externalstorage.documents/document/primary%3ADownload%2FBittrexv1.csv

The first uri crashes the app, I am not able to read from the first uri. The second uri works fine. Can you let me know if I am doing something wrong or know of any fix for this. Thanks

I am selecting the document using this:

DocumentPicker.show(
      {
        filetype: [DocumentPickerUtil.allFiles()]
      },
      (error, res) => {
        console.log(res.uri)
        this.fileuri = res.uri;
      }
    );

[AsocialCoder]

same error...

[Elyx0]

Did you figure it out, it's an interesting edge case

[kamleshsindhal08]

same error faced

[Elyx0]

Can you retry with latest?

[shubhnik]

Hi, @Elyx0 thanks for looking into it. Currently, I am not working on that project so might be difficult for me to test. If anyone can retry and close this issue. Thanks for the contribution 👍

[Arya-Aghaei]

@Elyx0 Hi, tested with the latest version and still the same result, for me I get :

Error:Error: failed to stat path "null" because it does not exist or it is not a folder

when I try to check the file exist with RNFetchBlob.fs.stat(decodeURIComponent(res.uri)).then(...blah blah)

[dantman]

res.uri is not a file path, FS exists functions are not going to work.

[Arya-Aghaei]

@dantman So how can I check if the file exists or not? or in a better way of asking, is it safe to directly upload the file to the server with res.uri without checking the existence of it?

[dantman]

@Arrow891 If the user was able to pick a file, then it doesn't not exist. If the user can't pick a file then they'll cancel the picker, which will throw a cancelation error you can detect.

[Eramirez06]

i'm having same issue if i pick the doc directly from Download folder the path does not exist so i for that reason i cannot upload file to firebase.

but if i go to my internal storage and i pick the download folder and pick the same folder the uri returned let me upload the file to firebase

this sure only happend in Android, IOS works fine

[SmirnovM91]

Do you have any updates? How can I fix it?

[kayzenkayzen]

Same error, if someone knows how to fix it? we can create a fork with this fix!

It's a critical issue!

[mohammadgarmroodi]

Same error here,this is a big problem!

[abnnajaf]

Please be resolved!!! :weary: :weary: :weary:

[mohammadnia8000]

@Elyx0 solve the problem pleaseee

[muhammad-ihsan]

please someone help ☕

[tamslinn]

Also interested. We are using RNFetchBlob.fs.stat(res.uri) to check if the file can be accessed, as want to screen out files picked from google drive (as the user may be offline). However calling this with the uri returned for the downloads folder results in failed to stat path "null" ... so we can't use this approach, and I'm not sure how else to do the check.

[glorynguyen]

Also interested. We are using RNFetchBlob.fs.stat(res.uri) to check if the file can be accessed, as want to screen out files picked from google drive (as the user may be offline). However calling this with the uri returned for the downloads folder results in failed to stat path "null" ... so we can't use this approach, and I'm not sure how else to do the check.

I think it's related to this line
PathResolver.java#L56

[YesSkyscrapers]

please someone help ☕

[glorynguyen]

I fixed it by upgraded rn-fetch-blob package version to 0.12.0 in package.json
"rn-fetch-blob": "0.12.0"

Hope it help

[meliodev]

Try out this. It worked for me !

   if (res.uri.startsWith('content://')) {
                const uriComponents = res.uri.split('/')
                const fileNameAndExtension = uriComponents[uriComponents.length - 1]
                const destPath = `${RNFS.TemporaryDirectoryPath}/${fileNameAndExtension}`

                await RNFS.copyFile(res.uri, destPath)
            }

The only issue is that you need memory on device to store the cached file. We would be grateful if somebody brings out a better solution !

[thipoeta]

@meliodev work like a charm!

[yestay90]

@shubhnik
Try to decode the uri before using it
if (Platform.OS === 'ios' || (Platform.OS === 'android' && parsedUri.includes('com.android.providers'))) { parsedUri = decodeURIComponent(parsedUri); }