You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
try{// ...}catch(e){constfetchError=newError(`Failed to fetch`);fetchError.cause=e;Sentry.captureException(fetchError);}
Previously the title of the error in sentry would be: Failed to fetch, but now the title is whatever is in e.message.
Expected Result
Title of error in Sentry UI is the error thrown, not the message of the error in the cause field. In the example above it should be "Failed to fetch", instead of e.message.
Actual Result
Unfortunately I can't share what we see in our sentry UI publicly, but the title of the error that we see is e.message
Product Area
Issues
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered:
Hi, @johndoherty - thanks for reporting! This is actually the same issue as #59679, so I'm going to close this in favor of that, since a bunch of conversation has already happened there. Feel free to comment if you have stuff to add. (Actually, I have a question for you, but I'm going to ask it over there so we can keep discussion in one place.)
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Create a linked error in sentry in the browser:
Previously the title of the error in sentry would be:
Failed to fetch
, but now the title is whatever is ine.message
.Expected Result
Title of error in Sentry UI is the error thrown, not the message of the error in the
cause
field. In the example above it should be "Failed to fetch", instead ofe.message
.Actual Result
Unfortunately I can't share what we see in our sentry UI publicly, but the title of the error that we see is
e.message
Product Area
Issues
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: