-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
"Java exception was raised during method invocation" error after React navigation on Android OS with FacebookMobile brwoser #15065
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
Comments
Hello @eshelsil, thanks for filing this. Unfortunately, we are not actively developing Sentry v7 anymore. You could try to ignore this error setting |
Same issue in @sentry/react': '8.47.0' |
We can add this error message to our default ignore errors list. I'm a bit worried about filtering out false positives though, so I'll take a look if we can be a tad smarter about it. For anyone experiencing this issue: For now, you can use |
) Filters out an unactionable error thrown by the Facebook Mobile browser web view. Closes #15065
A PR closing this issue has just been released 🚀This issue was referenced by PR #15430, which was included in the 9.2.0 release. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
7.93.0
Framework Version
18.2.0
Link to Sentry event
https://carefam.sentry.io/issues/6213106599/events/1a108b7f986349929f9de9866abdcb10/
Reproduction Example/SDK Setup
Steps to Reproduce
Expected Result
Actual Result
Getting multiple errors on Sentry.
Only on FacebookMobile browser on Andorid OS
The error is triggered from Sentry lib, so it is too generic to archive:
Issue Title:
Error
Object.init()
Error:
Java exception was raised during method invocation
StackTrace:
in Object.init at line 37:42346
In App
at line 37:40603
In App
../../node_modules/@sentry/browser/esm/helpers.js in sentryWrapped at line 97:17
This error happens immediately after navigation (auto navigation triggered by business logic, not by user click).
The user UX is unaffected, so this is just noise that Sentry is creating for us, and no safe way to ignore it.
Any help here?
Did anyone experienced a similar issue?
The text was updated successfully, but these errors were encountered: