this post was submitted on 24 Apr 2025
5 points (77.8% liked)

Voyager

6386 readers
109 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 2 years ago
MODERATORS
5
App broken? (discuss.tchncs.de)
submitted 2 days ago* (last edited 2 days ago) by CyberEgg@discuss.tchncs.de to c/voyagerapp@lemmy.world
 

Sorry that I cannot provide a more specific title, but the whole app seems to be broken. On the post tab I only get the error message "failed to load posts", on the profile tab it's "failed to load user profile", messages and notifications do not get loaded, no communities get listed, etc. Tried it with two accounts on different instances, neither account is banned, I can access everything in a browser iron other apps.

I installed the latest update after this error occurred, no changes.

Edit: app works again after de- and reinstallation, everything's back to normal.

top 5 comments
sorted by: hot top controversial new old
[โ€“] badbrainstorm@lemmy.world 2 points 2 days ago (1 children)

VPN? I've started getting those issues on a few servers

[โ€“] CyberEgg@discuss.tchncs.de 1 points 2 days ago (1 children)

No, no VPN, Proxy or similar.

[โ€“] acockworkorange@mander.xyz 1 points 14 hours ago (1 children)

When I get that, it usually means my instance server is rebooting or something of the sort.

[โ€“] tuna@discuss.tchncs.de 2 points 14 hours ago (1 children)

This was my thought as well because the problem resolves itself within a matter of minutes. However it doesn't make sense that OP would have the same problem for multiple instances, and could access each instance in the browser without issue. Also, our instance showed 100% uptime when I initially checked the post so I'm not sure it's that.

[โ€“] acockworkorange@mander.xyz 1 points 13 hours ago

Doh, I completely missed the part about multiple instances and working on the browser. Yup, something was afoot with the app.