Description
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?
Self-hosted/on-premise
Which SDK are you using?
@sentry/react
SDK Version
9.19.0
Framework Version
React 18.3.1
Link to Sentry event
N/A
Reproduction Example/SDK Setup
Sentry.init({
dsn: "https://[email protected]",
defaultIntegrations: false,
release: APP_VERSION,
environment: "production",
attachStacktrace: true,
initialScope: {
tags: {
extension,
shop,
},
},
// Allow us to capture IP address so we can reference them in internal logging
sendDefaultPii: true,
});
The code we've got deployed is this application: https://github.com/mention-me/ShopifyAppV2
And we've deployed it as a Shopify Checkout Extension: https://shopify.dev/docs/api/checkout-ui-extensions
Steps to Reproduce
We're really struggling to reproduce it. I know it's happening thousands of times a day. It doesn't appear to be having a major impact on our end users.
It's easy for us to cause an error which does get tracked successfully but doesn't cause this error. We're unable to see what is causing this specific problem.
Some things we know which might be useful:
- Shopify extensions run in a sort of sandbox - so we don't have access to things like the
navigator
object in the browser. - The reportError function is available from the sandbox.
- It doesn't appear to occur with every error, e.g. it's quite easy for the app to be configured such that error responses are thrown, but they don't trigger this specific reportError bug.
- I don't know if it's a Sentry problem or a Shopify issue, so I've raised a question in their community forums too: https://community.shopify.dev/t/sentry-receives-many-errors-about-crashes-in-non-app-reporterror/17274
Expected Result
Either:
- No errors reported for code that is irrelevant to us.
- More context on what the errors are
- A fix for the errors.
I'm not sure what's best!
Actual Result
This reportError
issue appears in our logs a lot:
Here's an example log, with some client and IP details blurred out:
Metadata
Metadata
Assignees
Type
Projects
Status