-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
captureException does not send exception #100
Comments
Hey, So to your issue, YES you also need to setup Sentry in the main process since we pipe everything through the main process to not have any "frontend" xhr going on. We use electron One thing I find strange is, that |
I am seeing a possibly similar issue. I am attempting to test my integration by calling
|
We have just released v3.0.0 of the SDK which includes a lot of changes and improvements since this issue was opened. If you can still reproduce this with v3, please open a new issue and I'll look into it. |
I am experiencing two issues in the renderer context
captureException
||captureMessage
does not send anything, but the functions do exist, the network tab shows no activitySentry.captureException
outside of the function where I initialize sentry,captureException
doesn't actually exist. PrintingSentry.captureException
returns nullFor testing purposes I am only running this on the renderer right now and am on version 0.7.0
Here is a video explaining my issue and showing my code:
https://www.useloom.com/share/61aabfd9a655435896544403d168903d
The text was updated successfully, but these errors were encountered: