Connect for Lemmy App

2767 readers

11 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago

MODERATORS

kuro_neko

[Possible Bug] Post not displaying all comments (lemmy.world)

submitted 2 years ago by [email protected] to c/lemmyconnect

6 comments fedilink hide all child comments

Hello, just picked up the Connect app and I've been enjoying it the most of any Lemmy app so far. However, I've been getting the following strange behavior, which may be a bug:

Viewing a specific post (https://lemmy.world/post/2104570) shows that there are (at time of writing) 76 total comments, but actually scrolling through reveals only ~37-40, even after expanding collapsed ones. Navigating directly to this post in a web browser reveals more comments than are shown in the app (still less than 76, around 65 or so, but I assume this is some other bug with Lemmy). Reloading the thread does not fix it and this has persisted across 2 days by my checks. I don't have any instances or users blocked, and I don't think that blocking communities would lead to this behavior (I haven't blocked the one in question). Am I missing something?

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 2 years ago* (last edited 2 years ago) (1 children)

This is one of the biggest issues that still affects Connect. It is most noticeable when it is your own comment that does not show. I have seen a few threads about this issue but I don't know if any comment was made by the dev on the issue

[–] kuro_neko 8 points 2 years ago (2 children)

Hi, thanks for the feedback! I did some investigation and it looks like this is sort of a Lemmy issue sort of a Connect issue. Looks like the API always returns the comments from the same page so any comments after the limit are lost. Using that linked post as an example check out these API calls:

I checked through the Lemmy Github and found this issue https://github.com/LemmyNet/lemmy/issues/3585 ([Bug]: Pagination doesn't work for GetComments if max_depth is set) so I think it's just a matter of not setting max_depth.

Anyways all of that to say it should be fixed in the next release!

[–] [email protected] 3 points 2 years ago

Sweet, thanks for the info! Looking forward to it as always :)

[–] [email protected] 2 points 2 years ago

Excellent! Thank you for your quick work.

load more comments