this post was submitted on 16 Jul 2023
50 points (98.1% liked)

Jerboa

10300 readers
14 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
[email protected]
50
Clicking into comments section redirecting to totally different thread (sh.itjust.works)
submitted 1 year ago by [email protected] to c/[email protected]
14 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

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.