Android: Response info is missing information.
See original GitHub issuereact-native: 0.57.8 rn-fetch-blob: 0.10.15
Sometimes response.info()
object is missing a lot of properties. It only returns { 'rnfbEncode' : 'utf8' }
and doesn’t include anything else.
Digging a little deeper it seems that RNFetchBlobState
event is not emitted to JS and this code is not run https://github.com/joltup/rn-fetch-blob/blob/master/index.js#L249
It seems to happen a lot more in release builds. It could be that https://github.com/joltup/rn-fetch-blob/blob/master/index.js#L291 is being called before the event is received
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:7
Top Results From Across the Web
Data missing in multiple View in RecyclerView using retrofit ...
I am facing an issue in multiple view type recycler view i think the code in myadapter is lacking something which i am...
Read more >Get help during an emergency with your Android phone
On your phone, open the Safety app . Sign in to your Google Account. Tap Settings . Add your emergency info. For Medical...
Read more >move data from android missing - Apple Community
While you set up your new iOS device, look for the Apps & Data screen. Then tap Move Data from Android. ( If...
Read more >Troubleshoot known issues with Android Emulator
This page lists known issues, workarounds, and troubleshooting tips for the Android Emulator. If you encounter an issue not listed here or ...
Read more >TelephonyManager
Provides access to information about the telephony services on the device. ... data). Returns the response of authentication for the default subscription.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In my case, this problem happens when using RNFetchBlob and react-native-threads. response in RNFetchBlob will be without headers.
Got the same problem, RNThreads is catching the messages from RNFetchBlob. Ended up by removing RNFetchBlob from
packages.add(new RNThreadPackage(...))