User information no available in the release session #19317
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
10.38.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
Sentry.init({
dsn:"_MY_DSN_",
debug:true,
attachStacktrace:true,
release:"test-app@2.0.0",
enableLogs: true,
tracesSampleRate: 1.0,
integrations:[
Sentry.browserTracingIntegration(),
],
})
const id = Math.floor(Math.random() * 1000000)
Sentry.setUser({id:id})
//can send an error here or not
Steps to Reproduce
- Run a simple JS app with the code above
Expected Result
The release sessions sent by the app have user information to correctly count Crash free user in the server.
Actual Result
No user information is sent with the session:
{"sent_at":"2026-02-13T10:07:25.812Z","sdk":{"name":"sentry.javascript.browser","version":"10.38.0"}}
{"type":"session"}
{"sid":"7d8eac533290452fb49bf952ffe2c8a6","init":true,"started":"2026-02-13T10:07:25.812Z","timestamp":"2026-02-13T10:07:25.812Z","status":"ok","errors":0,"attrs":{"release":"test-app@2.0.0","environment":"production","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36"}}
A similar issue has been reported by two users via support:
https://sentry.zendesk.com/agent/tickets/173229
https://sentry.zendesk.com/agent/tickets/172353
In one case, you see 1.7K transactions in a release, with 1.7K users in those events, but the release page only counts 297 users. This leads to a low crash-free user rate when compared to crash free session rate. See screenshot: (traces sample rate is 0.01)
Additional Context
No response
Priority
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.