Hi everyone, I’ve opened on cordova-docs PR #1552 (https://github.com/apache/cordova-docs/pull/1552) to document WebView 52 as the minimum supported version in the Android support table, linking to PR #1571 on cordova-android.
It also explains WebView updates and their limits on older Android versions: the final supported release is 119 for Android 7 and 138 for Android 8–9, with links to official Chromium sources. Feedback is welcome. Regards, Manuel > Am 15.11.2026 um 17:18 schrieb Manuel Beck via dev <[email protected]>: > > Hi everyone, > > I’ve updated PR #2043 (https://github.com/apache/cordova-android/pull/2043) > by using: > - Android 7.0 / API 24, WebView 52 > - Android 10 / API 29, WebView 74 > - Android 16 / API 36, WebView 133 > All three use AOSP images. A new instrumentation test records the loaded > WebView provider and requires WebView 52.x on Android 7.0 to preserve > minimum-version coverage. The other jobs use their image’s bundled WebView. > > All three jobs passed > (https://github.com/apache/cordova-android/actions/runs/43733508009), with 17 > tests each, no failures or skips. Reports and device logs are uploaded, and > the workflow can be rerun independently of the unit tests. > > The targeted startup regression tests and their fix remain in PR #2036 > (https://github.com/apache/cordova-android/pull/2036). They are not included > in these 17 tests, so the successful runs do not mean that the intermittent > startup issue is resolved. > > I’ll document the supported WebView versions separately in a cordova-docs PR. > > Regards, > Manuel > >> Am 13.11.2026 um 01:48 schrieb Bryan Ellis via dev <[email protected]>: >> >>> Does that necessarily mean we should support WebView 51? >> >> In my opinion, we should support WebView 51 because it was documented >> by Android. >> >> But, we don't technically have anything documented except for what was >> written in a pull request. If that is also considered apart of our source of >> truth, then go with 52 for now. >> >> In the future though, I think our minimum supported version should be >> determined using one of the following sources. (My preferred order) >> >> 1. Android's official website >> - Developer Documentation >> - Release Announcements/Notes >> - Change Log >> - Android Developer Blogs (?) >> 2. A non-upgraded AOSP image >> >> If the version is documented on Android's official website, we have an >> official reference to base our support minimum on. >> >> If Android does not explicitly document the version, which is usually >> the case, we can use the version available in an AOSP image, with a >> non-upgraded WebView. >> >> My assumption is that Norman obtained version 52 from an AOSP image. >> >> I'm not sure whether Android updates its images before shipping them, >> and if that is why there was a version difference from documentation. >> >> My main preference is to keep the minimum supported WebView version >> aligned with the SDK's baseline. >> >> If everyone prefers 52, as it was written on the ticket then it should be >> fine. It is only one version difference. >> >> Regards, >> Bryan >> >> >> On Thu, Nov 12, 2026, at 4:00 PM, Manuel Beck via dev wrote: >>> Hi Brian, >>> >>> the documentation mentions Chrome 51 as the version that introduced Chrome >>> as a WebView provider on Android 7.0. Does that necessarily mean we should >>> support WebView 51, or should we use WebView 52 as stated in Norman’s PR >>> #1571 (https://github.com/apache/cordova-android/pull/1571)? >>> >>> I would suggest pinning the minimum-version CI job to Android 7.0 with >>> WebView 52, unless we agree that 51 should also be supported. I have >>> already reproduced the startup issue from #2036 >>> (https://github.com/apache/cordova-android/pull/2036) with WebView 52 on >>> Android 7.1.1. Android 7.0 with WebView 51 or 52 has not been tested yet. >>> >>> Once the community agrees on the minimum, we can document it and validate >>> that exact version in CI, alongside the current Android configuration. >>> >>> Regards, >>> >>> Manuel >>> >>> (Reply partially created with the help of AI) >>> >>>> Am 11.11.2026 um 17:42 schrieb Bryan Ellis via dev >>>> <[email protected]>: >>>> >>>> I could be wrong, but I believe the correct minimum supported WebView >>>> version is 51. While the ticket says 52, Android's official >>>> documentation suggests 51. >>>> >>>> https://developer.android.com/about/versions/nougat/android-7.0#webview >>>> >>>> >>>> On 2026/11/11 15:39:16 Manuel Beck via dev wrote: >>>>> Ok, thanks for pointing that out. So should we document WebView 52 as the >>>>> minimum for cordova-android 15? Any other voices for it? >>>>> >>>>>> Am 07.11.2026 um 14:08 schrieb julio cesar sanchez >>>>>> <[email protected]>: >>>>>> >>>>>> When we bumped to SDK 24, Norman said the minimum WebView was 52, not 69, >>>>>> so I think that’s the version we should document that we support >>>>>> >>>>>> https://github.com/apache/cordova-android/pull/1571 >>>>>> >>>>>> But that adds a good reason to bump the min SDK to a version with a newer >>>>>> WebView version for Cordova-android 16. >>>>>> >>>>>> El El sáb, 7 nov 2026 a las 11:40, Manuel Beck via dev < >>>>>> [email protected]> escribió: >>>>>> >>>>>>> Thanks for clarifying. I think we should document the minimum supported >>>>>>> WebView version separately from the minimum Android API level. >>>>>>> >>>>>>> Would Chrome/WebView 69 be the agreed minimum for cordova-android 15 >>>>>>> onward? If so, I would close #2036: the startup issue reproduced with >>>>>>> WebView 52–59, but was not observed with WebView 60 or newer in the >>>>>>> tested >>>>>>> versions. >>>>>>> >>>>>>> We could document the minimum WebView version in the Android Platform >>>>>>> Guide, together with the last WebView versions available for Android 7–9 >>>>>>> and the fact that these Android versions no longer receive WebView >>>>>>> updates. >>>>>>> This would be more useful than stating which Android version currently >>>>>>> receives the latest WebView, since that requirement will change over >>>>>>> time. >>>>>>> >>>>>>> That would clarify our existing support expectations while keeping any >>>>>>> minimum SDK increase for the next major in a separate discussion. >>>>>>> >>>>>>> In general it would be good to have some documentation somewhere about >>>>>>> it. >>>>>>> >>>>>>>> Am 05.11.2026 um 17:33 schrieb Norman Breau via dev < >>>>>>> [email protected]>: >>>>>>>> >>>>>>>> the min SDK bump should be another thread to get a buy-in , but I'm >>>>>>>> also >>>>>>> not sure if we are ready to start targeting the next major yet. A PR >>>>>>> could >>>>>>> be made but it would have to sit until we are ready to start developing >>>>>>> for >>>>>>> the next major. >>>>>>>> >>>>>>>>> This would make development much more easier. >>>>>>>> >>>>>>>> This in itself is not really a valid reason either. We should compile a >>>>>>> list of reasons why upgrading to API 28 is necessary or in what way it >>>>>>> will >>>>>>> be an improvement that has value that warrants increasing the minimum >>>>>>> API >>>>>>> level. >>>>>>>> >>>>>>>> On 2026-11-05 11:03 a.m., Manuel Beck via dev wrote: >>>>>>>>> Yes, you are totally right. Should we make a another discussion for it >>>>>>> or already vote? I would be for minimum supporting Android 9 (API Level >>>>>>> 28). This would make development much more easier. >>>>>>>>> >>>>>>>>>> Am 05.11.2026 um 15:58 schrieb Norman Breau via dev < >>>>>>> [email protected]>: >>>>>>>>>> >>>>>>>>>> Sorry for the spam but -- Google currently uses API 29 ( >>>>>>> https://source.chromium.org/chromium/chromium/src/+/main:build/config/android/config.gni;l=63) >>>>>>> for their minimum API level for the android webview component. Meaning >>>>>>> that >>>>>>> latest webview releases now is only available for users on Android 10 or >>>>>>> later. >>>>>>>>>> >>>>>>>>>> Not saying we should match that requirement, but it's definitely >>>>>>>>>> worth >>>>>>> considering bumping our minimum in the next major release. Based on >>>>>>> https://apilevels.com/ >>>>>>>>>> >>>>>>>>>> API 26 - 99.2% usage >>>>>>>>>> API 28 - 98.2% usage >>>>>>>>>> API 29 - 96.6% usage >>>>>>>>>> >>>>>>>>>> We'd have to investigate what kind benefits that would yield, but it >>>>>>> would also bump our "minimum" webview version probably quite >>>>>>> significantly, >>>>>>> leading to better JS API support. I'm sure there would be a lot of >>>>>>> simplification we could start doing as well in the native code. >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>>> For additional commands, e-mail: [email protected] >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> >>>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
