e.getLastBreadcrumb is not a function. (In 'e.getLastBreadcrumb()', 'e.getLastBreadcrumb' is undefined)

[m-nathani]

Environment

SaaS (https://sentry.io/)

Version

7.26.0

Link

https://sentry.io/organizations/umai/issues/3807945297/?project=5264087&referrer=slack

DSN

No response

Steps to Reproduce

it came after enabling replay and upgrading sentry to 7.26.0

Expected Result

should not throw this error.

Actual Result

Throwing exception of breadcrums not found.

[getsentry-release]

Routing to @getsentry/team-web-sdk-frontend for triage. ⏲️

[Lms24]

Hi @m-nathani please check that you've upgraded all @sentry/* packages, especially @sentry/core which exports this function since 7.26.0.

[m-nathani]

Hi @m-nathani please check that you've upgraded all @sentry/* packages, especially @sentry/core which exports this function since 7.26.0.

Yup they are latest @Lms24

    "@sentry/react": "^7.26.0",
    "@sentry/replay": "^7.26.0",
    "@sentry/tracing": "^7.26.0",

[Lms24]

When you install @sentry/react, you also add additional packages to your node_modules directory, such as @sentry/core. So just to confirm, is @sentry/core in your node_modules also on version 7.26.0?

Just as a heads-up: I'm transferring this issue to the SDK repo by the way

[m-nathani]

When you install @sentry/react, you also add additional packages to your node_modules directory, such as @sentry/core. So just to confirm, is @sentry/core in your node_modules also on version 7.26.0?

Just as a heads-up: I'm transferring this issue to the SDK repo by the way

Yo, checked its latest:

    "node_modules/@sentry/core": {
      "version": "7.26.0",
      "resolved": "https://registry.npmjs.org/@sentry/core/-/core-7.26.0.tgz",
      "integrity": "sha512-ydi236ZoP/xpvLdf7B8seKjCcGc5Z+q9c14tHCFusplPZgLSXcYpiiLIDWmF7OAXO89sSbb1NaFt9YB0LkYdLQ==",
      "dependencies": {
        "@sentry/types": "7.26.0",
        "@sentry/utils": "7.26.0",
        "tslib": "^1.9.3"
      },
      "engines": {
        "node": ">=8"
      }
    },

[Lms24]

Hmm, usually these problems occur because of version mismatches, when you upgrade e.g. Replay or Browser but for some reason not core or any of the other Sentry dependencies. Is there any chance that you have a browser extension or 3rd party script installed that uses Sentry? Or are you perhaps using multiple Sentry instances yourself (Micro frontend architecture, module federation, etc)?

Also, would you mind sharing your Sentry init config? I'm curious if you're doing anything special when setting up Sentry and Replay

[m-nathani]

Hmm, usually these problems occur because of version mismatches, when you upgrade e.g. Replay or Browser but for some reason not core or any of the other Sentry dependencies. Is there any chance that you have a browser extension or 3rd party script installed that uses Sentry? Or are you perhaps using multiple Sentry instances yourself (Micro frontend architecture, module federation, etc)?

Also, would you mind sharing your Sentry init config? I'm curious if you're doing anything special when setting up Sentry and Replay

Hey..

I am pretty sure the versions are matched after the upgrade..

Moreover, for the extension I am not sure as this is opened on the client browser... However there is not any 3rd party apps that's using sentry.

Lastly, there was an issue for multiple instance which we have solved on our app today and is fixed.

Here the configuration we are doing for sentry:

export const initSentry = () =>
  Sentry.init({
    dsn: process.env.REACT_APP_SENTRY_DSN,
    release: `widget@${version}`,
    environment: `widget@${process.env.REACT_APP_ENVIRONMENT}`,
    ignoreErrors: [
      /ResizeObserver loop limit exceeded.*/,
      /SecurityError: The operation is insecure.*/,
      /SecurityError: Blocked a frame with origin.*/,
      /Non-Error promise rejection captured.*/
    ],
    integrations: [new Integrations.BrowserTracing(), new Replay()],

    // We recommend adjusting this value in production, or using tracesSampler
    // for finer control
    tracesSampleRate: isProductionEnv() ? 0.2 : 1.0,

    // This sets the sample rate to be 10%. You may want this to be 100% while
    // in development and sample at a lower rate in production
    replaysSessionSampleRate: isProductionEnv() ? 0.1 : 1.0,
    // If the entire session is not sampled, use the below sample rate to sample
    // sessions when an error occurs.
    replaysOnErrorSampleRate: 1.0
  });