How to fix Android Webview bug that causes applications like Gmail to close

If you have an Android and applications like Gmail or Chrome close themselves, you should know that you are not alone. Multiple users are having problems with their Android phones, where certain applications are closed instantly, with no warning message or apparent reason.

Fortunately, this problem has an easy solution. The reason for these unexpected closings is in a wrong update of Android System Webview, an application that acts as a link between the browser and the applications. Google has reported the problem and has already submitted a fix. However, many users have found that their mobiles do not act normally. Here we leave you how to solve it.

How to avoid unexpected shutdowns and fix the Android Webview bug

Faced with the problem with Webview there are two options. On the one hand, uninstall the Android Webview updates and return to the previous version that is causing problems or simply update the Android System WebView application from Google Play and place the patched version from Google.

Android Webview bug

The ruling affects mobiles of different brands, as WebView is a Google tool present in all kinds of applications. Samsung’s own technical support recommends uninstalling the updates and restarting the mobile to return to normal.

To do this we must go to Settings> Applications> display the menu of the points at the top and select Show system apps> choose Android System WebView> select Uninstall updates.

Fix android Webview bug

Once Google has sent the updated and corrected version of WebView, users can also go to the Google Play application store, click on the settings menu in the upper left corner, go to ‘My applications’ and search for the update of Webview that will surely appear to update us. Another option is to search for Android System WebView on Google Play and download the latest update. Once installed, the system should return to normal.

Google also recommends updating the Google Chrome application to avoid possible related failures. The problem was initially detected on Tuesday the 23rd at dawn and the solution has arrived about seven hours later.

Leave a Reply