breautek commented on issue #1846: URL: https://github.com/apache/cordova-android/issues/1846#issuecomment-3347855535
It is very likely nothing Cordova (or you) can do. Cordova simply uses the installed webview version, which is a separate package that users can update through Google Play. Cordova does not link to the chromium library directly. It interfaces with the Android SDK via webview APIs. The actual webview library can be anything and may vary by device, but is is typically chromium. Because this appears to be a crash inside Chromium itself, I would recommend reviewing https://www.chromium.org/for-testers/bug-reporting-guidelines/ to learn how to report issues to Chromium. They may require additional information however. If your clients are raising concerns, you're best response at this time will likely involve instructing how your clients can make sure they are using the latest webview version, by ensuring that the `Android System Webview` package is up to date. > We are targeting a minimum sdk version 24 and a target sdk of 35 Cordova's min SDK is also 24, but the latest chromium webview builds are using min SDK of 29. This means SDK 28 and earlier devices may not have access to the latest webview versions available. So if the crash is happening on any of these devices, they may forever be affected as Chromium seems to have dropped support for those API levels. https://source.chromium.org/chromium/chromium/src/+/main:build/config/android/config.gni;l=75 Even if a particular usage pattern from the java webview API is the root cause, Chromium should be handling errors gracefully instead of fatally crashing, with error feedback to hint on the problem. Since it is not, and instead fatally crashing, it would be virtually impossible to actually trace the root cause without chromium debug symbols. And the root cause may not be related to actual webview usage. If you know the reproduction steps and can reproduce locally, then it may be worth building a debug version of the webview component, but building chromium is extremely resource intensive requiring around 100gb of free space. On linux, a quad-core with 16gb of ram will take more than 24 hours to compile and will require swap space on the linking phase. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
