Voyager semi broken from outdated webview
I got an automatic Voyager update from F-droid and now it complains of an out of date Webview version and tells me to update Webview from the Play store. But I don’t use the Play store and don’t want to enroll an account there. I get all my apps from F-droid. Is there a fix or workaround from this? thanks. Android 14 on Motorola Stylus 5g 2023 if that matters.
The play store says it was just updated a few days ago. The comments are scary though. Yikes.
Open Webview (rooted device)
That onexalways fails for me to download the webviews. Guess i’ll have to look at the script, since Aurora has no webview update in queue.
You have to pull down to refresh on the ‘Updates’ page in Aurora for it to check for updates (or I have to, anyway.)
Also, if it helps, I installed Open Webview via a Magisk module installed through the IzzyOnDroid Magisk repo in the MMRL app (from F-Droid.)
Thanks, but that’s the same zip that fails for me.
Eh, in the next few days sometime.
Gotta keep your webview up to date! There’s alternatives as described in the comments but yeah, having a version of Chromium older than a year old is pretty dangerous/insecure.
I think most ‘normal’ android users never really think about it because Google keeps their webview up to date automatically, but if you dont use Play Store this can be easily overlooked. Really important for device security though.
Edit: As for why Voyager requires System WebView >= 140… Android recently overhauled safe area insets and their rollout was kinda botched with poor backward compatibility. This is a side affect unfortunately.
Edit: As for why Voyager requires System WebView >= 140… Android recently overhauled safe area insets and their rollout was kinda botched with poor backward compatibility.
But the app works fine with a “too old” webview. Why warn about it?
And please do feature detection instead of useragent parsing, if you do require some newest/uncommon features (but better don’t require that).
And please do feature detection
I’m not sure how you’d do that with safe area insets. You could check for zero but some modern devices megitimately have zero safe area insets. Capacitor itself has to check Blink version for the SystemBars plugin.
But the app works fine with a “too old” webview. Why warn about it?
If you go into dark mode the status bar will be white with white text, because safe area doesn’t work properly.
solrize
aeharding