sentry-javascript: Sentry floods Sentry with "antifingerprint not defined yet. will try and handle event after its ready..."

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.68.0

Framework Version

7.68.0

Link to Sentry event

https://hjemmelegene.sentry.io/issues/4496677982

SDK Setup

Sentry.init({ dsn: ‘https://93f5f63cb2514405a700053731ef67a6@o518563.ingest.sentry.io/5627822’, beforeSend, // Replay may only be enabled for the client-side integrations: [new Sentry.Replay()],

// Set tracesSampleRate to 1.0 to capture 100% // of transactions for performance monitoring. // We recommend adjusting this value in production tracesSampleRate: 0.1,

// Capture Replay for 10% of all sessions, // plus for 100% of sessions with an error replaysSessionSampleRate: 0.1, replaysOnErrorSampleRate: 1.0,

// …

// Note: if you want to override the automatic release value, do not set a // release value here - use the environment variable SENTRY_RELEASE, so // that it will also get attached to your source maps })

Steps to Reproduce

  1. Installed Sentry as per the modification suggested by the Sentry team over at Nx https://github.com/nrwl/nx/pull/19338
  2. Deployed to production

Expected Result

Sentry not introducing its own errors

Actual Result

Stack Trace

antifingerprint not defined yet. will try and handle event after its ready…

Crashed in non-app: ./node_modules/@sentry/integrations/esm/captureconsole.js in callback

Show 2 more frames

about:blank in generalAddEventListenerLogic at line 36:21 In App about:blank in HTMLDivElement.Element.addEventListener at line 49:5 In App Called from: ./node_modules/react-dom/cjs/react-dom.production.min.js in af

Show 2 more frames

<anonymous> in Set.forEach In App Called from: ./node_modules/react-dom/cjs/react-dom.production.min.js in cf

About this issue

  • Original URL
  • State: closed
  • Created 9 months ago
  • Reactions: 1
  • Comments: 18 (7 by maintainers)

Most upvoted comments

For anyone else experiencing this, it looks related to Outlook safelink scanning: https://github.com/getsentry/sentry-javascript/issues/3440#issuecomment-865857552

This is very unlikely an issue with the sentry SDK. If you don’t see any user impact from these errors/issues we recommend ignoring them in Sentry.

@nordhagen Fingerprinting in Sentry is definitely not related to this.

You have multiple ways of filtering out events: https://docs.sentry.io/platforms/javascript/configuration/filtering/