access content://com.android.providers.media.documents/document/image%3A99

[EyalSi]

I'm getting a content uri in android while using react-native-document-picker or react-native-contacts (for the avatars).
URIs like:
'content://com.android.providers.media.documents/document/image%3A99'
Trying to access this file fails with "File does not exist"

const urlDecoded = decodeURIComponent(url);
RNFS.stat(urlDecoded)
.then((file) => {
console.log("RNFS URL SUCCESS", file);
})
.catch((err) => {
console.log("RNFS URL ERROR", err);
});

Any idea how to access the file?
10x

[itinance]

Hi @EyalSi! The scheme "content://" is currently not supported.

PRs are very appreciated.

[lukasbowen]

@itinance Does this still need to be resolved? I saw a PR request that could resolve it but I believe it was rejected?

[nzhtrtlc]

I have the same error, any updates ?

[lukasbowen]

I have a fix locally in my project; however, I am hesitant to create a PR request since there is one that does the same already pending.

[itinance]

@LukBowen which one do you mean?

[lukasbowen]

PR #49

[itinance]

Yes, i remember. I turned back to the contributor but he never answered. I will modify this PR manually to keep backward compatibility alive.

[lukasbowen]

Sorry, I didn't realize that was it was missing backwards compatibility. Other wise I would have just create my own PR.

[itinance]

Submitting your own PR would be a good option! I would merge quickly (while CET-timezone ;) )

[lukasbowen]

I can still do it; however, it will have to be later today. Currently working on a separate project at work.

[itinance]

Great and many thanks. No rush :)

[krzysztof-miemiec]

Hey @itinance, I just added a PR based on @jrichardlai's work. I hope we'll finally be able to work with content URI's on Android with no trouble! 🙂