Bacancy Technology
Bacancy Technology represents the connected world, offering innovative and customer-centric information technology experiences, enabling Enterprises, Associates and the Society to Rise™.
12+
Countries where we have happy customers
1050+
Agile enabled employees
06
World wide offices
12+
Years of Experience
05
Agile Coaches
14
Certified Scrum Masters
1000+
Clients projects
1458
Happy customers
Artificial Intelligence
Machine Learning
Salesforce
Microsoft
SAP
July 31, 2023
Whenever we pick up a document on an Android device from the document picker, it returns us a URI something like
content://< authority >/< path >
Where is the content provider authority of the selected file and is the file path relative to the content provider’s root directory.
Which is not a valid link if you use it to send over the API, for example, when you are uploading a file on Firebase Storage.
To overcome this problem, we can use the copyTo: ‘documentDirectory’ option in the DocumentPicker. It will copy the selected file into the app’s document directory and return a URI pointing to the copied file in the document directory.
Here is how to achieve this:
let documents = await DocumentPicker.pickMultiple({ type: DocumentPicker.types.allFiles, //You can mention all the file types required here copyTo: 'documentDirectory', }); documents = documents.map(doc => ({ ...item, fileCopyUri: `file://${decodeURIComponent(doc.fileCopyUri)}`, }));
Using the above code snippet, the URI which gets returned will look something like
file://< path >
Where
The fileCopyUri property is created by appending `file://` before the copied file uri so it can have a format like file://< path >
The decodeURIComponent function will decode any URI-encoded characters in the URI such as spaces or non-ASCII characters.
For More Information: NPMJS