From 9ab4ebb72e648156b2af60578de112022f856fb4 Mon Sep 17 00:00:00 2001 From: Ben Hsieh Date: Thu, 3 Aug 2017 09:37:08 +0800 Subject: [PATCH 01/18] bump to 0.10.8 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 0d88ec178..a93dba81d 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "react-native-fetch-blob", - "version": "0.10.7", + "version": "0.10.8", "description": "A module provides upload, download, and files access API. Supports file stream read/write for process large files.", "main": "index.js", "scripts": { From 1336555d79014a181ab79350434e016ea1bc8324 Mon Sep 17 00:00:00 2001 From: Ben Hsieh Date: Thu, 3 Aug 2017 09:42:16 +0800 Subject: [PATCH 02/18] Update PULL_REQUEST_TEMPLATE --- .github/PULL_REQUEST_TEMPLATE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE index cef8ed2af..b03e3e8e3 100644 --- a/.github/PULL_REQUEST_TEMPLATE +++ b/.github/PULL_REQUEST_TEMPLATE @@ -1,5 +1,5 @@ Thank you for making a pull request ! Just a gentle reminder :) 1. If the PR is offering a feature please make the request to our "Feature Branch" 0.11.0 -2. Bug fix request to "Bug Fix Branch" 0.10.8 +2. Bug fix request to "Bug Fix Branch" 0.10.9 3. Correct README.md can directly to master From 2aea0b58e99581000d7336697e70b3bba7670a50 Mon Sep 17 00:00:00 2001 From: grylance Date: Wed, 9 Aug 2017 16:12:33 +0100 Subject: [PATCH 03/18] Fix path argument in iOS excludeFromBackupKey (#473) --- ios.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ios.js b/ios.js index 566b424e2..340ef04cf 100644 --- a/ios.js +++ b/ios.js @@ -43,7 +43,7 @@ function openDocument(path:string, scheme:string) { * @param {string} url URL of the resource, only file URL is supported * @return {Promise} */ -function excludeFromBackupKey(url:string) { +function excludeFromBackupKey(path:string) { return RNFetchBlob.excludeFromBackupKey('file://' + path); } From 821eeb0f9db1736009ee791c14298ef72144a825 Mon Sep 17 00:00:00 2001 From: Kota Furusawa Date: Thu, 24 Aug 2017 10:02:20 +0800 Subject: [PATCH 04/18] Fix README (#501) remove extra space --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7680fab86..3c7d24a59 100644 --- a/README.md +++ b/README.md @@ -236,7 +236,7 @@ RNFetchBlob console.log('The file saved to ', res.path()) // Beware that when using a file path as Image source on Android, // you must prepend "file://"" before the file path - imageView = + imageView = }) ``` From 5db2a74b077685666ea70c94c4f92c237cc66aa8 Mon Sep 17 00:00:00 2001 From: Catalin Miron Date: Thu, 12 Oct 2017 22:55:43 +0300 Subject: [PATCH 05/18] Fix README.md Fix example links for Download and Multipart/form-data --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3c7d24a59..7723d1ce7 100644 --- a/README.md +++ b/README.md @@ -18,9 +18,9 @@ A project committed to making file access and data transfer easier and more effi * [Installation](#user-content-installation) * [HTTP Data Transfer](#user-content-http-data-transfer) * [Regular Request](#user-content-regular-request) - * [Download file](#user-content-download-example--fetch-files-that-needs-authorization-token) + * [Download file](#download-example-fetch-files-that-need-authorization-token) * [Upload file](#user-content-upload-example--dropbox-files-upload-api) - * [Multipart/form upload](#user-content-multipartform-data-example--post-form-data-with-file-and-data) + * [Multipart/form upload](#multipartform-data-example-post-form-data-with-file-and-data) * [Upload/Download progress](#user-content-uploaddownload-progress) * [Cancel HTTP request](#user-content-cancel-request) * [Android Media Scanner, and Download Manager Support](#user-content-android-media-scanner-and-download-manager-support) From e39a41b8ebd9182692d5cd876f8111aba5060ce5 Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Wed, 6 Dec 2017 07:51:15 +0100 Subject: [PATCH 06/18] add "maintainer missing" --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 3c7d24a59..dc5b3c5a6 100644 --- a/README.md +++ b/README.md @@ -5,6 +5,11 @@ A project committed to making file access and data transfer easier and more efficient for React Native developers. > For Firebase Storage solution, please upgrade to the latest version for the best compatibility. +## RNFB MAINTAINER GONE MISSING (Help Wanted) + +wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that is left, is there anybody who else who could provide a maintained fork in the meantime? Create an issue and address me (@lll000111) and I'll add a link to your maintained repo fork right here. + + ## Features - Transfer data directly from/to storage without BASE64 bridging - File API supports regular files, Asset files, and CameraRoll files From 52c477315d473289f1bede66a51088c366dad643 Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Wed, 6 Dec 2017 07:52:09 +0100 Subject: [PATCH 07/18] add link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dc5b3c5a6..c0a3124e3 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ A project committed to making file access and data transfer easier and more effi ## RNFB MAINTAINER GONE MISSING (Help Wanted) -wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that is left, is there anybody who else who could provide a maintained fork in the meantime? Create an issue and address me (@lll000111) and I'll add a link to your maintained repo fork right here. +wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that is left, is there anybody who else who could provide a maintained fork in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)) and I'll add a link to your maintained repo fork right here. ## Features From 455097db73ccdb9d56426a47ccd1db949809a5b3 Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Wed, 6 Dec 2017 07:54:44 +0100 Subject: [PATCH 08/18] more vertical space around the message --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index c0a3124e3..20b08470b 100644 --- a/README.md +++ b/README.md @@ -5,10 +5,13 @@ A project committed to making file access and data transfer easier and more efficient for React Native developers. > For Firebase Storage solution, please upgrade to the latest version for the best compatibility. +
+ ## RNFB MAINTAINER GONE MISSING (Help Wanted) wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that is left, is there anybody who else who could provide a maintained fork in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)) and I'll add a link to your maintained repo fork right here. +
## Features - Transfer data directly from/to storage without BASE64 bridging From 51f8a19e0960987717ee521aa960a8737b99444b Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Wed, 6 Dec 2017 07:58:07 +0100 Subject: [PATCH 09/18] update the maintainer-missing message --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 20b08470b..883f0fd13 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ A project committed to making file access and data transfer easier and more effi ## RNFB MAINTAINER GONE MISSING (Help Wanted) -wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that is left, is there anybody who else who could provide a maintained fork in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)) and I'll add a link to your maintained repo fork right here. +wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here.
From 684f6df2838b41536a0e535966ffa5586866e79b Mon Sep 17 00:00:00 2001 From: nd-02110114 Date: Tue, 23 Jan 2018 15:05:05 +0900 Subject: [PATCH 10/18] add close tag --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 883f0fd13..edb5e170e 100644 --- a/README.md +++ b/README.md @@ -644,7 +644,7 @@ RNFetchBlob.fs.readStream( console.log('oops', err) }) ifstream.onEnd(() => { - }) }) ``` From 58df91fe8dd446dc3c3cb06474bd76d63bef13ff Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Tue, 20 Feb 2018 09:26:24 +0100 Subject: [PATCH 11/18] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 883f0fd13..e64e8f34c 100644 --- a/README.md +++ b/README.md @@ -5,12 +5,14 @@ A project committed to making file access and data transfer easier and more efficient for React Native developers. > For Firebase Storage solution, please upgrade to the latest version for the best compatibility. +

## RNFB MAINTAINER GONE MISSING (Help Wanted) -wkh237's last Github activity was in September 2017. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. +wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot given anyone else rights on this repo, somebody needs to fork it and become a full maintainer. +

## Features From e6480db3192b0c44721899bfc8d8966780e80026 Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Tue, 20 Feb 2018 09:26:57 +0100 Subject: [PATCH 12/18] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e64e8f34c..10ca0df76 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ A project committed to making file access and data transfer easier and more effi ## RNFB MAINTAINER GONE MISSING (Help Wanted) -wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot given anyone else rights on this repo, somebody needs to fork it and become a full maintainer. +wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot give anyone else rights on this repo, somebody needs to fork it and become a full maintainer.

From 05768a26afb9f6c4a813c706324e7798dffe068b Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Tue, 20 Mar 2018 17:00:49 +0100 Subject: [PATCH 13/18] Update README.md --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 486897675..5a655c565 100644 --- a/README.md +++ b/README.md @@ -1,19 +1,23 @@ -# react-native-fetch-blob -[![release](https://img.shields.io/github/release/wkh237/react-native-fetch-blob.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/releases) [![npm](https://img.shields.io/npm/v/react-native-fetch-blob.svg?style=flat-square)](https://www.npmjs.com/package/react-native-fetch-blob) ![](https://img.shields.io/badge/PR-Welcome-brightgreen.svg?style=flat-square) [![](https://img.shields.io/badge/Wiki-Public-brightgreen.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/wiki) [![npm](https://img.shields.io/npm/l/react-native-fetch-blob.svg?maxAge=2592000&style=flat-square)]() - +## RNFB MAINTAINER GONE MISSING (Help Wanted) -A project committed to making file access and data transfer easier and more efficient for React Native developers. -> For Firebase Storage solution, please upgrade to the latest version for the best compatibility. +wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot give anyone else rights on this repo, somebody needs to fork it and become a full maintainer. -

-## RNFB MAINTAINER GONE MISSING (Help Wanted) +## About Pull Requests -wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot give anyone else rights on this repo, somebody needs to fork it and become a full maintainer. +I cannot (@lll000111) handle them, I'm not the owner. My own PRs are still in the queue waiting for review from the owner. I coulöd merge the PRs of others but not my own... but since I am in no position to do anything with this repo, I don't do mobile development, I don't even have a smart phone, I won't merge anything. **In any case though,** you should not send PRs for `master` but against the `0.10.9` branch. It already is quite different from `master`. So try that branch first if you want to patch, not `master`, even for your own fork.

+
+ +# react-native-fetch-blob +[![release](https://img.shields.io/github/release/wkh237/react-native-fetch-blob.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/releases) [![npm](https://img.shields.io/npm/v/react-native-fetch-blob.svg?style=flat-square)](https://www.npmjs.com/package/react-native-fetch-blob) ![](https://img.shields.io/badge/PR-Welcome-brightgreen.svg?style=flat-square) [![](https://img.shields.io/badge/Wiki-Public-brightgreen.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/wiki) [![npm](https://img.shields.io/npm/l/react-native-fetch-blob.svg?maxAge=2592000&style=flat-square)]() + + +A project committed to making file access and data transfer easier and more efficient for React Native developers. +> For Firebase Storage solution, please upgrade to the latest version for the best compatibility. ## Features - Transfer data directly from/to storage without BASE64 bridging From c4c3d43636519106c94f9d1db6afca90f658243f Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Tue, 20 Mar 2018 17:03:43 +0100 Subject: [PATCH 14/18] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5a655c565..177e968f9 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ wkh237's last Github activity was in September 2017, and he has not reacted to e ## About Pull Requests -I cannot (@lll000111) handle them, I'm not the owner. My own PRs are still in the queue waiting for review from the owner. I coulöd merge the PRs of others but not my own... but since I am in no position to do anything with this repo, I don't do mobile development, I don't even have a smart phone, I won't merge anything. **In any case though,** you should not send PRs for `master` but against the `0.10.9` branch. It already is quite different from `master`. So try that branch first if you want to patch, not `master`, even for your own fork. +I (@lll000111) cannot handle them, I'm not the owner. My own PRs are still in the queue waiting for review from the owner. I could merge the PRs of others but not my own(!)... but since I am in no position to manage this repo — I don't do mobile development, I don't even have a smart phone — I won't merge anything. **In any case though,** you should not send PRs for `master` but against the `0.10.9` branch. It already is quite different from `master`. So try that branch first if you want to patch, not `master`, even for your own fork and your private patches.

From c582d0f1b684eb6265d86d0a7847522fba33a56e Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Thu, 22 Mar 2018 23:56:31 +0100 Subject: [PATCH 15/18] Update README.md --- README.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 177e968f9..7ed5633e6 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,17 @@ -## RNFB MAINTAINER GONE MISSING (Help Wanted) +## RNFB MAINTAINER GONE MISSING (New Repository Location) -wkh237's last Github activity was in September 2017, and he has not reacted to emails either. Since there is a lot of work on issues and PRs that needs to be done, is there anybody who could provide a maintained fork of this package in the meantime? Create an issue and address (ping) me ([@lll000111](https://github.com/lll000111)), or send me an email, and I'll add a link to your maintained repo fork right here. I don't have admin rights, I cannot accept PRs, I cannot give anyone else rights on this repo, somebody needs to fork it and become a full maintainer. +wkh237's last Github activity was in September 2017, and he has not reacted to emails either. This repository no longer is the main location of "react-native-fetch-blob". +**UPDATE 22 March, 2018** + +The owners of this fork have agreed to maintain this package: + +https://github.com/joltup/react-native-fetch-blob + +That means issues and PRs should be posted there. + + +

## About Pull Requests From be49c45933536a5dc0e405d0aaf46d1a9c873a7e Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Thu, 22 Mar 2018 23:59:54 +0100 Subject: [PATCH 16/18] Update README.md --- README.md | 807 +----------------------------------------------------- 1 file changed, 3 insertions(+), 804 deletions(-) diff --git a/README.md b/README.md index 7ed5633e6..31bb6c652 100644 --- a/README.md +++ b/README.md @@ -1,814 +1,13 @@ -## RNFB MAINTAINER GONE MISSING (New Repository Location) +# New Maintainers and Repository Location wkh237's last Github activity was in September 2017, and he has not reacted to emails either. This repository no longer is the main location of "react-native-fetch-blob". -**UPDATE 22 March, 2018** - The owners of this fork have agreed to maintain this package: https://github.com/joltup/react-native-fetch-blob That means issues and PRs should be posted there. +--- -
-
- -## About Pull Requests - -I (@lll000111) cannot handle them, I'm not the owner. My own PRs are still in the queue waiting for review from the owner. I could merge the PRs of others but not my own(!)... but since I am in no position to manage this repo — I don't do mobile development, I don't even have a smart phone — I won't merge anything. **In any case though,** you should not send PRs for `master` but against the `0.10.9` branch. It already is quite different from `master`. So try that branch first if you want to patch, not `master`, even for your own fork and your private patches. - -
-
-
- -# react-native-fetch-blob -[![release](https://img.shields.io/github/release/wkh237/react-native-fetch-blob.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/releases) [![npm](https://img.shields.io/npm/v/react-native-fetch-blob.svg?style=flat-square)](https://www.npmjs.com/package/react-native-fetch-blob) ![](https://img.shields.io/badge/PR-Welcome-brightgreen.svg?style=flat-square) [![](https://img.shields.io/badge/Wiki-Public-brightgreen.svg?style=flat-square)](https://github.com/wkh237/react-native-fetch-blob/wiki) [![npm](https://img.shields.io/npm/l/react-native-fetch-blob.svg?maxAge=2592000&style=flat-square)]() - - -A project committed to making file access and data transfer easier and more efficient for React Native developers. -> For Firebase Storage solution, please upgrade to the latest version for the best compatibility. - -## Features -- Transfer data directly from/to storage without BASE64 bridging -- File API supports regular files, Asset files, and CameraRoll files -- Native-to-native file manipulation API, reduce JS bridging performance loss -- File stream support for dealing with large file -- Blob, File, XMLHttpRequest polyfills that make browser-based library available in RN (experimental) -- JSON stream supported base on [Oboe.js](https://github.com/jimhigson/oboe.js/) @jimhigson - -## TOC (visit [Wiki](https://github.com/wkh237/react-native-fetch-blob/wiki) to get the complete documentation) -* [About](#user-content-about) -* [Installation](#user-content-installation) -* [HTTP Data Transfer](#user-content-http-data-transfer) - * [Regular Request](#user-content-regular-request) - * [Download file](#download-example-fetch-files-that-need-authorization-token) - * [Upload file](#user-content-upload-example--dropbox-files-upload-api) - * [Multipart/form upload](#multipartform-data-example-post-form-data-with-file-and-data) - * [Upload/Download progress](#user-content-uploaddownload-progress) - * [Cancel HTTP request](#user-content-cancel-request) - * [Android Media Scanner, and Download Manager Support](#user-content-android-media-scanner-and-download-manager-support) - * [Self-Signed SSL Server](#user-content-self-signed-ssl-server) - * [Transfer Encoding](#user-content-transfer-encoding) - * [Drop-in Fetch Replacement](#user-content-drop-in-fetch-replacement) -* [File System](#user-content-file-system) - * [File access](#user-content-file-access) - * [File stream](#user-content-file-stream) - * [Manage cached files](#user-content-cache-file-management) -* [Web API Polyfills](#user-content-web-api-polyfills) -* [Performance Tips](#user-content-performance-tips) -* [API References](https://github.com/wkh237/react-native-fetch-blob/wiki/Fetch-API) -* [Caveats](#user-content-caveats) -* [Development](#user-content-development) - -## About - -This project was started in the cause of solving issue [facebook/react-native#854](https://github.com/facebook/react-native/issues/854), React Native's lacks of `Blob` implementation which results into problems when transferring binary data. - -It is committed to making file access and transfer easier and more efficient for React Native developers. We've implemented highly customizable filesystem and network module which plays well together. For example, developers can upload and download data directly from/to storage, which is more efficient, especially for large files. The file system supports file stream, so you don't have to worry about OOM problem when accessing large files. - -In `0.8.0` we introduced experimental Web API polyfills that make it possible to use browser-based libraries in React Native, such as, [FireBase JS SDK](https://github.com/wkh237/rn-firebase-storage-upload-sample) - - -## Installation - -Install package from npm - -```sh -npm install --save react-native-fetch-blob -``` - -Or if using CocoaPods, add the pod to your `Podfile` - -``` -pod 'react-native-fetch-blob', - :path => '../node_modules/react-native-fetch-blob' -``` - -After `0.10.3` you can install this package directly from Github - -```sh -# replace with any one of the branches -npm install --save github:wkh237/react-native-fetch-blob-package# -``` -**Automatically Link Native Modules** - -For 0.29.2+ projects, simply link native packages via the following command (note: rnpm has been merged into react-native) - -``` -react-native link -``` - -As for projects < 0.29 you need `rnpm` to link native packages - -```sh -rnpm link -``` - -Optionally, use the following command to add Android permissions to `AndroidManifest.xml` automatically - -```sh -RNFB_ANDROID_PERMISSIONS=true react-native link -``` - -pre 0.29 projects - -```sh -RNFB_ANDROID_PERMISSIONS=true rnpm link -``` - -The link script might not take effect if you have non-default project structure, please visit [the wiki](https://github.com/wkh237/react-native-fetch-blob/wiki/Manually-Link-Package) to link the package manually. - -**Grant Permission to External storage for Android 5.0 or lower** - -The mechanism for granting Android permissions has slightly different since Android 6.0 released, please refer to [Official Document](https://developer.android.com/training/permissions/requesting.html). - -If you're going to access external storage (say, SD card storage) for `Android 5.0` (or lower) devices, you might have to add the following line to `AndroidManifest.xml`. - -```diff - - - - -+ -+ - - ... - -``` - -Also, if you're going to use `Android Download Manager` you have to add this to `AndroidManifest.xml` - -```diff - - - -+ - -``` - -**Grant Access Permission for Android 6.0** - -Beginning in Android 6.0 (API level 23), users grant permissions to apps while the app is running, not when they install the app. So adding permissions in `AndroidManifest.xml` won't work for Android 6.0+ devices. To grant permissions in runtime, you might use [PermissionAndroid API](https://facebook.github.io/react-native/docs/permissionsandroid.html). - -## Usage - -ES6 - -The module uses ES6 style export statement, simply use `import` to load the module. - -```js -import RNFetchBlob from 'react-native-fetch-blob' -``` - -ES5 - -If you're using ES5 require statement to load the module, please add `default`. See [here](https://github.com/wkh237/react-native-fetch-blob/wiki/Trouble-Shooting#rnfetchblobfetch-is-not-a-function) for more detail. - -``` -var RNFetchBlob = require('react-native-fetch-blob').default -``` - -## HTTP Data Transfer - - -### Regular Request - -After `0.8.0` react-native-fetch-blob automatically decides how to send the body by checking its type and `Content-Type` in the header. The rule is described in the following diagram - - - -To sum up: - -- To send a form data, the `Content-Type` header does not matter. When the body is an `Array` we will set proper content type for you. -- To send binary data, you have two choices, use BASE64 encoded string or path points to a file contains the body. - - If the `Content-Type` containing substring`;BASE64` or `application/octet` the given body will be considered as a BASE64 encoded data which will be decoded to binary data as the request body. - - Otherwise, if a string starts with `RNFetchBlob-file://` (which can simply be done by `RNFetchBlob.wrap(PATH_TO_THE_FILE)`), it will try to find the data from the URI string after `RNFetchBlob-file://` and use it as the request body. -- To send the body as-is, simply use a `Content-Type` header not containing `;BASE64` or `application/octet`. - -> It is Worth to mentioning that the HTTP request uses cache by default, if you're going to disable it simply add a Cache-Control header `'Cache-Control' : 'no-store'` - -> After 0.9.4, we disabled `Chunked` transfer encoding by default, if you're going to use it, you should explicitly set header `Transfer-Encoding` to `Chunked`. - -### Download example: Fetch files that need authorization token - -Most simple way is download to memory and stored as BASE64 encoded string, this is handy when the response data is small. - -```js - -// send http request in a new thread (using native code) -RNFetchBlob.fetch('GET', 'http://www.example.com/images/img1.png', { - Authorization : 'Bearer access-token...', - // more headers .. - }) - // when response status code is 200 - .then((res) => { - // the conversion is done in native code - let base64Str = res.base64() - // the following conversions are done in js, it's SYNC - let text = res.text() - let json = res.json() - - }) - // Status code is not 200 - .catch((errorMessage, statusCode) => { - // error handling - }) -``` - -### Download to storage directly - -If the response data is large, that would be a bad idea to convert it into BASE64 string. A better solution is streaming the response directly into a file, simply add a `fileCache` option to config, and set it to `true`. This will make incoming response data stored in a temporary path **without** any file extension. - -**These files won't be removed automatically, please refer to [Cache File Management](#user-content-cache-file-management)** - -```js -RNFetchBlob - .config({ - // add this option that makes response data to be stored as a file, - // this is much more performant. - fileCache : true, - }) - .fetch('GET', 'http://www.example.com/file/example.zip', { - //some headers .. - }) - .then((res) => { - // the temp file path - console.log('The file saved to ', res.path()) - }) -``` - -**Set Temp File Extension** - -Sometimes you might need a file extension for some reason. For example, when using file path as the source of `Image` component, the path should end with something like .png or .jpg, you can do this by add `appendExt` option to `config`. - -```js -RNFetchBlob - .config({ - fileCache : true, - // by adding this option, the temp files will have a file extension - appendExt : 'png' - }) - .fetch('GET', 'http://www.example.com/file/example.zip', { - //some headers .. - }) - .then((res) => { - // the temp file path with file extension `png` - console.log('The file saved to ', res.path()) - // Beware that when using a file path as Image source on Android, - // you must prepend "file://"" before the file path - imageView = - }) -``` - -**Use Specific File Path** - -If you prefer a particular file path rather than randomly generated one, you can use `path` option. We've added [several constants](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#dirs) in v0.5.0 which represents commonly used directories. - -```js -let dirs = RNFetchBlob.fs.dirs -RNFetchBlob -.config({ - // response data will be saved to this path if it has access right. - path : dirs.DocumentDir + '/path-to-file.anything' -}) -.fetch('GET', 'http://www.example.com/file/example.zip', { - //some headers .. -}) -.then((res) => { - // the path should be dirs.DocumentDir + 'path-to-file.anything' - console.log('The file saved to ', res.path()) -}) -``` - -**These files won't be removed automatically, please refer to [Cache File Management](#user-content-cache-file-management)** - -#### Upload example : Dropbox [files-upload](https://www.dropbox.com/developers/documentation/http/documentation#files-upload) API - -`react-native-fetch-blob` will convert the base64 string in `body` to binary format using native API, this process is done in a separated thread so that it won't block your GUI. - -```js - -RNFetchBlob.fetch('POST', 'https://content.dropboxapi.com/2/files/upload', { - Authorization : "Bearer access-token...", - 'Dropbox-API-Arg': JSON.stringify({ - path : '/img-from-react-native.png', - mode : 'add', - autorename : true, - mute : false - }), - 'Content-Type' : 'application/octet-stream', - // here's the body you're going to send, should be a BASE64 encoded string - // (you can use "base64"(refer to the library 'mathiasbynens/base64') APIs to make one). - // The data will be converted to "byte array"(say, blob) before request sent. - }, base64ImageString) - .then((res) => { - console.log(res.text()) - }) - .catch((err) => { - // error handling .. - }) -``` - -### Upload a file from storage - -If you're going to use a `file` as request body, just wrap the path with `wrap` API. - -```js -RNFetchBlob.fetch('POST', 'https://content.dropboxapi.com/2/files/upload', { - // dropbox upload headers - Authorization : "Bearer access-token...", - 'Dropbox-API-Arg': JSON.stringify({ - path : '/img-from-react-native.png', - mode : 'add', - autorename : true, - mute : false - }), - 'Content-Type' : 'application/octet-stream', - // Change BASE64 encoded data to a file path with prefix `RNFetchBlob-file://`. - // Or simply wrap the file path with RNFetchBlob.wrap(). - }, RNFetchBlob.wrap(PATH_TO_THE_FILE)) - .then((res) => { - console.log(res.text()) - }) - .catch((err) => { - // error handling .. - }) -``` - -### Multipart/form-data example: Post form data with file and data - -In `version >= 0.3.0` you can also post files with form data, just put an array in `body`, with elements have property `name`, `data`, and `filename`(optional). - -Elements have property `filename` will be transformed into binary format, otherwise, it turns into utf8 string. - -```js - - RNFetchBlob.fetch('POST', 'http://www.example.com/upload-form', { - Authorization : "Bearer access-token", - otherHeader : "foo", - 'Content-Type' : 'multipart/form-data', - }, [ - // element with property `filename` will be transformed into `file` in form data - { name : 'avatar', filename : 'avatar.png', data: binaryDataInBase64}, - // custom content type - { name : 'avatar-png', filename : 'avatar-png.png', type:'image/png', data: binaryDataInBase64}, - // part file from storage - { name : 'avatar-foo', filename : 'avatar-foo.png', type:'image/foo', data: RNFetchBlob.wrap(path_to_a_file)}, - // elements without property `filename` will be sent as plain text - { name : 'name', data : 'user'}, - { name : 'info', data : JSON.stringify({ - mail : 'example@example.com', - tel : '12345678' - })}, - ]).then((resp) => { - // ... - }).catch((err) => { - // ... - }) -``` - -What if you want to append a file to form data? Just like [upload a file from storage](#user-content-upload-a-file-from-storage) example, wrap `data` by `wrap` API (this feature is only available for `version >= v0.5.0`). On version >= `0.6.2`, it is possible to set custom MIME type when appending a file to form data. But keep in mind when the file is large it's likely to crash your app. Please consider use other strategy (see [#94](https://github.com/wkh237/react-native-fetch-blob/issues/94)). - -```js - - RNFetchBlob.fetch('POST', 'http://www.example.com/upload-form', { - Authorization : "Bearer access-token", - otherHeader : "foo", - // this is required, otherwise it won't be process as a multipart/form-data request - 'Content-Type' : 'multipart/form-data', - }, [ - // append field data from file path - { - name : 'avatar', - filename : 'avatar.png', - // Change BASE64 encoded data to a file path with prefix `RNFetchBlob-file://`. - // Or simply wrap the file path with RNFetchBlob.wrap(). - data: RNFetchBlob.wrap(PATH_TO_THE_FILE) - }, - { - name : 'ringtone', - filename : 'ring.mp3', - // use custom MIME type - type : 'application/mp3', - // upload a file from asset is also possible in version >= 0.6.2 - data : RNFetchBlob.wrap(RNFetchBlob.fs.asset('default-ringtone.mp3')) - } - // elements without property `filename` will be sent as plain text - { name : 'name', data : 'user'}, - { name : 'info', data : JSON.stringify({ - mail : 'example@example.com', - tel : '12345678' - })}, - ]).then((resp) => { - // ... - }).catch((err) => { - // ... - }) -``` - -### Upload/Download progress - -In `version >= 0.4.2` it is possible to know the upload/download progress. After `0.7.0` IOS and Android upload progress are also supported. - -```js - RNFetchBlob.fetch('POST', 'http://www.example.com/upload', { - //... some headers, - 'Content-Type' : 'octet-stream' - }, base64DataString) - // listen to upload progress event - .uploadProgress((written, total) => { - console.log('uploaded', written / total) - }) - // listen to download progress event - .progress((received, total) => { - console.log('progress', received / total) - }) - .then((resp) => { - // ... - }) - .catch((err) => { - // ... - }) -``` - -In `0.9.6`, you can specify an object as the first argument which contains `count` and `interval`, to the frequency of progress event (this will be done in the native context a reduce RCT bridge overhead). Notice that `count` argument will not work if the server does not provide response content length. - - -```js - RNFetchBlob.fetch('POST', 'http://www.example.com/upload', { - //... some headers, - 'Content-Type' : 'octet-stream' - }, base64DataString) - // listen to upload progress event, emit every 250ms - .uploadProgress({ interval : 250 },(written, total) => { - console.log('uploaded', written / total) - }) - // listen to download progress event, every 10% - .progress({ count : 10 }, (received, total) => { - console.log('progress', received / total) - }) - .then((resp) => { - // ... - }) - .catch((err) => { - // ... - }) -``` - -### Cancel Request - -After `0.7.0` it is possible to cancel an HTTP request. Upon cancellation, it throws a promise rejection, be sure to catch it. - -```js -let task = RNFetchBlob.fetch('GET', 'http://example.com/file/1') - -task.then(() => { ... }) - // handle request cancelled rejection - .catch((err) => { - console.log(err) - }) -// cancel the request, the callback function is optional -task.cancel((err) => { ... }) - -``` - -### Drop-in Fetch Replacement - -0.9.0 - -If you have existing code that uses `whatwg-fetch`(the official **fetch**), it's not necessary to replace them with `RNFetchblob.fetch`, you can simply use our **Fetch Replacement**. The difference between Official them is official fetch uses [whatwg-fetch](https://github.com/github/fetch) which wraps XMLHttpRequest polyfill under the hood. It's a great library for web developers, but does not play very well with RN. Our implementation is simply a wrapper of our `fetch` and `fs` APIs, so you can access all the features we provided. - -[See document and examples](https://github.com/wkh237/react-native-fetch-blob/wiki/Fetch-API#fetch-replacement) - -### Android Media Scanner, and Download Manager Support - -If you want to make a file in `External Storage` becomes visible in Picture, Downloads, or other built-in apps, you will have to use `Media Scanner` or `Download Manager`. - -**Media Scanner** - -Media scanner scans the file and categorizes by given MIME type, if MIME type not specified, it will try to resolve the file using its file extension. - -```js - -RNFetchBlob - .config({ - // DCIMDir is in external storage - path : dirs.DCIMDir + '/music.mp3' - }) - .fetch('GET', 'http://example.com/music.mp3') - .then((res) => RNFetchBlob.fs.scanFile([ { path : res.path(), mime : 'audio/mpeg' } ])) - .then(() => { - // scan file success - }) - .catch((err) => { - // scan file error - }) -``` - -**Download Manager** - -When downloading large files on Android it is recommended to use `Download Manager`, it supports a lot of native features like the progress bar, and notification, also the download task will be handled by OS, and more efficient. - - - -When using DownloadManager, `fileCache` and `path` properties in `config` will not take effect, because Android DownloadManager can only store files to external storage, also notice that Download Manager can only support `GET` method, which means the request body will be ignored. - -When download complete, DownloadManager will generate a file path so that you can deal with it. - -```js -RNFetchBlob - .config({ - addAndroidDownloads : { - useDownloadManager : true, // <-- this is the only thing required - // Optional, override notification setting (default to true) - notification : false, - // Optional, but recommended since android DownloadManager will fail when - // the url does not contains a file extension, by default the mime type will be text/plain - mime : 'text/plain', - description : 'File downloaded by download manager.' - } - }) - .fetch('GET', 'http://example.com/file/somefile') - .then((resp) => { - // the path of downloaded file - resp.path() - }) -``` - -Your app might not have right to remove/change the file created by Download Manager, therefore you might need to [set custom location to the download task](https://github.com/wkh237/react-native-fetch-blob/issues/236). - -**Download Notification and Visibility in Download App (Android Only)** - - - - - -If you need to display a notification upon the file is downloaded to storage (as the above) or make the downloaded file visible in "Downloads" app. You have to add some options to `config`. - -```js -RNFetchBlob.config({ - fileCache : true, - // android only options, these options be a no-op on IOS - addAndroidDownloads : { - // Show notification when response data transmitted - notification : true, - // Title of download notification - title : 'Great ! Download Success ! :O ', - // File description (not notification description) - description : 'An image file.', - mime : 'image/png', - // Make the file scannable by media scanner - mediaScannable : true, - } -}) -.fetch('GET', 'http://example.com/image1.png') -.then(...) -``` - -**Open Downloaded File with Intent** - -This is a new feature added in `0.9.0` if you're going to open a file path using official [Linking](https://facebook.github.io/react-native/docs/linking.html) API that might not work as expected, also, if you're going to install an APK in `Downloads` app, that will not function too. As an alternative, you can try `actionViewIntent` API, which will send an ACTION_VIEW intent for you which uses the given `MIME` type. - -Download and install an APK programmatically - -```js - -const android = RNFetchBlob.android - -RNFetchBlob.config({ - addAndroidDownloads : { - useDownloadManager : true, - title : 'awesome.apk', - description : 'An APK that will be installed', - mime : 'application/vnd.android.package-archive', - mediaScannable : true, - notification : true, - } - }) - .fetch('GET', `http://www.example.com/awesome.apk`) - .then((res) => { - android.actionViewIntent(res.path(), 'application/vnd.android.package-archive') - }) -``` - -Or show an image in image viewer - -```js - android.actionViewIntent(PATH_OF_IMG, 'image/png') -``` - -## File System - -### File Access - -File access APIs were made when developing `v0.5.0`, which helping us write tests, and was not planned to be a part of this module. However, we realized that it's hard to find a great solution to manage cached files, everyone who uses this module may need these APIs for their cases. - -Before start using file APIs, we recommend read [Differences between File Source](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#differences-between-file-source) first. - -File Access APIs -- [asset (0.6.2)](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#assetfilenamestringstring) -- [dirs](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#dirs) -- [createFile](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#createfilepath-data-encodingpromise) -- [writeFile (0.6.0)](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#writefilepathstring-contentstring--array-encodingstring-appendbooleanpromise) -- [appendFile (0.6.0) ](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#appendfilepathstring-contentstring--array-encodingstringpromise) -- [readFile (0.6.0)](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#readfilepath-encodingpromise) -- [readStream](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#readstreampath-encoding-buffersizepromise) -- [writeStream](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#writestreampathstring-encodingstring-appendbooleanpromise) -- [unlink](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#unlinkpathstringpromise) -- [mkdir](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#mkdirpathstringpromise) -- [ls](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#lspathstringpromise) -- [mv](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#mvfromstring-tostringpromise) -- [cp](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#cpsrcstring-deststringpromise) -- [exists](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#existspathstringpromise) -- [isDir](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#isdirpathstringpromise) -- [stat](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#statpathstringpromise) -- [lstat](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#lstatpathstringpromise) -- [scanFile (Android only)](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API#scanfilepathstringpromise-androi-only) - -See [File API](https://github.com/wkh237/react-native-fetch-blob/wiki/File-System-Access-API) for more information - -### File Stream - -In `v0.5.0` we've added `writeStream` and `readStream`, which allows your app read/write data from the file path. This API creates a file stream, rather than convert entire data into BASE64 encoded string. It's handy when processing **large files**. - -When calling `readStream` method, you have to `open` the stream, and start to read data. When the file is large, consider using an appropriate `bufferSize` and `interval` to reduce the native event dispatching overhead (see [Performance Tips](#user-content-performance-tips)) - -> The file stream event has a default throttle(10ms) and buffer size which preventing it cause too much overhead to main thread, yo can also [tweak these values](#user-content-performance-tips). - -```js -let data = '' -RNFetchBlob.fs.readStream( - // file path - PATH_TO_THE_FILE, - // encoding, should be one of `base64`, `utf8`, `ascii` - 'base64', - // (optional) buffer size, default to 4096 (4095 for BASE64 encoded data) - // when reading file in BASE64 encoding, buffer size must be multiples of 3. - 4095) -.then((ifstream) => { - ifstream.open() - ifstream.onData((chunk) => { - // when encoding is `ascii`, chunk will be an array contains numbers - // otherwise it will be a string - data += chunk - }) - ifstream.onError((err) => { - console.log('oops', err) - }) - ifstream.onEnd(() => { - - }) -}) -``` - -When using `writeStream`, the stream object becomes writable, and you can then perform operations like `write` and `close`. - -```js -RNFetchBlob.fs.writeStream( - PATH_TO_FILE, - // encoding, should be one of `base64`, `utf8`, `ascii` - 'utf8', - // should data append to existing content ? - true) -.then((ofstream) => { - ofstream.write('foo') - ofstream.write('bar') - ofstream.close() -}) - -``` - -### Cache File Management - -When using `fileCache` or `path` options along with `fetch` API, response data will automatically store into the file system. The files will **NOT** removed unless you `unlink` it. There're several ways to remove the files - -```js - - // remove file using RNFetchblobResponse.flush() object method - RNFetchblob.config({ - fileCache : true - }) - .fetch('GET', 'http://example.com/download/file') - .then((res) => { - // remove cached file from storage - res.flush() - }) - - // remove file by specifying a path - RNFetchBlob.fs.unlink('some-file-path').then(() => { - // ... - }) - -``` - -You can also group requests by using `session` API and use `dispose` to remove them all when needed. - -```js - - RNFetchblob.config({ - fileCache : true - }) - .fetch('GET', 'http://example.com/download/file') - .then((res) => { - // set session of a response - res.session('foo') - }) - - RNFetchblob.config({ - // you can also set session beforehand - session : 'foo' - fileCache : true - }) - .fetch('GET', 'http://example.com/download/file') - .then((res) => { - // ... - }) - - // or put an existing file path to the session - RNFetchBlob.session('foo').add('some-file-path') - // remove a file path from the session - RNFetchBlob.session('foo').remove('some-file-path') - // list paths of a session - RNFetchBlob.session('foo').list() - // remove all files in a session - RNFetchBlob.session('foo').dispose().then(() => { ... }) - -``` - -### Transfer Encoding - -After `0.9.4`, the `Chunked` transfer encoding is disabled by default due to some service provider may not support chunked transfer. To enable it, set `Transfer-Encoding` header to `Chunked`. - -```js -RNFetchBlob.fetch('POST', 'http://example.com/upload', { 'Transfer-Encoding' : 'Chunked' }, bodyData) -``` - -### Self-Signed SSL Server - -By default, react-native-fetch-blob does NOT allow connection to unknown certification provider since it's dangerous. To connect a server with self-signed certification, you need to add `trusty` to `config` explicitly. This function is available for version >= `0.5.3` - -```js -RNFetchBlob.config({ - trusty : true -}) -.then('GET', 'https://mysite.com') -.then((resp) => { - // ... -}) -``` - -## Web API Polyfills - -After `0.8.0` we've made some [Web API polyfills](https://github.com/wkh237/react-native-fetch-blob/wiki/Web-API-Polyfills-(experimental)) that makes some browser-based library available in RN. - -- Blob -- XMLHttpRequest (Use our implementation if you're going to use it with Blob) - -Here's a [sample app](https://github.com/wkh237/rn-firebase-storage-upload-sample) that uses polyfills to upload files to FireBase. - -## Performance Tips - -**Read Stream and Progress Event Overhead** - -If the process seems to block JS thread when file is large when reading data via `fs.readStream`. It might because the default buffer size is quite small (4kb) which result in a lot of events triggered from JS thread. Try to increase the buffer size (for example 100kb = 102400) and set a larger interval (available for 0.9.4+, the default value is 10ms) to limit the frequency. - -**Reduce RCT Bridge and BASE64 Overhead** - -React Native connects JS and Native context by passing JSON around React Native bridge, and there will be an overhead to convert data before they sent to each side. When data is large, this will be quite a performance impact to your app. It's recommended to use file storage instead of BASE64 if possible.The following chart shows how much faster when loading data from storage than BASE64 encoded string on iPhone 6. - - - -**ASCII Encoding has /terrible Performance** - -Due to the [lack of typed array implementation in JavascriptCore, and limitation of React Native structure](https://github.com/facebook/react-native/issues/1424), to convert data to JS byte array spends lot of time. Use it only when needed, the following chart shows how much time it takes when reading a file with different encoding. - - - -**Concat and Replacing Files** - -If you're going to concatenate files, you don't have to read the data to JS context anymore! In `0.8.0` we introduced new encoding `uri` for writeFile and appendFile API, which make it possible to handle the whole process in native. - - - -## Caveats - -* This library does not urlencode unicode characters in URL automatically, see [#146](https://github.com/wkh237/react-native-fetch-blob/issues/146). -* When you create a `Blob` , from an existing file, the file **WILL BE REMOVED** if you `close` the blob. -* If you replaced `window.XMLHttpRequest` for some reason (e.g. make Firebase SDK work), it will also affect how official `fetch` works (basically it should work just fine). -* When file stream and upload/download progress event slow down your app, consider an upgrade to `0.9.6+`, use [additional arguments](https://github.com/wkh237/react-native-fetch-blob/wiki/Fetch-API#fetchprogressconfig-eventlistenerpromisernfetchblobresponse) to limit its frequency. -* When passing a file path to the library, remove `file://` prefix. - -when you got a problem, have a look at [Trouble Shooting](https://github.com/wkh237/react-native-fetch-blob/wiki/Trouble-Shooting) or [issues labeled Trouble Shooting](https://github.com/wkh237/react-native-fetch-blob/issues?utf8=✓&q=label:%22trouble%20shooting%22%20), there'd be some helpful information. - -## Changes - -See [release notes](https://github.com/wkh237/react-native-fetch-blob/releases) - -### Development - -If you're interested in hacking this module, check our [development guide](https://github.com/wkh237/react-native-fetch-blob/wiki/Home), there might be some helpful information. -Please feel free to make a PR or file an issue. +Posted by https://github.com/lll000111/ ("Collaborator" in this repo) on 22 March, 2018 From 1fb974fc531fe93f7641b2f62a077bf6ed12a28f Mon Sep 17 00:00:00 2001 From: KittenWithHerbs Date: Fri, 23 Mar 2018 00:00:22 +0100 Subject: [PATCH 17/18] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 31bb6c652..bf0e3c458 100644 --- a/README.md +++ b/README.md @@ -10,4 +10,4 @@ That means issues and PRs should be posted there. --- -Posted by https://github.com/lll000111/ ("Collaborator" in this repo) on 22 March, 2018 +Posted by [@lll000111](https://github.com/lll000111/) ("Collaborator" in this repo) on 22 March, 2018 From a6c5ad11581290acf3a32e8412212ae6ab4be4d3 Mon Sep 17 00:00:00 2001 From: Eddie Date: Fri, 3 Aug 2018 18:52:05 -0500 Subject: [PATCH 18/18] Fix iOS Yellow box warning "requires main queue setup" Fix iOS Yellow box warning "requires main queue setup" since it overrides constantsToExport but doesn't implement requiresMainQueueSetup Add: ```` + (BOOL)requiresMainQueueSetup { return NO; } ```` --- ios/RNFetchBlob/RNFetchBlob.m | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ios/RNFetchBlob/RNFetchBlob.m b/ios/RNFetchBlob/RNFetchBlob.m index 246d6707c..be4011ce2 100644 --- a/ios/RNFetchBlob/RNFetchBlob.m +++ b/ios/RNFetchBlob/RNFetchBlob.m @@ -36,6 +36,11 @@ - (dispatch_queue_t) methodQueue { return commonTaskQueue; } ++ (BOOL)requiresMainQueueSetup +{ + return NO; +} + + (RCTBridge *)getRCTBridge { RCTRootView * rootView = [[UIApplication sharedApplication] keyWindow].rootViewController.view;