-
-
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
Replay tunnel fails due to empty envelope #13453
Comments
Hello, thanks for writing in. The envelopes should not be empty for replays. You could add a guard to exit out early if Please set |
Yes the body of the request is there so I'm not sure why I can't get anything out of it on the server side. Client side debug: https://gist.github.com/johnathanludwig/1bcefb76f2609a2b44eb3820dbdea26e Server side:
|
Could you please amend the server side debug log with the logs that occur on app startup? Also, does this happen if you disable compression?
|
Disabling compression does resolve the issue. Thank you for the help with that. Here are the server startup logs when compression was still enabled:
|
Right, so For now, I suggest to either turn compression off or adapt your tunnel route to deal with the compressed data. Here's an example from our integration tests. |
Great, thanks for the help! |
Let's keep this open, I added it to our backlog so we can work on it. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/sveltekit
SDK Version
8.26.0
Framework Version
Sveltekit 2.5.18
Link to Sentry event
No response
Reproduction Example/SDK Setup
Using the example provided from the documentation does not work with replay requests. The docs show using an array buffer. This works well with traces, however for replays the code error on parsing
piece
. In this case theenvelopeBytes
is 0 andenvelope
empty.https://docs.sentry.io/platforms/javascript/troubleshooting/#dealing-with-ad-blockers
Steps to Reproduce
/api/errors/+server.ts
./api/errors
.Expected Result
The replays get sent to sentry successfully.
Actual Result
Traces are tunneled. Replays result in this error:
The text was updated successfully, but these errors were encountered: