Trouble Shooting
- Firebase login and other API calls no response after replace the XMLHttpRequest
- version 0.7.0+ does not work with react-native 0.27 (Android)
- App crash on start (Android)
- RNFetchBlob.fetch is not a function
- Unknown type name 'namespace' (IOS)
- Could not send any HTTP request except localhost (IOS)
- Could not compile on IOS
- Undefined is not an object (evaluating 'RNFetchBlob.DocumentDir')
- How to access files from assets
- fs.readStream is freezing JS thread
On 0.7.5, we have fixed Android OkHttp dependency issue on pre 0.28 projects excepted 0.27, 0.29.0, and 0.29.1. For 0.29.0 and 0.29.1 it's because rnpm link is broken in these versions, you may need to manually link Android package. It is recommended to upgrade you project if possible
$ react-native upgrade
After the project upgraded, run rnpm link again.
This might because rnpm added multiple new RNFetchBlobPacket() to your MainApplication.java, the error message may looks like
java.lang.RuntimeException: Unable to start activity ComponentInfo ...
Try to remove duplicated new RNFetchBlobPacket() in MainApplication.java
This usually means that you're using ES5, you use require('react-native-fetch-blob') instead of import RNFetchBlob from 'react-native-fetch-blob'. There's a very very good explanation on StackOverflow
The issue is you are using ES5 style require statements with a library written against ES6/ES2015. You have two options:
ES5:
var RNFetchBlob = require('react-native-fetch-blob').default
ES6:
import RNFetchBlob from 'react-native-fetch-blob'
by rmevans9@StackOverflow
This usually happens when the RNFetchBlob deployment target version is incorrect, it is fixed in 0.7.1, you may upgrade your package to 0.7.1 or manually fix it by following steps
Open .xcodeproj of your app and open the Libraries folder in left side tree view
Find project -> RNFetchBlob, click on it
Change the deployment target to 7.0
Rebuild the project again
reference from official document
App Transport Security is a security feature, added in iOS 9, that rejects all HTTP requests that are not sent over HTTPS. This can result in HTTP traffic being blocked, including the developer React Native server.
ATS is disabled by default in projects generated using the React Native CLI in order to make development easier. You should re-enable ATS prior to building your app for production by removing the NSAllowsArbitraryLoads entry from your Info.plist file in the ios/ folder.
To learn more about how to configure ATS on your own Xcode projects, see this post on ATS.
If you're having problem when compiling IOS project, and the error looks like
ARC forbids synthesizing a property of an Objective-C ..
You should try to upgrade Xcode to version >= 7.3 or upgrade react-native-fetch-blob to latest version, because we have already solved this problem.
see also #31
Error messages like XXX is undefined, could not found RNFetchBlob ... usually because the package does not properly installed, there're some closed issues about installation problems #51, #12, #30
After 0.6.2 you can access files inside app bundle by simply adding the prefix bundle-assets:// before the filename. You can also wrap the filename by fs.asset API. For example, upload a file from assets
RNFetchBlob
.fetch('POST', 'http://myupload.com/upload',
{ 'Content-Type' : 'application/octet-stream' },
RNFetchBlob.wrap(RNFetchBlob.fs.asset('my-asset.png')))
.then((resp) => { ... })Generally you can access the file as usual once you wrap the file name by fs.asset, but keep in mind, assets files are readonly, so you are not be able to remove, or change them.
By default, readStream uses a very small buffer (4kb), when the file is large, the onData events will likely becomes heavy overhead to JS thread, the solution is increase the bufferSize to reduce the amount of event, but keep in mind if the buffer size is too large (greater than heap limit), it will crash the app. For more discussion see #118.
This is caused by incorrect implementation in XMLHttpRequest polyfill, we've fixed this issue in 0.9.6-beta.2, it should be fixed after you upgrade the package.