-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
fix: use LogWarning instead of LogError for potential SDK errors #861
Conversation
Actually. Does it make sense to be an error? We'd like to warn the user that somethjing went wrong here so we can be aware |
It does make sense, that's why it was an error. Whether it should still be is up to you. See #747 (comment) update: clarified now - we will add a "Sentry: " prefix to avoid sending the error but still log it as LogError |
@@ -151,7 +151,8 @@ public ScopeCallback(Action<AndroidJavaObject> callback) : base("io.sentry.Scope | |||
} | |||
catch (Exception e) | |||
{ | |||
UnityEngine.Debug.LogError($"Error in SentryJava.ScopeCallback: {e}"); | |||
// Adding the Sentry logger prefix ensures we don't send this error to Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<3
closes #839
#skip-changelog