I've never seen a stack trace like that and have no idea how to troubleshoot. It didn't happen in Android 10 (SDK 29) or earlier. The app is built with androidx support library and SDK 30.
The phone where it has happened:
Samsung Note 10+ 5G running on SDK 30
Any pointers are appreciated.
That's all I could get from PlayStore:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> app-package-name <<<
backtrace:
#00 pc 00000000038621f0 /data/app/~~dDiCj_8810kb6DPfFJq1VA==/com.google.android.trichromelibrary_438909034-1CcX13lT2sfyKsCGVu4mkA==/base.apk!libmonochrome_64.so (offset 0x646000)
You may have downloaded the app improperly, and all you need to do is to reinstall the app to fix the crashing problem: Go to Settings > “Apps” or “Application manager” > Choose the app that crashes > Tap the “Uninstall” option to make it. Then you can go to Google Play Store to reinstall the app after a few minutes.
Observe the App Crash Suppose you have built an application with multiple activities or fragments or both then you need to observe and see which action causes the application to crash. This might sometimes help you automatically remember or recall what mistake was made and which part of the app is causing that. 2. Find the Stack Trace
Android vitals considers crashes excessive when an app: Exhibits at least one crash in at least 1.09% of its daily sessions. Exhibits two or more crashes in at least 0.18% of its daily sessions. A daily session refers to a day in which your app was used.
As we have talked about before, if you accidentally run into Android apps crashing, then you can try to uninstall Android System WebView on Google Play Store. Navigate to Google Play and Tap on the My Apps & Games. Then find Uninstall and go to Android System WebView.
No matter for what reasons, Tenorshare ReiBoot for Android provides one tap solution to repair Android system to fix app crash problems with 100% success. Launch ReiBoot for Android after installing and connect your Android device to your computer via USB cable.
As @Morrison Chang and @Tink have indicated in comments, the crashes have been related to Android System WebView that can be found at the following location in Play Store:
https://play.google.com/store/apps/details?id=com.google.android.webview
In my case the problem has been fixed after I've updated the above app with the release that Google has pushed to Play Store on 03/22.
Even though my application doesn't use WebView directly there are probably dependencies in the Android and Samsung libraries that my application relies on.
Google announced an incident for their own Gmail App. Users cannot launch the App. And it's related to the Android System WebView, which is more like a component for Android system but can be updated via Google Play. The issue was reported at 3/23/21, 7:05 AM But this issue is more than Google thought. Not only Gmail app will crash, many other Apps will crash too. Reddit thread for this.
Unluckily, our App is one of them, we saw live crash number going up and then going down. And we have many users complain about this. They just cannot open our App.
Luckily, Google fixed their bug and everything will be good if users update their Android System WebView app in Google Play.
We didn't catch this crash in Firebase Crashlytics, but we can see it in Google Play Console. And actually, I have no idea about this crash log. I have to Google it to see if it's only me or for everyone. Thanks for posting this issue here so I know I'm not alone.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With