Show the raw error and/or stack trace to the user.
Show a generalized error.
Show a user friendly error message mapped to error codes or types.
Can we improve the UX here?
Can we stop showing raw rpc errors and/or stack traces to users?
Should we implement a client only tracing system, where we can provide users trace IDs in their error messages that they can use to communicate their issues. We can then use the IDs to correlate the report to a log.
We handle displaying errors in a few ways -
Can we improve the UX here? Can we stop showing raw rpc errors and/or stack traces to users? Should we implement a client only tracing system, where we can provide users trace IDs in their error messages that they can use to communicate their issues. We can then use the IDs to correlate the report to a log.