Undefined hub.startSession on v6 upgrade

[namoscato]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• other: @sentry/react

Version:

6.0.4

Description

I'm getting an error when bumping @sentry/react to v6.0.4:

Uncaught TypeError: hub.startSession is not a function
    at startSessionTracking (sdk.ts:221)
    at init (sdk.ts:106)
    at Module.init (sdk.ts:18)
    at Module.<anonymous> (index.tsx:22)
    at Module../src/index.tsx (index.tsx:64)
    at __webpack_require__ (bootstrap:856)
    at fn (bootstrap:150)
    at Object.1 (wdyr.js:11)
    at __webpack_require__ (bootstrap:856)
    at checkDeferredModules (bootstrap:45)
    at Array.webpackJsonpCallback [as push] (bootstrap:32)
    at main.chunk.js:1

Debugging this line, hub indeed does not seem to have a startSession function on its prototype.

Disabling autoSessionTracking fixes the issue, but is this expected?

[kamilogorek]

Debugging this line, hub indeed does not seem to have a startSession function on its prototype.

https://github.com/getsentry/sentry-javascript/blob/6.0.4/packages/hub/src/hub.ts#L363-L379

Can you verify that all @sentry/react dependencies also get updated to the v6? It looks like something is out of sync here.

[namoscato]

Can you verify that all @sentry/react dependencies also get updated to the v6? It looks like something is out of sync here.

Yeah, we use a few other packages with indirect @sentry/minimal dependencies, but I tried to mitigate this via Yarn resolutions:

{
    "resolutions": {
        "@sentry/hub": "^6.0.4",
        "@sentry/minimal": "^6.0.4",
        "@sentry/types": "^6.0.4"
    }
}

Here's the output of npm-ls for all @sentry/* packages

├─┬ @sentry/react@6.0.4
│ ├─┬ @sentry/browser@6.0.4
│ │ ├─┬ @sentry/core@6.0.4
│ │ │ ├── @sentry/hub@6.0.4 deduped
│ │ │ ├── @sentry/minimal@6.0.4 deduped
│ │ │ ├── @sentry/types@6.0.4 deduped
│ │ │ ├── @sentry/utils@6.0.4 deduped
│ │ │ └── tslib@1.14.1
│ │ ├── @sentry/types@6.0.4 deduped
│ │ ├── @sentry/utils@6.0.4 deduped
│ │ └── tslib@1.14.1
│ ├─┬ @sentry/minimal@6.0.4
│ │ ├── @sentry/hub@6.0.4 deduped
│ │ ├── @sentry/types@6.0.4 deduped
│ │ └── tslib@1.14.1
│ ├── @sentry/types@6.0.4
│ ├─┬ @sentry/utils@6.0.4
│ │ ├── @sentry/types@6.0.4 deduped
│ │ └── tslib@1.14.1
│ ├── hoist-non-react-statics@3.3.2 deduped
│ └── tslib@1.14.1
├─┬ @sentry/tracing@6.0.4
│ ├─┬ @sentry/hub@6.0.4
│ │ ├── @sentry/types@6.0.4 deduped
│ │ ├── @sentry/utils@6.0.4 deduped
│ │ └── tslib@1.14.1
│ ├── @sentry/minimal@6.0.4 deduped
│ ├── @sentry/types@6.0.4 deduped
│ ├── @sentry/utils@6.0.4 deduped
│ └── tslib@1.14.1
├─┬ apollo-link-sentry@1.3.0
│ ├── UNMET DEPENDENCY @sentry/minimal@^5.15.5
│ ├── UNMET DEPENDENCY @sentry/types@^5.15.4
│ ├── apollo-link@1.2.14 deduped
│ ├── deepmerge@4.2.2
│ ├─┬ dot-prop@5.2.0
│ │ └── is-obj@2.0.0
│ └── tslib@1.14.1
├─┬ filestack-js@3.18.0
│ ├─┬ @babel/runtime@7.9.0
│ │ └── regenerator-runtime@0.13.5 deduped
│ ├── @filestack/loader@1.0.7
│ ├── UNMET DEPENDENCY @sentry/minimal@^5.12.0
│ ├── abab@2.0.3
│ ├─┬ debug@4.1.1
│ │ └── ms@2.1.2
│ ├── eventemitter3@4.0.0
│ ├── fast-xml-parser@3.17.4
│ ├── file-type@10.11.0
│ ├── follow-redirects@1.11.0 deduped
│ ├── isutf8@2.1.0
│ ├── jsonschema@1.2.6
│ ├── lodash.clonedeep@4.5.0
│ ├─┬ p-queue@4.0.0
│ │ └── eventemitter3@3.1.2
│ ├── spark-md5@3.0.1
│ └── ts-node@8.10.2 deduped

[iker-barriocanal]

The method startSession exists since pre-v6 and the functionality (startSessionTracking) has been enabled by default in v6. I don't see any way that this could possibly happen as your package manager ranges are restricted to major versions so they should always resolve to v6. Is there a chance you could provide a minimal repro case?

[namoscato]

Is there a chance you could provide a minimal repro case?

Yeah, I'll try to put something together over the next week or so that approaches the state of my project, and hopefully we can figure it out.

Thanks for trying to help, @kamilogorek and @iker-barriocanal!

[lobsterkatie]

@namoscato It's a long shot, but any chance you're running into this? #3207 (comment)

[namoscato]

@lobsterkatie, that's a good thought but not the case.

I spent some more time with this and isolated the issue to a conflicting filestack-js dependency. Here's a simple sandbox that illustrates the issue. I haven't looked into their implementation yet and am happy to reach out to them about it, but do any of you have any thoughts / recommendations?

It's worth noting this issue seems to prevent a bunch of context from making its way to Sentry as well.

[namoscato]

I'm guessing this scope configuration is at least causing the missing context issue? As mentioned here:

it is discouraged to interfere with the event context. If for some reason your library needs to inject context information, beware that this might override the user's context values

[lobsterkatie]

Heh. Yeah - https://github.com/filestack/filestack-js/blob/a11ebc0e61d73b31e7d63e488e81c4d90d3e69ad/package.json#L45. Good find.

I mean, yes, by far the simplest short-term fix is if you can convince them to upgrade to at least 5.27.0, as that was the release which introduced Hub.startSession. That doesn't fix the long-term issue, though.

This quarter we're working on the next major version of the SDK, and as part of that, we're going to re-examine the way we deal with situations like this, where there are competing Sentry instances on a page. I've added this (version conflicts) to our list of specific things to solve for in that process.

If you don't mind poking them to upgrade as a first step, let's start there and see if we can at least get you going again.

[namoscato]

I've added this (version conflicts) to our list of specific things to solve for in that process.

That's fantastic, @lobsterkatie – thanks!

If you don't mind poking them to upgrade as a first step, let's start there and see if we can at least get you going again.

I think filestack/filestack-js#416 summarizes the issue(s), but let me know if I'm misinterpreting anything.

[thinhvo0108]

I have exactly the same problem here (on using the combination Sentry + FileStack)
It has been a week, any update so far?