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
I have a bit of a weird one and I'm trying to figure it out. I've built on this in a react-native project, they use this polyfill.
I make a JSON request and have a body returned, every other request returns the correct (it's to my own server running a rails app) .json() object, but in this returned object I have the following logs:
I've been scratching my head for a few days, I know it's probably a configuration error on a server somewhere but the content types seem to be okay and the headers seem to be okay, I just can't for the life of me figure out what I've done wrong. If this is the wrong project happy to jump down the stack, just haven't seen anyone reporting anything like this before :)
The text was updated successfully, but these errors were encountered:
It's important that you do not use _bodyText property. The leading underscore indicates that this property is internal to our polyfill and not part of the fetch API. In fact, your code that users our internal property won't work in browsers that have native fetch implementations, such as Chrome and Firefox.
I have a bit of a weird one and I'm trying to figure it out. I've built on this in a react-native project, they use this polyfill.
I make a JSON request and have a body returned, every other request returns the correct (it's to my own server running a rails app) .json() object, but in this returned object I have the following logs:
Full Response Object:
But if I call data.json()
But if I call data._bodyText:
I've been scratching my head for a few days, I know it's probably a configuration error on a server somewhere but the content types seem to be okay and the headers seem to be okay, I just can't for the life of me figure out what I've done wrong. If this is the wrong project happy to jump down the stack, just haven't seen anyone reporting anything like this before :)
The text was updated successfully, but these errors were encountered: