From e7d5d1fc110d7a9692bfde8b99d1c1a80bf7e0e5 Mon Sep 17 00:00:00 2001 From: Doron Pearl Date: Tue, 4 Mar 2025 10:57:12 -0500 Subject: [PATCH 1/3] ref(sourcemaps): added fault integration to troubleshooting doc --- platform-includes/sourcemaps/troubleshooting/javascript.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 0778afc2795a2..78e6afb0ec192 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -184,3 +184,8 @@ The Sentry Node.js SDK generally works well with the [source-map-support](https: If you are uploading source maps to Sentry or if you are using a Sentry SDK in the browser, your code cannot use the `source-map-support` package. `source-map-support` overwrites the captured stack trace in a way that prevents our source map processors from correctly parsing it. + +### Third-Party Integrations +In rare cases, faulty integrations may modify the error sent to Sentry, causing essential information to be lost and preventing Sentry from displaying the source map. Temporarily disable third-party [integrations](../../../docs/platforms/javascript/common/configuration/integrations/index.mdx) to rule out this possibility. + + From d0adecd7b11b7a85ff712050740f054568474c03 Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Thu, 24 Apr 2025 09:40:12 +0200 Subject: [PATCH 2/3] Update platform-includes/sourcemaps/troubleshooting/javascript.mdx --- platform-includes/sourcemaps/troubleshooting/javascript.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 78e6afb0ec192..d883d2faf62cb 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -186,6 +186,6 @@ If you are uploading source maps to Sentry or if you are using a Sentry SDK in t `source-map-support` overwrites the captured stack trace in a way that prevents our source map processors from correctly parsing it. ### Third-Party Integrations -In rare cases, faulty integrations may modify the error sent to Sentry, causing essential information to be lost and preventing Sentry from displaying the source map. Temporarily disable third-party [integrations](../../../docs/platforms/javascript/common/configuration/integrations/index.mdx) to rule out this possibility. +In rare cases, faulty or outdated third-party integrations may modify the error sent to Sentry, causing essential information to be lost and preventing Sentry from displaying the source map. If you're using a third party integration or other community-maintained packages, try to temporarily disable them to rule out this possibility. From 93cc616883e4b970b081e466f90783f3bc269b76 Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Thu, 24 Apr 2025 09:51:34 +0200 Subject: [PATCH 3/3] add conflicting package by name --- platform-includes/sourcemaps/troubleshooting/javascript.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index d883d2faf62cb..8b0f14487d43a 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -186,6 +186,9 @@ If you are uploading source maps to Sentry or if you are using a Sentry SDK in t `source-map-support` overwrites the captured stack trace in a way that prevents our source map processors from correctly parsing it. ### Third-Party Integrations + In rare cases, faulty or outdated third-party integrations may modify the error sent to Sentry, causing essential information to be lost and preventing Sentry from displaying the source map. If you're using a third party integration or other community-maintained packages, try to temporarily disable them to rule out this possibility. +We will collect known instances of conflicting third-party packages here: +- `posthog-js` versions from `1.207.4` to `1.229.0` (fixed in `posthog-js` version `1.229.1`)