-
-
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
Manual replays are longer than recording #13791
Comments
Hey, so I can reproduce this (example) myself in a test app. I think this is happening because of some replay breadcrumbs we emit. which are happening after the page initially loads: @c298lee gonna tag you since you looked recently into replay web vital breadcrumbs: Any chance that there is a problem with us collecting/buffering breadcrumbs if there's no active replay (but |
Here's my reproduction app btw. It's basically just the example from the issue description pasted into a Vite React 17 app: https://github.com/Lms24/gh-sentry-javascript-13791-replay-manual-start-stop |
Looks like it's the same issue as this one: https://github.com/getsentry/team-replay/issues/451. |
This is happening due to buffered events happening at an earlier timestamp (including web vitals) being added to the replay. We will discuss how we want to handle this Monday, because we think events such as web vitals are nice to show, however it is confusing for the user to see. |
Have there been any updates since then? I'm experiencing the same issue and am waiting for a resolution. |
@bino98 This should be fixed as of SDK version 8.35.0. Please let me know if you still experience this after upgrading your SDK! |
Closing as this should be fixed by 8.35.0 (as noted above). Please open a new ticket if you're still experiencing an issue. |
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
8.31.0 and 7.119.0
Framework Version
React 17.0.0
Link to Sentry event
No response
Reproduction Example/SDK Setup
Steps to Reproduce
Expected Result
The replay in sentry only has the movements from after the replay was started
Actual Result
The replay in sentry has a a period at the start when nothing is shown in the replay. Then it shows the "start replay" click and all the movements as expected until the replay is stopped.
There are no request sent to sentry before the replay starts, I could not identify why the Sentry UI is showing the freezed paged for such a long time before the actual start of the replay. Sample replays can be found in my organisation:
https://dev-curumas.sentry.io/replays/?project=5278835
The text was updated successfully, but these errors were encountered: