this post was submitted on 07 Aug 2023
19 points (91.3% liked)

Voyager

5634 readers
79 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
 

I'm unable to expand the reply at the bottom of this conversation and it's unclear why. Tapping it shows the spinner to indicate it's trying, but then nothing. This behaviour occurs on iOS and Firefox on desktop.

Any ideas?

https://wefwef.app/profile/sh.itjust.works/c/voyagerapp@lemmy.world/comments/2352604

top 8 comments
sorted by: hot top controversial new old
[–] aeharding@lemmy.world 9 points 1 year ago (2 children)

This is definitely a Lemmy bug. We use child_count to determine if there are unloaded comments, but child_count is incorrect in this case. (says 3 children, only 2 returned)

[–] danielton@lemmy.world 6 points 1 year ago

I remember this happening on Reddit with Apollo as well, and Apollo would show a message explaining why no more comments loaded.

[–] AlmightySnoo@lemmy.world 4 points 1 year ago

it seems to happen with deleted comments

[–] NotSpez@lemm.ee 7 points 1 year ago (1 children)

Mom, I’m on TV! I mean Lemmy!

[–] We1chy@lemm.ee 6 points 1 year ago

Me too! Haha

[–] We1chy@lemm.ee 3 points 1 year ago

If it helps, since I created the post, for me it shows only 4 comments. So I have no idea why it would try to show more replies.

[–] LazaroFilm@lemmy.film 0 points 1 year ago (1 children)

There’s a badge on your settings. You either need to update or setup you WAP. You may also want to look into using the native app versions available for iOS and Android.

[–] HolidayGreed@sh.itjust.works 3 points 1 year ago* (last edited 1 year ago)

The screenshot was taken from Firefox on desktop, running the latest version 1.5.0. The badge is a prompt to install.

The same issue occurs on iPhone PWA 1.5.0, iPadOS PWA 1.5.0 and native application 1.5.0.

I have updated the original post with this info.