Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
8.55.0
Framework Version
React 19.1.0
Link to Sentry event
https://rubrikinc.sentry.io/explore/discover/trace/7bdadd12bb354a6b9b49cd265bb6b866/?dataset=transactions&field=title&field=project&field=user.display&field=timestamp&name=All%20Errors&node=span-8602bdf238eefb8a&query=transaction%3A%2A%2F%2A%2F3%2F%2A&queryDataset=transaction-like&sort=-timestamp&source=discover&statsPeriod=30d×tamp=1755069450&yAxis=count%28%29
Reproduction Example/SDK Setup
https://github.com/rk-1203/sentry-router-simple/tree/route-config-and-sentry-v9
Steps to Reproduce
This issue is happening when we have lazy-loaded routes in our application, and when Sentry tries to capture the page load transaction for that route.
This issue is fixed now in v10.3.0. We are asking for a backport to 8.55.0.
This might be the PR where it's fixed - #17277
Expected Result
The transaction should look like
- /part1/part2/:id
- /part1/part2/:id/:anotherId
- /part1/part2/:id/:anotherId/:someAnotherId
Actual Result
Current transaction looks like
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
8.55.0
Framework Version
React 19.1.0
Link to Sentry event
https://rubrikinc.sentry.io/explore/discover/trace/7bdadd12bb354a6b9b49cd265bb6b866/?dataset=transactions&field=title&field=project&field=user.display&field=timestamp&name=All%20Errors&node=span-8602bdf238eefb8a&query=transaction%3A%2A%2F%2A%2F3%2F%2A&queryDataset=transaction-like&sort=-timestamp&source=discover&statsPeriod=30d×tamp=1755069450&yAxis=count%28%29
Reproduction Example/SDK Setup
https://github.com/rk-1203/sentry-router-simple/tree/route-config-and-sentry-v9
Steps to Reproduce
This issue is happening when we have lazy-loaded routes in our application, and when Sentry tries to capture the page load transaction for that route.
This issue is fixed now in v10.3.0. We are asking for a backport to 8.55.0.
This might be the PR where it's fixed - #17277
Expected Result
The transaction should look like
Actual Result
Current transaction looks like