19
Voyager semi broken from outdated webview (lemmy.world)
submitted 7 months ago by 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
[–] 0 points 7 months ago (2 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).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 7 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •