I'm using an Android application utilizing system WebView. After Android OTA upgrade up to 6.0.1, WebView's major version was 47. As far as I have had some issues with this version (specifically, webview sporadically hangs, and there is a similar issue logged - Android WebView stops loading pages), I decided to look for a fix.
According to WebView beta community, there was available more recent release of 47 major version (47.0.2526.99) than I have had (I do not remember my former minor version exactly, but it was older than 47.0.2526.99). Then I decided to try to update webview in Google Play. Indeed it shown me that an update is available for System WebView and I made the update.
As a result I received "newer" WebView with major version 46! This is just illogical to me. So I'd like to know: how is it possible to receive version updates which are downgrades in reality?
Isn't this a mess? Shouldn't they prompt the user about exact version he will receive?
So the main question is: how one can ensure upgrade to the latest stable (or, at least, specified) version? If Google Play can provide outdated versions and even do not check if the device's already installed version is newer and overwrites it silently, then I just don't know what to think. Specifically I'd like to get the mentioned latest stable major version 47.
The 3-rd and the last question about the beta channel is voided now. It was absolutely unclear from the WebView Beta Community site, if stable WebView and beta WebView can live on the same device side by side, and if it is so, then how to embed one or another into an application. The answer is that installation of beta version means that the stable WebView will be replaced completely with the beta. This affects all applications using WebView, and this is definitely not how Chrome beta channel works (Chrome beta can work in parallel with stable versions and they do not interfere each other).