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
@ljdawson@lemmy.world were you able to recreate the issue? I went through the settings and could find nothing that I could have done that would lead to this issue. All I have changed since installing the app is changing fonts and font sized. Almost all other settings are whatever they were by default.
Hell there comments in this very thread made by you and me that don’t load up in sync. https://lemmy.one/comment/2596964.
If you have not been able to recreate the issue, I will make a post enquiring as to if others are facing the same issue or if it is some problem on my end
I think I might have figured this out
Have you set a language in your profile?
I will try changing the language but there does seem to be a subtle difference in our cases. He couldn’t see the comments on the official website but I can. I will still try the solution though
Let me know how it goes!
I tried some things out and I have learnt a few things.
- Changing the language settings(and including every language) did not solve the issue.
- I reinstalled the app and before logging in, viewed this post and was able to load and view all comments.
- After logging in, I was not able to view all the comments of this post. By switching to the anonymous lemmy.world feed I am able to see the comments again.
- I also tried to view the comments before restoring my settings and after restoring my settings. The outcome in both cases was the same
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.
Link to the comment?
There is this comment as well (not mine) which I cannot see/expand on sync but can on other apps.
Hmm so your comment is collapsed if you open the whole thread but clicking expand works
Clicking expand does not work on my end though. When I click to the expand the comment, I get a ‘no messages found’ pop up at the bottom and the comment just disappears
Just tried on your instance and it’s working fine too.
You haven’t accidentally set some filters have you?
No filters set as far as I am aware. I will try to link a video of the issue if possible.
https://files.catbox.moe/zzxj8q.mp4
Video showing the bug