@sentry/nextjs: Multiple browserTracingIntegration instances are not supported.

[mrmckeb]

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/nextjs

SDK Version

9.22.0

Framework Version

next: ^15.3.2 / react: ^19.1.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

// instrumentation-client.ts
import {
  browserTracingIntegration,
  featureFlagsIntegration,
  init,
  replayIntegration,
} from "@sentry/nextjs";

init({
  integrations: [
    browserTracingIntegration(),
    featureFlagsIntegration(),
    replayIntegration({
      blockAllMedia: true,
      maskAllInputs: true,
      maskAllText: true,
    }),
  ],

  tracesSampleRate: 0.01,

  replaysOnErrorSampleRate: 1.0,

  replaysSessionSampleRate: 0,
}

Steps to Reproduce

We have Turbopack on for development only. We do have instrumentation.ts for Edge & Server.

Expected Result

Should not see the browserTracingIntegration warning logged to the browser console.

Actual Result

The warning is logged in production:

Multiple browserTracingIntegration instances are not supported.

[chargome]

Hey @mrmckeb, thanks for reaching out!

You don't need to add the browserTracingIntegration() in your integrations array, just set a sample rate and you should be good 👍 (you can check the example in our docs)

[Lms24]

Worth noting though that the SDK should not throw this warning but merge multiple browserTracingIntegrations in meta frameworks (where we indeed add a default instance). Otherwise, there's no way for users to configure browserTracingIntegration differently to the default instance. This is likely a result of #16042 (which admittedly I must have missed in the review)

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16386, which was included in the 9.23.0 release.

[mrmckeb]

Thanks, I'll update to the new release ASAP!