Starting from a certain version, the `transaction` recorded by Sentry started getting messed up

[wong2]

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-router

SDK Version

10.23.0

Framework Version

react router v7

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Our project is private and too big, I can't provide it.

Expected Result

Sentry can accurately record the request path where the error occurred.

Actual Result

Sentry often logs error request paths.

Additional Context

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1153

[logaretm]

Thanks for creating an issue, can you elaborate more on how it is "messed up" exactly? Did it start to happen after an upgrade to a specific version?

Also a link to the event can be helpful for us.