-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Remix SDK not reporting server errors to Sentry #8216
Comments
Hi @MoSattler thanks for writing in and thanks for the detailed information!
Hmm looks like something weird is going on. I can see that you're passing the three hooks needed to the routing instrumentation. but one of the 4 params required here, is missing. Maybe something funky happens to I'm not sure if this is related to the error not being caught, though. We'll have to take a closer look at this but at the moment we're very busy with other issues (🔥 🚒 ). I'll backlog this with high prio so that we take a look at it soon. |
possibly related: #8200 |
Thank you @Lms24! Let me know if you need anything else from you side. |
Hi @MoSattler, thanks for the issue report!
This log is misleading and should not be on the server-side, so I opened a PR to fix it. (#8269) I could not reproduce the bug locally, with the steps you mentioned in the report. To trigger the action I used:
And can see the thrown error from the Is there a specific setup or deployment target where you are seeing this issue? |
Hi @onurtemizkan - I can reproduce it in 7.53.1, but it seems fixed in 7.54.0. I guess it was related to #8265. Thank you for your help! |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/remix
SDK Version
7.53.1
Framework Version
Remix 1.16.1
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
When turning on
debug
, it will also give outExpected Result
Unhandled error that breaks actions or loaders should be reported to sentry
Actual Result
Nothing is reported to sentry
The text was updated successfully, but these errors were encountered: