I had this bug recently on beta 40 where I would reply to a comment on a post and my comment would show up. Then if I refreshed the post to load in new comments, my reply would be collapsed and clicking on it would lead to a 'no comments added' message. The comment would still be visible in the profile section and from other lemmy apps.
Edit : some photos as proof/example
Edit : This is not only an issue for my comments only, it is also issue for comments from other people aswell. Usually it seems to be an issue associated with the last comment of a thread where the these comments are collapsed in sync and when I expand them, no comments are added. But these actually exist and can be seen from other apps(voyager in my case). Oddly this does not happen for every comment thread but it happens with enough comments that it is noticable. I have not been able dig up any other commonilities between the disappearring comments other than the fact they appear at the end of comment chains/threads.
Device information
Sync version: v23.08.31-14:10
Sync flavor: googlePlay
View type: Slides
Device: hanoip
Model: motorola moto g(60)
Android: 12
Let me know how it goes!
I tried some things out and I have learnt a few things.
Edit : I changed the instance that the anonymous feed uses from lemmy.world to lemmy.one and was able to replicate the issue. It seems the issue lies how sync is fetching comments from the lemmy.one instance. I will try out if other instances run into the same issue
The 5-6 other instances I tried out did not face this problem. Just to be sure, I cleared the app's cache and user data, force stopped it and then viewed the post using lemmy.one as the base instance and was able to replicate the problem. @ljdawson@lemmy.world
So just to be clear it's only lemmy.one?
I have tested with around 20 instances. The popular ones like lemmy.ml, lemmy.world, etc, a few of the feddit.country domains and a few random instances. Lemmy.one seems to be the only one suffering from the issue. Now i haven't tested all the instances so maybe some obscure instance faces this problem but in my experience only lemmy.one suffers from the bug.
Gotcha thanks. I'll write this up as an issue on GitHub and see if I can replicate it my end.
Yeah no pressure. It was just bugging me as the issue was seeming very random and unreproducible. Thanks for all the work on the app