TypeError: getCurrentHub(...).getIsolationScope is not a function

[khanharis87]

I am facing this issue, which is breaking my whole app. It seems to be in sentry but I can not get more information what might be the problem. Sentry logs tells

Crashed in non-app: /app/node_modules/.pnpm/@[email protected]/node_modules/@sentry/core/cjs/hub.js

/**
 * Get the currently active isolation scope.
 * The isolation scope is active for the current exection context,
 * meaning that it will remain stable for the same Hub.
 */
function getIsolationScope() {
  // eslint-disable-next-line deprecation/deprecation
  return getCurrentHub().getIsolationScope();
}

[lforst]

Hi, I suspect a dependency conflict. Please try to wipe your package manager cache and reinstall node_modules. Thanks!

[lforst]

@stormfar That also looks like a conflict in your dependencies. Can you clear your caches and reinstall node modules? Thanks!

[stormfar]

Appreciate the prompt response!

Just tried deleting node_modules, package-lock.json and even the .next dir, followed by npm cache clean --force, then npm install and the problem persists. Not sure what other cache I could be missing.

[stormfar]

Think I found the issue. The error does not show when I comment out this line the Sentry.init call in sentry.client.config.js:

// Adjust this value in production, or use tracesSampler for greater control
tracesSampleRate: 1,

I'm not sure why, but at least it works.

However, when I throw an error from /sentry-example-page, I see a similar issue.

Interestingly, normal issues are being created at sentry.io

[lforst]

Are all your sentry package versions aligned in your package json?

[stormfar]

Indeed they are. Same version in package.json and package-lock.json