Android Users: Are you experiencing multiple unexplained app crashes today?
Here is the solution that worked for me:
https://www.reddit.com/r/techsupport/comments/mb24zj/multiple_apps_keep_crashing_on_android_phone/
^ This isn't the first time Android System Web View has borked things, IIRC.
The other solution listed in the thread which I did not try is to uninstall all updates for Chrome and disable the app. (My Chrome was already disabled.)
@voltronic The textra notice is what clued me in. Of course, if I was paying attention to CoSo, I would have known sooner. Lesson learned. NEVER LOOK AWAY FROM CoSo.
My troubles started in the middle of reading the exchange about this between @voltronic and @ecksmc this morning so I had the fix in front of me exactly when I needed it!
@misterfive @voltronic @ecksmc you did not look away from CoSo. That was my error. I looked away. 😉
@SimplyZippy
I wasn't using the CoSo app, but I tried it on a hunch that something screwy was going on with web integrations. It turns out that the nature of that app makes it a good canary in a coal mine for this bug.
yeah, I saw this on CoSo yesterday, so today when all my devices were like "update for android system webview available" I noped right outta that...
@opie
It will just update itself when you're not looking though. Really frustrating as you can't disable this or tons of things break.
either of you know if this has been resolved?
I haven't updated webview on any of my devices, and the update still shows 22 Mar as last updated date...so I'm thinkin no?
(my apps do not auto-update)
@opie @voltronic it has been resolved on my wife's phone and mine seems to have escaped. Both phones current on all updates and apps updated.
@SimplyZippy
Opposite situation here. Wife's phone never had the issue (same exact model and OS version; both auto-update). I did the lounge procedure on mine as described in the screenshot from the play store reviewer and all has been well since.
I had Chrome disabled on my phone; she did not. Not sure if that would have anything to do with it or not.
^ This was NOT a permanent solution though, as Webview updated itself again and the problem returned.
What seems to be working now is this more involved procedure: