Arctic

355 readers

1 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

CreatureSurvive@lemmy.world

Clicking on some posts will open a seemingly unrelated post. (imgur.com)

submitted 6 months ago by quaff@lemmy.ca to c/arctic@lemmy.world

9 comments fedilink hide all child comments

I'm not sure what's going on, but I'm noticing on the latest beta, that some posts (haven't found a pattern) will open to a completely unrelated post.

Actually... usually it's related to !TenForward@lemmy.world, I'm not sure why (I could be wrong too). It's something I've noticed maybe 5-6 times in the last couple of weeks?

I've linked to a screen recording, hopefully it's obvious to you @CreatureSurvive@lemmy.world

you are viewing a single comment's thread
view the rest of the comments

[–] CreatureSurvive@lemmy.world 3 points 6 months ago (1 children)

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.

[–] quaff@lemmy.ca 1 points 6 months ago* (last edited 6 months ago) (1 children)

That’s great to hear! I’m glad you found the mismatched data 🙏🙏🙏 hopefully finding the root issue doesn’t cost you too many cycles 🫡

[–] CreatureSurvive@lemmy.world 3 points 6 months ago

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.