Forum Discussion
Enrollment failing - Could not update Webview
We have reports of devices no longer being able to enroll.
Our policy has a FORCE_INSTALL of Android Webview (com.google.android.webview), with a minimum version set to 593815300.
Reproduced here with an Acer ACTAB10KB24.
If I remove the minimum version requirement, I can enroll the device, and also update the webview to 139.0.7258.158. Why isn't the configuration with minimumVersionCode set working?
We have previously enrolled many of these, but from our logs the latest successful enrollment was on the 16th of August (2025).
6 Replies
Stupid question: Is it during enrollment or after enrollment? I never heard of this being possible to be set as an enrollment "option" anywhere but maybe i missed that yet.
The reason i ask is, it make a big difference what does it trigger and how. So can you explain that to me where and how you set this minimum version to this specific app?
Sorry, I was unclear. It is part of the policy applied. If the initial policy pushed to the device has an applicationPolicy with a FORCE_INSTALL of Android Webview (com.google.android.webview) and minimumVersionCode set to 593815300, this device will not complete the wizard. It will fail with the "Could not update Android System WebView".
If we leave the minimumVersionCode unset, the wizard completes, and if we update manually we now get versionCode 733905133. System package on tested device is versionCode 535912833.
I don't understand why the package can't be updated initially. There should be a compatible package available matching minimumVersionCode 593815300 since we could install 733905133 manually right?
never seen such app policy yet being available. Can you link me to it as it'S something new to me.
But how about if the version 593815300 is not available anymore (because of Google took it away maybe because of found critical bugs), did you try latest verison as minimum version?
