Clicking into comments section redirecting to totally different thread

oSillyScope@sh.itjust.works to Jerboa@lemmy.ml – 49 points –

The app works well for the most part, but every now and then, when I tap to get into a comment section, it will go to the comments of an entirely different post. Backing out and trying a second time has worked every time so far. I'm running the app from my Pixel 6 pro if that matters.

14

Contrary to the other comments, I think this issue still persists. It happened to me multiple times today, and I am using 0.0.39 from F-Droid. Can't tell about 0.0.40.

interesting. as mentioned before, this issue completely disappeared for me around about v0.0.37 or 38.

iirc, i do seem to remember that the issue involved stale overlay popup screens when jerboa didnt get a reply from the server in time. but, I cant seem to reproduce the issue at all anymore, so...?

the v0.0.40 f-droid build of jerboa is complete and just waiting to get into the distribution repo. would love to hear if an update improves anything.

I will report back if it solves the issue. Had it happening a lot yesterday, like 1 out of 3 times.

This used to happen to me an older version but since upgrading to 0.0.40 I've not experienced this anymore

As others have noted, this was an issue that was frequently with Jerboa ~v0.34 or so with Lemmy v0.17.x and was attributed to the buggy websockets API. It initially stopped happening to me once lemmy.world upgraded to Lemmy v0.18.x and I got on Jerboa v0.37 or so... and most reports of it died down as well.

But in the last couple days, I have been seeing it as well. Including today. I'm now running Jerboa v0.40 against lemmy.world with a v0.18.2 build... so it's not websockets anymore it must be a different underlying cause. But I definitely do confirm your report of seeing the wrong post and fixing it via reloading, though I can't explain why. I also use liftoff and voyager via m.lemmy.world and I haven't seen the problem there. I assume it's a local bug in Jerboa this time, rather than a protocol issue.

So anyhoo, you're not alone in seeing this and although folks are correct to say that a similar issue was already fixed... it's possible to see this with fully updated Jerboa. In fact, I think it must be a bug that was introduced somewhere between v0.38 and v0.40.because it stopped happening for a while after things upgraded away from Lemmy v0.17.x and the jerboa versions form around that time.

this has occasionally happened for me on older versions of jerboa. I am currently on the v0.0.39 f-droid build and this issue has completely vanished.

also, my 'home' instance is running mainline lemmy v0.18.2, so that may make a difference under certain circumstances when using particular versions of jerboa and your home instance experiences congestion.

edit: your home instance (sh.itjust.works) seems to be on lemmy v0.18.2 - so, barring any weirdness on your lemmy server, its likely just your version of jerboa.

That's why I stopped using the app and switched to liftoff until the issue is fixed.