I am noticing this too. Do you have any filters and does the “unrelated” post contain them?
this post was submitted on 30 Apr 2024
1 points (100.0% liked)
Arctic
361 readers
6 users here now
Arctic is a Lemmy client for iOS built on pure Swift. It currently supports iOS 15+ and Lemmy v0.17+
Get the latest version on TestFlight, or check it out on the AppStore.
If you would like to support Arctic’s development, feel free to Buy Me A Coffee
founded 1 year ago
MODERATORS
The TenForward community I sub to is favourited, other than that, no fillers or anything done to it.
Weird, it must be something else then. I submitted feedback on TestFlight about it
This is a peculiar one that I have not seen before. Had you noticed this at all before the latest beta release? I cannot think of anything that changed in that build that would have affected this.
I see some odd issues here where the post you clicked is showing mixed data. The post content and community name is that of the c/technology post, but then the community icon is for c/tenforward.
I see the post was created by a mbin user, perhaps it is due to a federation issue, or maybe the mbin api has changed and I need to update support.
Next time you encounter this, would you mind checking some of these details such a as post creator instance, post content all matches, etc.
I’ll start looking into this, thank you for informing me!
It’s happened on a previous beta, I can’t remember if it was the last one or the one before that.
I had it happen again yesterday. Not related to those two communities. Same issues, the feed showed one thing, but with mixed data (I think the community thumbnail was displaying the post that actually loads). I’ll make another video when I see it again 🙏
Caught it again! Seems to be happening quite frequently now. I spot it by looking for mismatched community icons.
I spent all day trying to reproduce this issue without any luck. However I was finally able to track down where the mismatched data is being applied, and prevent it from happening, I’ll need to do a little more digging to find the root issue and properly fix it.
I might have time to finish this up tomorrow morning, if not I’ll definitely have a patch released sometime on Friday. Thank you for bringing this to my attention, it’s probably been hiding there in plain sight for a while now without being noticed.
That’s great to hear! I’m glad you found the root issue 🙏🙏🙏
Looking into it further, I’m not sure if I found the actual issue or not. However I did add some checks to try and ensure the prefetched data is not inserted in the wrong location. I’ll be releasing an update today, and it should hopefully resolve this issue.