Improve error handling for importer when WebView is out of date

[david-allison]

See:

• AnkiDroid import screen white screen for all deck formats (txt/csv/apkg) #19913 (comment)

AnkiDroid Version = 2.23.1 (3f3133b496b531383e9a6494f5a7704634935308)  
Backend Version = 0.1.62-anki25.09.2 (25.09.2 3890e12c9e48c028c3f12aa58cb64bd9f8895e30)  
Android Version = 10 (SDK 29)  
ProductFlavor = full  
Device Info = HUAWEI | HUAWEI | HWTAS | TAS-AL00 | TAS-AL00 | kirin990  
Webview User Agent = Mozilla/5.0 (Linux; Android 10; TAS-AL00 Build/HUAWEITAS-AL00; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/78.0.3904.108 Mobile Safari/537.36  
ACRA UUID = aed8344c-9c29-4b4b-8b94-de0c7b1a9f2b  
FSRS = 5.1.0 (Enabled: false)  
Crash Reports Enabled = true

My Huawei device (EMUI) blocks Google’s official WebView installation—only Huawei-signed WebView is allowed. I installed an updated Huawei-signed WebView build, which resolved the AnkiDroid import blank screen issue.

We have two options:

• Improve outdated WebView detection (may be hard - do we have a Huawei to test?)
• Improve error handling on the WebPage; suggest updating the WebView if feasible

[Fandroid745]

This is the approach that I am planning to take
Implement a check in pageFragment.kt
If it is a huawei/honor phone then check if the webview provider is valid.
if not then add an alert dialog to update the webview with a link for that in huawei app gallery.
is this correct?
if so I can go ahead with the pr

[xenonnn4w]

how you plan to test the same?

[Fandroid745]

I don't have a huawei phone,but I can mock the test to work on my phone. If the error message is displayed while importing after mocking the test then it works.

[xenonnn4w]

Sure, but ig mocking alone won’t fully validate this, since the failure depends on the actual WebView provider and Chromium version, not just device brand. Can we detect outdated / incompatible WebView in a vendor-agnostic way?

[AnEht]

I don't have a huawei phone,but I can mock the test to work on my phone. If the error message is displayed while importing after mocking the test then it works.

I have the problematic Huawei device (the one from #19913) and an unupdated Honor. I'm willing to help test after school （around UTC 13:00）

[AnEht]

I've reproduced this issue on my Webiew unupdated Honor device.

AnkiDroid Version = 2.23.1 (3f3133b496b531383e9a6494f5a7704634935308)  
Backend Version = 0.1.62-anki25.09.2 (25.09.2 3890e12c9e48c028c3f12aa58cb64bd9f8895e30)  
Android Version = 10 (SDK 29)  
ProductFlavor = full  
Device Info = HUAWEI | HONOR | HWCDY-H | CDY-AN90 | CDY-AN90 | kirin820  
Webview User Agent = Mozilla/5.0 (Linux; Android 10; CDY-AN90 Build/HUAWEICDY-AN90; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/78.0.3904.108 Mobile Safari/537.36  
ACRA UUID = 0e52b44d-f801-474c-ac5f-62095e71e8e8  
FSRS = 5.1.0 (Enabled: false)  
Crash Reports Enabled = true

[

](url)

[Fandroid745]

Sure, but ig mocking alone won’t fully validate this, since the failure depends on the actual WebView provider and Chromium version, not just device brand. Can we detect outdated / incompatible WebView in a vendor-agnostic way?

Yeah, I can add a check if the chromium version is lower than 90 then ask the user to update the webview in the alert dialog. I will then post the apk file in the comment thread for @AnEht to verify.

[david-allison]

We already have a check in AnkiDroidApp for an outdated WebView, we should figure out why this isn't working in this case

[Fandroid745]

We already have a check in AnkiDroidApp for an outdated WebView, we should figure out why this isn't working in this case

I found the check in acceptFileSchemeCookies function. It is only checking if webview exists or not using MissingWebViewPackageException.

[david-allison]

Ah, this is what I get for reviewing on my phone. Sorry!

This is in the startup path, but not in AnkiDroidApp:

Anki-Android/AnkiDroid/src/main/java/com/ichi2/utils/WebViewUtils.kt

Lines 34 to 54 in e3bcf44

	internal const val OLDEST_WORKING_WEBVIEW_VERSION_CODE = 418306960L
	internal const val OLDEST_WORKING_WEBVIEW_VERSION = 85
	/**
	* Shows a dialog if the current WebView version is older than the last supported version.
	*/
	fun checkWebviewVersion(activity: AnkiActivity) {
	val userVisibleCode = getChromeLikeWebViewVersionIfOutdated(activity) ?: return
	// Provide guidance to the user if the WebView is outdated
	val webviewPackageInfo = getAndroidSystemWebViewPackageInfo(activity.packageManager)
	val legacyWebViewPackageInfo = getLegacyWebViewPackageInfo(activity.packageManager)
	// TODO modify the alert dialog text to handle the usage of developer builds for system WebView
	if (legacyWebViewPackageInfo != null) {
	Timber.w("WebView is outdated. %s: %s", legacyWebViewPackageInfo.packageName, legacyWebViewPackageInfo.versionName)
	showOutdatedWebViewDialog(activity, userVisibleCode, R.string.link_legacy_webview_update)
	} else {
	Timber.w("WebView is outdated. %s: %s", webviewPackageInfo?.packageName, webviewPackageInfo?.versionName)
	showOutdatedWebViewDialog(activity, userVisibleCode, R.string.link_webview_update)
	}
	}

[Fandroid745]

Can I follow this approach?

Update the minimum supported WebView constants in WebViewUtils.kt
webview_version = 90 and webview_version_code = 443000000L.

change the return type of checkWebviewVersion to return a Boolean
Return true when the WebView is outdated and the warning dialog is shown, otherwise return false.

Call checkWebviewVersion in PageFragment

Stop webview intialization if it is outdated
If the function returns true, immediately return from onViewCreated and do not create or load the WebView.

[david-allison]

Why 90? The listed agent is 78

[Fandroid745]

Why 90? The listed agent is 78

Huawei uses higher version code compared to google so even though version 78 is lower than the limit of 85 the update dialog was not displayed because the versionCode for it is greater than the limit of 418306960L
allowing it to pass this check
if (versionCode >= OLDEST_WORKING_WEBVIEW_VERSION_CODE
so by increasing it to 90 along with increasing the version code we stop it from passing the check thereby ensuring the update dialog is displayed