You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PerformanceResourceTiming.nextHopProtocol is used without check for support #16804
We're updating our Sentry dependencies from v8 to v9, but Sentry performance monitoring (tracing integration) causes a breaking error in devices that use older browsers.
Looking at the error data, we can trace the error to the usage of nextHopProtocol without check for support. I can see that this code was added in #15161
Steps to Reproduce
Just loading any page and initializing Sentry triggers this error.
Expected Result
Sentry should initialize without issues, even in older browsers that don't have full support of browser APIs
Actual Result
Sentry triggers an error that breaks the whole application
yeah, we need to support much older browsers so we transpile all our dependencies, which has been working fine for the most part.
For what I can see this is the only issue that breaks our Sentry integration
Hi, thanks for the quick help with this issue.
However, I was just testing it and I'm afraid that the fix didn't work :(
Looking at the error stack, the error comes from packages/browser-utils/src/metrics/browserMetrics.ts in the _addResourceSpans() function. I guess that the fix needs to be applied there
Activity
AbhiPrasad commentedon Jul 3, 2025
Hey @Mantish thanks for writing in.
What browser/browser version are you testing this on? Here are the supported browser versions by the Sentry SDK in v9: https://docs.sentry.io/platforms/javascript/troubleshooting/supported-browsers/
Mantish commentedon Jul 3, 2025
yeah, we need to support much older browsers so we transpile all our dependencies, which has been working fine for the most part.
For what I can see this is the only issue that breaks our Sentry integration
AbhiPrasad commentedon Jul 3, 2025
yeah fair, I think we can add a guard for this so that we unblock you.
Mantish commentedon Jul 3, 2025
that would be great!! 🙏
AbhiPrasad commentedon Jul 3, 2025
Opened #16806 to fix!
fix(browser): Guard against undefined nextHopProtocol (#16806)
github-actions commentedon Jul 9, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #16806, which was included in the 9.36.0 release.
Mantish commentedon Jul 10, 2025
Hi, thanks for the quick help with this issue.
However, I was just testing it and I'm afraid that the fix didn't work :(
Looking at the error stack, the error comes from
packages/browser-utils/src/metrics/browserMetrics.tsin the_addResourceSpans()function. I guess that the fix needs to be applied thereAbhiPrasad commentedon Jul 10, 2025
Yup you're right @Mantish - opened a PR for that here: #16900
fix(browser): guard `nextHopProtocol` when adding resource spans (#16900
AbhiPrasad commentedon Jul 14, 2025
released with https://github.com/getsentry/sentry-javascript/releases/tag/9.38.0