Closed IcyEagle closed 4 days ago
Hi @IcyEagle, Thanks for reaching out.
Could you verify, maybe through debugging, that this is in fact a supressed exception? If so, supressed exception are currently not supported/reported on/to sentry in our stable versions. We have, however, implemented support for them already in our branch for the upcoming 8.0 release in #3396 . There's currently 8.0.0-alpha.4 out for it. You could give that a try if you'd like, you can find it here.
Hope this helps. If you have any more questions/issues, don't hesitate to let us know.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Integration
sentry
Java Version
21
Version
7.9.0
Sentry instance
24.3.0 self-hosted
Steps to Reproduce
Your stacktrace may look like this:
Expected Result
Stacktrace is properly parsed and sent to the Sentry server. Then it could be read and linked with Source Maps.
Actual Result
Sentry only reads the first 2 lines, the error message and 1 stacktrace line. It probably stops at
Suppressed
and ignores what comes after that.