Changes requested to the Sentry documentation

Extensions
1

We followed the guide to setting up Sentry as per this link.

The documentation says to use this config:

Sentry.init({
  dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0',
  defaultIntegrations: false,
});

And to disable those defaultIntegrations because:

We recommend disabling the default integrations to be sure it will run within a Web Worker.

We’ve been having hundreds of thousands of errors a week from our Shopify Checkout Extension and been working with Sentry to figure out the problem.

We raised this issue with Sentry to get help: Receiving many "Crashed in non-app: [native code] in reportError" errors in Shopify Checkout Extensions · Issue #16584 · getsentry/sentry-javascript · GitHub

The Sentry team say the problem is the defaultIntegrations: false disables some useful integrations for filtering noisy errors. You can find these integrations in their documentation.

We’ve changed our integration to their suggestion:

Sentry.init({
        defaultIntegrations: false,
        integrations: [
           Sentry.eventFiltersIntegration(), // applies default filters for known useless errors
           Sentry.dedupeIntegration(), // this avoids sending the same error twice, just in case
        ]
    });

Can I request some help from the Shopify engineering team to:

  • Help define which integrations should or should not be disabled (maybe you know something that Sentry does not about why this is wrong?)
  • Documentation of what is or isn’t supported
  • Updating the documentation accordingly

Thanks!
Ed

1 Like
Sentry receives many errors about crashes in non-app "reportError"