Voyager

8052 readers

40 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 2 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

Voyager semi broken from outdated webview (lemmy.world)

submitted 4 days ago by solrize@lemmy.world to c/voyagerapp@lemmy.world

15 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] aeharding@vger.social 1 points 4 days ago* (last edited 4 days ago) (1 children)

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 thei rollout was kinda botched with poor backward compatibility. This is a side affect unfortunately.

[–] MonkderVierte@lemmy.zip 1 points 4 days ago (1 children)

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).

[–] aeharding@vger.social 1 points 4 days ago (1 children)

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.

[–] MonkderVierte@lemmy.zip 1 points 3 days ago* (last edited 3 days ago)

Oh, didn't notice that, since i have set usage limits on Voyager.