this post was submitted on 14 Jul 2023
6 points (100.0% liked)

Voyager

5607 readers
264 users here now

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

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! ๐Ÿ‘‡

Number of sponsors badge

๐Ÿ’™

founded 1 year ago
MODERATORS
aeharding@lemmy.world
aeharding@midwest.social
aeharding@vger.social
6
Installing the PWA from a self-hosted Voyager instance [FIXED] (nc.gnzl.cl)
submitted 1 year ago* (last edited 1 year ago) by gnzl@nc.gnzl.cl to c/voyagerapp@lemmy.world
10 comments fedilink hide all child comments
 

I recently self-hosted Voyager and it was a very painless process, I'm very pleased!

I noticed some strange behavior: When I navigate to my Voyager instance from Chrome, everything works as expected. When I install the PWA from Chrome, the list of Lemmy instances doesn't match my CUSTOM_LEMMY_SERVERS variable; it's the same list as vger.app. Then, if I navigate from Chrome to my Voyager instance, the list is now also the same as vger.app. None of this happens if I install the PWA from Firefox (it seems that Firefox installs PWAs differently from Chrome though; it doesn't show up on the app drawer, for example).

I suspect the PWA doesn't actually come from my server when I install it from Chrome. Is this what's happening? Or am I doing something wrong?

EDIT: this issue is now fixed, build the Docker image from the source code to try it out. Thank you @aeharding@lemmy.world!

top 9 comments
sorted by: hot top controversial new old
[โ€“] aeharding@lemmy.world 3 points 1 year ago (1 children)

This is a bug. See: https://github.com/aeharding/voyager/issues/124

[โ€“] gnzl@nc.gnzl.cl 2 points 1 year ago (1 children)

I see, thank you! And thanks a million for your work on Voyager, it's one of the most impressive web apps I've seen and used.

[โ€“] aeharding@lemmy.world 3 points 1 year ago (1 children)

Thanks! Should be fixed now, try it out.

[โ€“] gnzl@nc.gnzl.cl 2 points 1 year ago

It works! Replying from my instance using the PWA right now. Thank you so much!

[โ€“] habanhero@lemmy.world 3 points 1 year ago (1 children)

Could it be a cache thing?

[โ€“] gnzl@nc.gnzl.cl 1 points 1 year ago

It is indeed a cache issue. When I clear the cache I can start over - go to my Voyager instance, see the custom Lemmy servers I defined, and install the PWA. When I load the PWA though, my list of Lemmy servers changes to the same list you see on vger.app. My suspicion is, then, that Chrome doesn't install the PWA from my server (maybe from vger.app?), and that installing the PWA "overwrites" my Voyager instance and I see this overwritten version from that moment on.

[โ€“] elvith@feddit.de 2 points 1 year ago* (last edited 1 year ago) (1 children)

Maybe it's a bug with vger, maybe a cache/Chrome thing but it might also be a config issue.

When a web app wants to be installable, it needs to serve a file that tells the browser some things about itself - the manifest. If you visit your own instance on your server and take a look at the HTML source code in the browser (or use the dev tools), you should see a line like this:

<link rel="manifest" href="/manifest.json">

This tell the browser where to find the manifest. If you open said file, it should contain a line with the start link that gets invoked when you start the PWA. In this file, you should see a line like this with the link:

  "start_url": "/?source=pwa",

Make sure that this link points to your installation and not to vger.app

As I don't host vger myself, I don't know if and how you can change the values there or what should be the correct link, but this might get you started to track down the error.

[โ€“] gnzl@nc.gnzl.cl 1 points 1 year ago

Thank you! I'll dig into this.

[โ€“] gnzl@nc.gnzl.cl 1 points 1 year ago

I should add that I'm talking about Chrome on Android 13.

load more comments
view more: next โ€บ