Live data from Hacker News

Google confirms an issue with WebView is crashing many Android apps (Fixed)

xda-developers.com

1–10 of 45 posts

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#2
There is a misconception that removing Android Webview is "fixing" the problem. The proper word is that removing the updated Android Webview is "a temporary workaround" until an updated Android Webview is released.

You cannot remove Android Webview because it is an essential part of Android. By "removing" the package, you are removing the latest update and revert back to the old (and probably insecure) version of Android Webview that came with the initial Android version of the phone.

In the end, Google eventually released a new package now, so you can perform the update of Android Webview to the latest version.

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#4

The problem is, I didn't issue an update on my android phone this week. I don't even have a Google play account and use ApkPure. Yet this morning my applications started to break. How did the update occured on my phone ?

IIRC system components can be OTA updated in the background. The only way to get around that is to use a de-googled android distro.

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#5
post #2

There is a misconception that removing Android Webview is "fixing" the problem. The proper word is that removing the updated Android Webview is "a temporary workaround" until an updated Android Webview is released. You cannot remove Android Webview because it is an essential part of Android. By "removing" the package, you are removing the latest update and revert back to the old (and probably insecure) version of And…

Dont see an update option for this app in the app store. It says last release was March 12th. How exactly do I get this update?

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#6
Experienced this this morning on my Pixel 1. Woke up to several apps in a crash loop every few seconds and most others crashing on startup. After a reboot didn't solve anything I thought perhaps my (older) phone had suffered a RAM failure since I hadn't updated anything in several days. After finding an article about the issue I updated Chrome which corrected the issue.

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#7
post #2

There is a misconception that removing Android Webview is "fixing" the problem. The proper word is that removing the updated Android Webview is "a temporary workaround" until an updated Android Webview is released. You cannot remove Android Webview because it is an essential part of Android. By "removing" the package, you are removing the latest update and revert back to the old (and probably insecure) version of And…

Dont see an update option for this app in the app store. It says last release was March 12th. How exactly do I get this update?

I was able to just do a Chrome update to solve the issue on my phone.

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#9
post #2

There is a misconception that removing Android Webview is "fixing" the problem. The proper word is that removing the updated Android Webview is "a temporary workaround" until an updated Android Webview is released. You cannot remove Android Webview because it is an essential part of Android. By "removing" the package, you are removing the latest update and revert back to the old (and probably insecure) version of And…

Dont see an update option for this app in the app store. It says last release was March 12th. How exactly do I get this update?

No action required if you’re not experiencing issues.

If you’re affected and not able to update, trying to “uninstall updates” for “Android System WebView” will revert it to ROM-included unaffected version and solve it.

Re: Google confirms an issue with WebView is crashing many Android apps (Fixed)

#10
post #8

How does something like this make it to production? I couldn't reply to any work emails for the greater part of the evening yesterday. Adds more evidence to the case of "never use Google for your business".

I guess the team has Q1 OKR to meet and/or error budget to spend? Either way, it's bad.

I am not saying the bug would have been prevented if the team operates differently. Brown paper bag release happens. However, the way this incident blew up suggests that the bad release made it to too many users in too short of a time, exactly the behavior incentivized by meeting (or exceeding) an OKR while having some spare error budget.

Post reply on HN