-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed as not planned
Closed as not planned
Copy link
Labels
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/react
SDK Version
7.100.1
Framework Version
18.2.0
Link to Sentry event
No response
SDK Setup
Sentry.init({
dsn: 'xxx',
integrations: [
Sentry.reactRouterV6BrowserTracingIntegration({
useEffect,
useLocation,
useNavigationType,
createRoutesFromChildren,
matchRoutes,
}),
Sentry.replayIntegration(),
],
tracesSampleRate: 0.33,
release: `${name}@${version}`,
replaysSessionSampleRate: 0.33,
replaysOnErrorSampleRate: 1.0,
normalizeDepth: 6,
})
Steps to Reproduce
- Init Sentry
- After user login, call
Sentry.setUser({ id: 'Manager:123' }) - Expected to see user
Manager:123in administration - From browser is sent
Manager}:123(checked network; our code is settingManager:123) - In Sentry dashboard is
Manager}:123for events with `@sentry/react
Expected Result
Before version 7.99.0 everything worked as expected. In version 7.100.1 7.99.0...7.100.1 something happened to @sentry/react and started adding } to user.id while calling Sentry.setUser({ id: 'Manager:123' })
Actual Result
Version 7.100.1 should set in code Sentry.setUser({ id: 'Manager:123' }) and in UI the user.id should be Manager:123 instead of Manager}:123
Metadata
Metadata
Assignees
Labels
Projects
Status
Waiting for: Community