19

We are experiencing large number of crashes recently especially in Samsung, LG devices (mostly Android 10, 11).

The crash report in Play Console says : backtrace: #00 pc 0000000001bb1ed8 /data/app/~~8ql0flEwCl8tpQXEDqYp-w==/com.google.android.webview-nHOdMOK9WY-Nv2RB5HLF7A==/base.apk!libmonochrome.so (offset 0x352000)

#00 pc 0000000002a299cc /data/app/com.android.chrome-vWnAqmlPpzO9GGYC3iaeyg==/base.apk (offset 0xd49000)

Has anyone else been experiencing this and can anyone point out to what might be causing such a thing?

soripk
  • 191
  • 1
  • 1
  • 3
  • This is mostly due to a Chrome / WebView bug that pops up every once in a while. I assume your app uses Ads so the Banner Ads use WebView internally which might have been the cause. (Even if you do not use Ads, there might be some other library which might be using WebView somewhere). There's nothing you can do particularly except waiting for the team to push an update & the users update the WebView app. – Darshan Feb 25 '21 at 05:31
  • 1
    Experiencing the same issue today. If anyone found a solution, please let me know. – Stefa Jul 20 '21 at 18:22
  • same solution from Varad, uninstall Android System Webview update – RacsO Jul 23 '21 at 10:59
  • I have also got this error on Vitals – Vikas Pandey Dec 01 '22 at 10:07
  • We need to notify our affected users about the resolve that themselves need to do. Is there a way to catch this excepton and notify. – Vikas Pandey Dec 01 '22 at 10:21

2 Answers2

13

Recently I experienced same issue on webview.

Problem was from last update of Android System Webview. When I disabled it, App webviews were working properly.

So the only solution we got was to inform & direct users via notification to update their Chrome and Android System Webview apps to latest version, to overcome this issue.

I hope this might help others.

Varad Mondkar
  • 1,441
  • 1
  • 18
  • 29
  • 1
    Are you talking about this thread https://support.google.com/android/thread/103561027 ? – KAlO2 Aug 31 '22 at 10:28
  • Yes yes, but didn't knew they made this thread. Thanks for posting. – Varad Mondkar Sep 06 '22 at 07:43
  • so how do we get to know users who are experiencing this issue, so we can notify them only. – Vikas Pandey Dec 05 '22 at 05:39
  • @VikasPandey if you are storing your users ID in vitals/crashlytics/server crash logs, and you have user ID and their FCM mapping. You can send notification to all those users. In my case, our userbase is huge and almost every users where affected whose `Android System Webview` was on auto update. So we notified every users with steps to update their `Android System Webview` – Varad Mondkar Dec 06 '22 at 04:53
0

Play Console only shows: "[base.apk!libmonochrome_64.so]" and that it last occured on an Android 11 device. No further information. We don't use a Webview. MAYBE the Google Map uses one.

Since only one user was affected in the last 28 days (5 crashes) and we have a working customer support, I ignore the error as long as nobody reports. Maybe I did that myself when testing and the crash isn't even noticeable...

The incredible Jan
  • 741
  • 10
  • 17