-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React Native: Does not send exceptions at all #526
Comments
Interestingly I just ran across this same issue. |
There's a broader issue here, I think, at least in 0.22. I now have to explicitly supply a Content-type header to fetch(), at least in dev mode, when I did not have to previously and don't have to iOS. |
That's already fixed (not sure if pushed), check recent pull requests :) |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a side note - we should really improve the way we call onError callbacks - without original error or at least request response it's really hard.
Anyway, after putting console.log inside
request.onreadystatechange
in react-native plugin, I've seen all requests on Android fail with statusCode: 0 and body: "Payload is set but no content-type header specified".Simply adding:
fixed the issue and errors started appearing in dashboard immediately.
It seems to me like it's a RN change as it used to work last week before upgrade.
The text was updated successfully, but these errors were encountered: