TypeError: d.m_ is not a function after upgrading to @sentry/ember 7.100.1

[rohitpaulk]

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

SDK Version

7.100.1

Framework Version

7.100.1

Link to Sentry event

https://codecrafters.sentry.io/issues/4953498292/?project=5922961&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=24h&stream_index=0

SDK Setup

Sentry.init({
    autoSessionTracking: true,
    dsn: config.environment === 'production' ? sentryDSN : '',
    environment: config.environment,
    tracesSampleRate: 0.01,
});

Steps to Reproduce

Load any page with Sentry enabled.

Expected Result

No errors in console

Actual Result

Errors are present in the console.

[mydea]

Hey, can you double check that all @sentry/xxx packages you have installed have the same/correct version? This smells to me like there may be an outdated dependency somewhere that is being picked up, possibly, as this method was added in an recent version.

[rohitpaulk]

@mydea from the looks of it everything does seem to have the correct version:

The only entry in package.json is @sentry/ember, I looked in package-lock.json and found these:

[AbhiPrasad]

This should be exported:

sentry-javascript/packages/ember/addon/index.ts

Line 120 in 737fb0e

export * from '@sentry/browser';

sentry-javascript/packages/browser/src/index.ts

Line 64 in 737fb0e

startBrowserTracingPageLoadSpan,

sentry-javascript/packages/ember/addon/instance-initializers/sentry-performance.ts

Line 9 in 737fb0e

import * as Sentry from '@sentry/browser';

If you do

import * as Sentry from '@sentry/ember';

console.log(Sentry.startBrowserTracingPageLoadSpan);

what gets emitted?

[mike-engel]

I'm having the same issue here. Here's the output with the log:

I'm on ^7.102.1 for all dependencies