-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Let me enable logging #970
Comments
Setting For main process native crashes or abnormal exits, the event is not sent until the next app startup since the process exits immediately. |
I took another look and maybe this could have been filed in another repo because the line that makes all the difference is this But another thing surprised me in your answer: should I expect an event to be sent for abnormal exits? Because I don't see anything and assumed that was the reason and that events would only be sent for |
I have not seen this before. Do you have a minimal example that reproduces this? I've checked with the latest version and setting
Yes:
|
Problem Statement
I have an issue where my app crashes but no report is generated by Sentry. I want to understand Sentry's behavior but by default no logs at all are emitted. The configuration has a
debug
option but it seems to only log at error or warning level. I am not able to understand what Sentry does or what the issue is that prevents my app's crash from being reported.Solution Brainstorm
Reading the
@sentry/utils
source code I was able to figure out that I can enable more verbose logging withbut this does not seem to be documented anywhere. Can you offer an API or configuration option for this?
side note: by enabling this, I found out that my app's crash is registered as an "abnormal" exit and not a "crash". I still don't know why that is but at least now I have some information to continue investigating.
The text was updated successfully, but these errors were encountered: