-
Notifications
You must be signed in to change notification settings - Fork 70
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
LogRocket sessionUrl not set #72
Comments
A possibility is to follow along with This way you'd get a new fieldset with a |
After some investigation this is not a problem with this module but the Sentry JS SDK itself. To summarise you can't use This means it doesn't work for JS errors that trigger on page load but it works with errors that trigger afterwards (like AJAX requests, etc). What we did was going the other way around, save the Sentry |
Do you want to request a feature or report a bug?
Bug
Bug: What is the current behavior?
The LogRocket sessionUrl does not show in Sentry's issue report when LogRocket is configured.
Bug: What is the expected behavior?
The LogRocket sessionUrl should show in Sentry's issue report when LogRocket is configured.
Bug: What is the proposed solution?
I'm not sure to be honest, here's a few things I tried but didn't help:
setContext
instead sincesetExtra
was deprecated.setTag("sessionUrl", sessionUrl)
.5.30.0
version of the JS SDK instead of5.28.0
.I can confirm LogRocket works as expected and the URL does get generated (I added a
console.log(sessionUrl)
and visiting the logged URL does show the session replay fine). I'm not sure if this is an issue with the module or LogRocket/Sentry.What is the version of Magento and of Sentry extension you are using? Always use the latest version of the extension one before opening a bug issue.
Magento 2.4.1
Module 2.5.0
The text was updated successfully, but these errors were encountered: