Skip to content
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

Merged
merged 3 commits into from
Jul 5, 2022

Conversation

vaind
Copy link
Collaborator

@vaind vaind commented Jun 29, 2022

closes #839

#skip-changelog

@vaind vaind requested a review from bitsandfoxes as a code owner June 29, 2022 06:47
@bruno-garcia bruno-garcia self-requested a review July 5, 2022 12:06
@bruno-garcia
Copy link
Member

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

@vaind
Copy link
Collaborator Author

vaind commented Jul 5, 2022

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3

@vaind vaind merged commit 6ae8941 into main Jul 5, 2022
@vaind vaind deleted the fix/log-error branch July 5, 2022 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SDK internal error logged through Debug.LogError
3 participants