random crash with "this.updateVisibleFocusableElements.bind"

[dtogias]

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

SDK Version

8.54.0

Framework Version

nuxt 3.13.2

Link to Sentry event

https://myinstacar.sentry.io/issues/6733343905/?project=4507883486445568&referrer=project-issue-stream

Reproduction Example/SDK Setup

No response

Steps to Reproduce

N/A

Expected Result

Last night we started seeing a lot of these errors, with no change in our codebase.

Stacktrace

TypeError: undefined is not an object (evaluating 'this.updateVisibleFocusableElements.bind')
  at ? (/e88a641f-fb46-4045-915b-041d3f690251/cc.js:2:222692)
  at sentryWrapped(./node_modules/@sentry/browser/build/npm/esm/helpers.js:93:17)

Actual Result

Not crash

[Lms24]

Hi @dtogias thanks for writing in!

What makes you think that this is an SDK issue? the sentryWrapped stack frame only indicates that the error thrown happened in a callback that was wrapped by the Sentry SDK. Furthermore, I don't see any usage of updateVisibleFocusableElements in our SDK code. From the stack trace, it seems like this error originates from an anonymous function in the cc.js file.

with no change in our codebase

Any chance you're pulling in a 3rd party script, e.g. from some CDN? This could change without you actively making changes. Could also be a browser extension from particular users.

[casions]

I believe that this error is being thrown by Cookiebot and has nothing to do with Sentry. @dtogias, can you confirm you are also using Cookiebot?

[jkennedyphlo]

@dtogias
Good morning, we had the same error start occurring yesterday morning.

Tracked it down to a Cookiebot consent banner.
If it is displayed, or was previously displayed during the customers session then on resize of screen this error is thrown - a lot!

So far doesnt seem to be causing users issue using our site.