You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This shows that contrary to other responses the __didReceiveNetworkData method is never called, which is why this._nativeResponse remains undefined, hence the error.
Workaround
I found that I can work around the issue by passing the extra reactNative: { textStreaming: true } options to the fetch function:
Currently having the issue on production env with expo-notification. since their fetch is based on built-in one, they don't pass the reactNative: { textStreaming: true }, which generate the blobId error on getExpoPushTokenAsync
blobId error is on Ios only,
on android we get a different error msg but the issue is the same.
When performing a "DEL" request to a server which responds with an HTTP "204 No Content" response, I get the following error:
This is a JSON dump of the symbolicated stack:
Debugging
I removed the comments from some methods in
Fetch.js
to reveal this:This shows that contrary to other responses the
__didReceiveNetworkData
method is never called, which is whythis._nativeResponse
remainsundefined
, hence the error.Workaround
I found that I can work around the issue by passing the extra
reactNative: { textStreaming: true }
options to the fetch function:The text was updated successfully, but these errors were encountered: