-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
react-hydration-errors inbound filter doesn't catch all errors #45363
Comments
Assigning to @getsentry/support for routing, due by Friday, March 3rd at 5:00 pm (sfo). ⏲️ |
We have shipped a small fix a few hours ago. Do you think you can test again and see if it is filtering out? 🙏 |
but yes you are right...we are only filtering the most common cases as listed here sentry/src/sentry/relay/config/__init__.py Lines 122 to 126 in 2413734
|
Routing to @getsentry/team-web-sdk-frontend for triage, due by Tuesday, March 7th at 9:14 am (sfo). ⏲️ |
It's fixed now, thanks! 🙏🏻 |
Environment
SaaS (https://sentry.io/)
Version
No response
Link
https://prisjakt-ab.sentry.io/issues/3933815010/?project=1228836
DSN
No response
Steps to Reproduce
n/a
Expected Result
With #45188, React hydration errors should be filtered out directly. This is sadly not the case.
Actual Result
After removing client-side hydration error filtering, this is what happened:
The text was updated successfully, but these errors were encountered: