-
Notifications
You must be signed in to change notification settings - Fork 251
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
Vue3: Two hits to sessions.bugsnag.com on each route change #1697
Comments
After digging in to this further, I don't think that this is a bug with Bugsnag. Sorry for the noise. For the record, the new Vue Router ( Vue 3's router differs from Vue 2's, which just does a |
Hi @bbotto-pdga - thanks for bringing this to our attention. Although this isn't strictly an issue with Bugsnag in the sense that There's also a bit of discussion over at #1071 if you wanted to override the default behaviour with manual session tracking. |
Thanks @luke-belton. I read through #1071 prior to adding this issue and ended up going with manual session tracking. After reading up on the subject, I think we should have been using manual session tracking all along, even in Vue 2. For us, our Vue application is an SPA. We now start a single session when the SPA is loaded--no new sessions on route change. |
Describe the bug
My team is in the process of upgrading from Vue 2 to Vue 3:
Steps to reproduce
I've attached a small zip archive with reproduction code. Unzip it, install deps, then run the code:
Update
src/main.js
with a valid API key on line 32.Run the app:
Open http://localhost:3001/first-page in a browser. Note that each time a link is clicked in the app, there are two posts to sessions.bugsnag.com. Below is a screenshot that shows the network requests after opening the aforementioned link, then navigating one time using the link on the page:
If I recreate the same code in Vue 2, I see only one hit to session.bugsnag.com on each route change.
Environment
@bugsnag/plugin-vue
dependency, although it has it specified in package.json.vue-bs-repro.zip
The text was updated successfully, but these errors were encountered: