-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
Displaying error name instead of Error code #2958
Comments
Assigning to @getsentry/support for routing, due by Thursday, April 20th at 10:13 am (sfo). ⏲️ |
Routing to @getsentry/team-mobile for triage, due by Monday, April 24th at 9:18 am (sfo). ⏲️ |
Hey @arielelkin, did you check out our custom error descriptions? Please reopen this issue, if it doesn't solve your problem. |
@philipphofmann thanks for your response. Unfortunately custom error descriptions are not a viable suggestion, as we have hundreds of different errors; this involves creating a lookup table of error codes and duplicating their names just for the sake of reporting them to Sentry. Could you please re-open the issue? I don't have the option on my side. |
Call into Swift to get the error description for Swift errors to get meaningful error names instead of only the error enum code. To avoid sending PII the SDK strips parameter values and doesn't send the swift error name for struct based Swift errors. Fixes GH-2958
Call into Swift to get the error description for Swift errors to get meaningful error names instead of only the error enum code. To avoid sending PII the SDK strips parameter values and doesn't send the swift error name for struct based Swift errors. Fixes GH-2958
@arielelkin, #2960 should solve your problem. It would be great if you could give us some feedback before we merge the PR. |
Call into Swift to get the error description for Swift errors to get meaningful error names instead of only the error enum code. Fixes GH-2958
Problem Statement
We are tracking errors in our macOS app using Sentry. Our errors are usually represented by Swift or C enums.
When they get reported, we just see the numerical error code rather than the error name. This means we need to then go look up the precise error name.
For example:
is reported as "com.firebase.appCheck Code: 0", but to know what Code 0 means we need to look up that error enum.
Is there a way to display the error name rather than the numerical error code in Sentry ?
Thanks
Solution Brainstorm
Since we pass the error object to the sentry SDK, the sentry SDK should report the enum's value (via introspection) and its
localizedDescription
(if any).The text was updated successfully, but these errors were encountered: