New issue
Advanced search Search tips

Issue 644613 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Webview disabled; update install rolls back to previous version

Reported by rusty.i...@gmail.com, Sep 7 2016 
THIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB
BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE!

Device name: nexus 6p
Android version: 7.0
WebView version (from system settings -> Apps -> Android System WebView): trying to install 53.x (Sept 6); keeps rolling back to version 51.0.2704.90
Application:Webview is broken preventing Gmail from working 
Application version:

URLs (if applicable):



Steps to reproduce:
(1) hit enable on Webview in play store
(2) hit install 
(3) check version and see it rolled back instead of installing. 
(4) rinse and repeat

Expected result:correct versions installed for personal and work profile 


Actual result: old version
bugreport-NRD90T-2016-09-06-11-13-24.zip
4.7 MB Download

Comment 1 by torne@chromium.org, Sep 7 2016

Status: WontFix (was: Unconfirmed)
On Android 7.0, Chrome is used as the WebView implementation by default. You get a new WebView when Chrome is updated. The WebView package is disabled to prevent redundant updates wasting bandwidth and disk space; it's enabled automatically if Chrome is disabled, to ensure you continue getting WebView updates either way.

You aren't supposed to be able to enable it manually; a future version of the play store will disable this button for WebView to prevent the confusing behaviour where it disables itself, but we didn't quite get this change done in time for the initial 7.0 release, sorry.

Comment 2 by rusty.i...@gmail.com, Sep 7 2016 

FYI - I was emailing with a Google engineer and part of the issue is that I had Chrome Dev installed in my personal profile and regular Chrome installed in my work profile. Installing Chrome Dev in both profiles fixed the 2 different versions of WebViewer that were trying to load from the different Chrome browser versions.

Thanks for the fast reply!

Comment 3 by torne@chromium.org, Sep 7 2016 

I'm the same Google engineer. :)

The problem is not caused by the webview versions mismatching - *all* users always use whichever version is selected by the primary user, even if it's not installed for that user, and under normal circumstances this works fine (it's possible to load a not-installed package in this case). However, with multiprocess *also* enabled, the renderer process for the multiprocess webview is unable to start because of how the service is looked up; we're working on that, but since multiprocess is a developer-only feature at the moment it's not critical. For normal users who don't have multiprocess enabled, it always works fine.

Comment 4 by boliu@chromium.org, Oct 27 2016 

 Issue 659999  has been merged into this issue.

Comment 5 by tobiasjs@chromium.org, Dec 9 2016 

 Issue 672643  has been merged into this issue.
►

Sign in to add a comment