Browser SDK still sending 'session' data despite being disabled

[samkelleher]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Sentry 'Session' is disabled. It's something we never wanted. It was disabled. Following upgrade to 9.1.0, the SDK is making calls again. The docs indicate the config is correct.

Sentry.init({
    dsn: "example",
    environment: "production",
    release: "example",
    autoSessionTracking: false,
    replaysSessionSampleRate: 0,
    replaysOnErrorSampleRate: 0,
  });

In the above setup, sentry is still making calls

{"sent_at":"2025-02-14T12:59:24.684Z","sdk":{"name":"sentry.javascript.browser","version":"9.1.0"}}
{"type":"session"}

Expected Result

Sentry should not be making any calls.

Actual Result

Sentry is making tracking calls.

Product Area

Replays

Link

No response

DSN

No response

Version

9.1.0

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-replays for triage ⏲️

[andreiborza]

Hey @samkelleher, thanks for filing this.

autoSessionTracking has been removed with v9 of our SDKs. To prevent session tracking you have to remove the BrowserSession integration:

Sentry.init({
  ...
  integrations: (defaults) => defaults.filter((i) => i.name !== "BrowserSession"),
})

[samkelleher]

Thank you highlighting this, we've adjusted that here. 🙌