-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Sentry returns 400 with the "premature end of input at line x column y" response #8739
Comments
Hi, can you share the payload that was attempted to be sent? Thanks! |
Request Payload: {"event_id":"f782814af21d4b3abe25868755c87ba4","sent_at":"2023-08-04T10:39:01.445","sdk":{"name":"sentry.javascript.react","version":"7.61.0"},"trace":{"environment":"production","public_key":"MY_PUBLIC_KEY","trace_id":"2557cd1435ad48899a70f6231bede4c9"}} Thanks. |
Ok seems like there is a |
I have a feeling that this is not on the SDK since many many people would report this and we would be missing a lot of events. |
Hello, thanks for your investigation. We override the toISOString method to return "YYYY-MM-DDTHH:mm:ss.SSS" and many teams in our company use this method. So we can't take it back. :( Thanks :) |
@YusufZiya since I also don't think it is worth it for us to add a way to configure the |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
7.61.0
Framework Version
React 18.2.0
Link to Sentry event
No response
SDK Setup
Sentry.init({
dsn: "MY_DSN",
maxBreadcrumbs: 50,
debug: true,
});
Steps to Reproduce
I tried to integrate sentry to my existing react project which is generated via CRA. I added a button click handler in order to generate an error.
const foo = {};
foo.bar();
Sentry caught the error but when it sent to the server it responded like that.
{
"detail": "invalid event envelope",
"causes": [
"invalid envelope header",
"premature end of input at line 1 column 82"
]
}
Expected Result
Return 200
Actual Result
Http status code: 400
Response:
{
"detail": "invalid event envelope",
"causes": [
"invalid envelope header",
"premature end of input at line 1 column 82"
]
}
The text was updated successfully, but these errors were encountered: