isBrainDed
isBrainDed
Should I keep the session open for multiple hours to see if at some point the error is reported properly? Anything required from me or just wait for the other...
Hello, I have tested it on SaaS and it seems that the Error is being seen in the replays there. Issue: https://isbrainded.sentry.io/issues/218501/events/82b516c155a64eb181193a92c802e004/ Replay: https://isbrainded.sentry.io/replays/e8d33e70c59f45a4a60327286fa5a0c9/?referrer=%2Freplays%2F%3AreplaySlug%2F&t=0&t_main=errors I have created it again on...
```js Sentry.init({ app, dsn: "REMOVED", integrations: [ Sentry.browserTracingIntegration(), Sentry.replayIntegration(), ], trackComponents: true, // Performance Monitoring tracesSampleRate: 1.0, // Capture 100% of the transactions // Set 'tracePropagationTargets' to control for which...
I will update my local instance in the next 24 hours
I have tried on Sentry 24.4.2 and the scenario is still the same. If you want me to go on specific commit, let me know the exact commit
"dependencies": { "@sentry/vue": "^7.112.2", "pinia": "^2.1.7", "vue": "^3.4.21", "vue-router": "^4.3.0" },
Updated to "dependencies": { "@sentry/vue": "^8.0.0", "pinia": "^2.1.7", "vue": "^3.4.21", "vue-router": "^4.3.0" }, Same issue persists as well
Let me know if you need any logs from any of the containers and how to collect them, I can submit any of it.