Errors in rrweb

[sentry]

Sentry Issue: JAVASCRIPT-2B7E

TypeError: Cannot read properties of undefined (reading 'prototype')
  at Array.forEach (<anonymous>)
  at new Promise (<anonymous>)
...
(18 additional frame(s) were not displayed)

One source of missing replay accounts appear to be here, where our SDK is erroring, but we tag events with the replayId anyways.

[igor-danilov1994]

we get the same error / can't figure out why((((

[mydea]

@igor-danilov1994 do you only see this error, or is it actually also affecting replays not being sent etc.?

[emewjin]

Is this same error?

// TypeError: Cannot read properties of undefined (reading 'prototype')
// ../../../node_modules/@sentry/replay/esm/node_modules/rrweb/es/rrweb/packages/rrweb/src/record/observer.js at line 382:26
            }
            return unmodifiedFunctions[typeKey].deleteRule.apply(this, arguments);
        };
    });
    return function () {
        win.CSSStyleSheet.prototype.insertRule = insertRule; // <--- 🐞
        win.CSSStyleSheet.prototype.deleteRule = deleteRule;
        Object.entries(supportedNestedCSSRuleTypes).forEach(function (_a) {
            var _b = __read(_a, 2), typeKey = _b[0], type = _b[1];
            type.prototype.insertRule = unmodifiedFunctions[typeKey].insertRule;
            type.prototype.deleteRule = unmodifiedFunctions[typeKey].deleteRule;

our sentry replay setting is:

// version: 7.26.0
new Replay({
        blockAllMedia: false,
        maskAllText: false,
        maskAllInputs: false,
        inlineStylesheet: false,
      }),

[mydea]

Hi @emewjin , can you update your sentry version (including replay) to the latest version (7.28.1)? In 7.27.0 we landed a change that should avoid capturing rrweb errors to sentry. Let me know if the problem persists!

[emewjin]

@mydea Hi, I update to the 7.28.1 but the error still alive

[mydea]

Thanks for trying it! Just to be absolutely sure, you also updated @sentry/replay to 7.28.1, right?
This is... surprising! I guess you also do not have enabled any _experiments? Because judging from your screenshot, this error should be filtered out, as we filter them by stack, and I can see the path we filter on in the screenshot - see:

https://github.com/getsentry/sentry-javascript/blob/master/packages/replay/src/coreHandlers/handleGlobalEvent.ts#L24

and

https://github.com/getsentry/sentry-javascript/blob/master/packages/replay/src/util/isRrwebError.ts

[emewjin]

Just to be absolutely sure, you also updated @sentry/replay to 7.28.1, right?

absolutely 😅

I guess you also do not have enabled any _experiments?

Do you mean https://docs.sentry.io/platforms/javascript/guides/react/performance/instrumentation/automatic-instrumentation/#_experiments ?
We don't use that option, here is our full sentry setting

if (MODE !== 'localhost') {
  Sentry.init({
    dsn: '',
    release: import.meta.env.VITE_PLUGIN_SENTRY_CONFIG.release,
    replaysSessionSampleRate: 0.1,
    replaysOnErrorSampleRate: 1.0,
    environment: MODE,
    integrations: [
      new BrowserTracing(),
      new CaptureConsole({
        levels: ['error'],
      }),
      new Replay({
        blockAllMedia: false,
        maskAllText: false,
        maskAllInputs: false,
        inlineStylesheet: false,
      }),
    ],
    ignoreErrors: SENTRY_IGNORE_ERRORS,
    sampleRate: 1,
    tracesSampleRate: 1,
  });
}

[Lms24]

Hi @emewjin, could you share a screenshot of your raw stack trace? Just want to double check that the raw stack frame has the same URL which we test to filter out such rrweb errors. If you're using Sentry SaaS (sentry.io), would you mind sharing a link to the event so we could take a closer look at it? Thanks!

One last thing you could try would be to set debug: true in your Sentry config which will enable debug logging in the console. Maybe there's something going wrong in the initialization that could explain this.

Furthermore, are you using the SDK in a regular React+Vite app? Or are you in some kind of special environment? (e.g. a Micro Frontend app or a browser extension).

[emewjin]

hi @Lms24 !

If you're using Sentry SaaS (sentry.io), would you mind sharing a link to the event so we could take a closer look at it? Thanks!

Sure! link

Furthermore, are you using the SDK in a regular React+Vite app?

yes! our dependencies:

"vite-plugin-sentry": "^1.1.6",
"vite": "3.0.2",
"react": "17.0.2",
"react-dom": "17.0.2",
"@sentry/integrations": "^7.28.1",
"@sentry/react": "^7.28.1",
"@sentry/replay": "^7.28.1",
"@sentry/tracing": "^7.28.1",

[mydea]

This is really weird. TBH I am not entirely sure why this is not being ignored, as far as I can tell it should be ignored.
Anyhow, once we land this: #6749, this specific error should hopefully be avoided altogether!