fix(browser): Ensure user id is consistently added to sessions#19341
Open
fix(browser): Ensure user id is consistently added to sessions#19341
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
Codecov Results 📊✅ 415 passed | ⏭️ 179 skipped | Total: 594 | Pass Rate: 69.87% | Execution Time: 9m 44s All tests are passing successfully. Generated by Codecov Action |
Contributor
size-limit report 📦
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
Lms24
changed the title
Sentry.setUser calls
3 tasks
JPeer264
approved these changes
Feb 16, 2026
CHANGELOG.md
Outdated
|
|
||
| While we're at it, if you're using Sentry in a Single Page App or meta framework, you might want to give the new `'page'` session lifecycle a try! | ||
| This new mode no longer creates a session per soft navigation but continues the initial session until the next hard page refresh. | ||
| Check out the [docs](TODO LINK) to learn more! |
Member
There was a problem hiding this comment.
l: Just a reminder to not forget to set the link in the docs
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
6 tasks
Co-authored-by: Jan Peer Stöcklmair <jan.peer@sentry.io>
Lms24
force-pushed
the
lms/fix-browser-session-user
branch
from
eb2a670 to
5a94cad
Compare
Lms24
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Feb 18, 2026
…ntegration` (#16428) <!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR Adds docs for getsentry/sentry-javascript#18997. I'd like to merge this before getsentry/sentry-javascript#19341 since it calls out this page in the changelog. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes multiple bugs and problems around browser sessions, mostly related to user id assignment:
When calling
Sentry.setUser()on static pages (i.e. no soft navigations), the user id would never be added to sessions. This is because in static pages, we don't send an"exited"session update. The fix: We send a session update whenever the user is set on the isolationScope (see comment about limitations)When calling
Sentry.setUser()in a single page application (i.e. with soft navigations), we would update the initial session with the user data when starting a new session for a new navigation. However, we did not include the user id on the new session, because thegetCurrentScope().getUser() || getIsolationScope().getUser()check was flawed. The fix: we use ourgetCombinedScopeDatahelper to get the "correct" (read, consistently like in other telemetry items) user.It seems like we had an incorrect check that would skip creating a new sessions for the first soft navigation after the pageload (in the default
'route') session lifecycle. The fix: We no longer check forfrombeing undefined.In addition, I also added a new
waitForSessionhelper and refactored most session integration tests to use this helper. This allows us to more granularly listen to multiple session envelopes simultaneously without running into collision risks.As a result of these fixes, session counts could increase as a whole but also metrics like "crash free users" will likely change. I added a note to the changelog calling this out.
Waiting on https://github.com/getsentry/sentry-docs/pull/16428/changes for final changelog note modification
closes #19317