-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gatsby: Sentry.captureException() doesn't work unless reinitialized #5727
Comments
Hey, thanks for writing in! Does this also happen when using a |
Same thing with |
Ah yes we did do this - #4857, but not sure why manual calls are not working. Will backlog, but PRs are welcome for anyone who would like to help out! |
I can't reproduce it. Can I get detailed configuration files? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Same thing is happening with Next.js. |
@moy2010, please open a GH issue and fill out a new bug report, we'll take a look! |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/gatsby
SDK Version
7.12.1
Framework Version
Gatsby 4.14.1
Link to Sentry event
No response
Steps to Reproduce
Initialize the plugin in
gatsby-config.js
:On the client (e.g. inside a component):
Expected Result
An exception should be sent to Sentry.
Actual Result
Nothing is sent to Sentry (nothing at sentry.io or in the browser's network tab) unless calling
Sentry.init({ dns: 'XXXX' })
before callingSentry.captureException()
. Unhandled exceptions are properly captured, but not manual calls toSentry.captureException()
.The text was updated successfully, but these errors were encountered: