-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
JniAndroid$UncaughtExceptionException: Native stack trace: #20147
Comments
Sentry issue: WORDPRESS-ANDROID-2TTG |
Sentry issue: JETPACK-ANDROID-HNP |
Sentry issue: JETPACK-ANDROID-HN0 |
Sentry issue: WORDPRESS-ANDROID-2T29 |
Noting that this often appears as a new crash due to the fact it comes up in numerous different areas. All of these Sentry reports show a comment |
Sentry issue: JETPACK-ANDROID-FQB |
Sentry issue: JETPACK-ANDROID-J8R |
Sentry issue: WORDPRESS-ANDROID-2V0V |
Sentry issue: WORDPRESS-ANDROID-2V85 |
Sentry issue: WORDPRESS-ANDROID-2TKN |
Sentry issue: WORDPRESS-ANDROID-2V5H |
I collected all the reports of JniAndroid$UncaughtExceptionException from Sentry and linked all of the ones I could find that included
While this often appears as a new crash as @SiobhyB noted, the oldest issue I could find first appeared in 23.7.1. Keeping Medium Priority per the matrix. |
Given that the crash is affecting app versions as old as 21.5 I think that the recent surge is unlikely related with our app.
also looks similar with this Google issue but I opened a new one since the recent crashes might indicate that a recent WebView version is causing this. |
Checking the issue on Android Vitals the spike started on January 26th around the time that |
Just a heads up that the issue on the Google tracker is marked as |
Following up on our discussion (ref p1708008049877909/1707711421.715029-slack-C012H19SZQ8) and the responses from Google we think that the issue is more of a crash reporting change and not a new crash. |
While investigating this issue I noticed that some of the Chromium related crashes appear when we try to get the default user agent We can probably avoid this type of crash by catching the edit: raised for discussion internally pcdRpT-5Us-p2 |
Sentry Issue: WORDPRESS-ANDROID-2VFY This issue is an ANR but it seems to have been caused by the same root cause related to the chromium library. I'm linking to this issue so we can have the full investigation history about the main root cause and the possible solutions and workarounds implemented. |
Sentry Issue: JETPACK-ANDROID-JSB |
Sentry Issue: JETPACK-ANDROID-JVQ |
I took another snapshot of the old and the new crash report numbers and I believe that our overall crash rate is not affected significantly since the spiking new issue almost matches the drop of crashes in the old issue.
I think there is no action on our side other than expecting the new WebView M123 sometime in mid-March. |
Sentry Issue: JETPACK-ANDROID-HPJ |
Sentry Issue: WORDPRESS-ANDROID-2WA6 |
Sentry Issue: JETPACK-ANDROID-MPQ |
Sentry Issue: WORDPRESS-ANDROID-2WA4 |
The expected new Webview release arrived a few days ago. There is no change in the recorder crashes yet but it may take some time to rollout and notice a difference 🤞 |
Sentry Issue: JETPACK-ANDROID-KAM |
I've added the webview version in the crash reports with #20533 to be able to measure if the new release has an impact on the crashes. |
Sentry Issue: WORDPRESS-ANDROID-2VYY |
The WORDPRESS-ANDROID-2VYY ANR is related to the fix :( I'll track the user agent retrieval related ANRs in #12259 |
Following this.... |
Sentry Issue: JETPACK-ANDROID-QC5 |
A lot of people still complaining in the Google Issue Tracker that the crash is still happening in recent versions of WebView. It looks like a new ticket was opened related to that, but I don't have access to it, so it's hard to track if they are working on a fix. |
I do not have access to the new issue either and left a follow up comment. |
Sentry Issue: WORDPRESS-ANDROID-2XTT |
Sentry Issue: JETPACK-ANDROID-RT0 |
is there any solution or workaround for this crash? |
Unfortunately, there is not. As noted above, this is an issue in the Android |
Sentry Issue: JETPACK-ANDROID-J3B
The text was updated successfully, but these errors were encountered: