this post was submitted on 22 Jun 2023
19 points (100.0% liked)

Jerboa

10295 readers
9 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
dessalines@lemmy.ml
19
Issues with 0.0.35 (lemm.ee)
submitted 1 year ago by awesome_person@lemm.ee to c/jerboa@lemmy.ml
17 comments fedilink hide all child comments
 

I immediately updated to v0.0.35 as soon as i saw it on GitHub, to realize i get kicked out of the app for having an account on a Lemmy instance still running 0.17. Reinstalled v0.0.34, except that now crashes on startup, probably since the default instance it uses is on 0.18.

Do I have to use 0.0.35 in anonymous mode until my instance updates to lemmy 0.18, or is there some workaround?

you are viewing a single comment's thread
view the rest of the comments
[–] Coeus@coeus.sbs 4 points 1 year ago (2 children)

I had the same message when I opened .35 but the app continued to work like normal. My server is on .17

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 year ago (1 children)

Just note, there are two things I know of that cause crashes with a 0.17 server:

  • mark as read
  • login

As long as you don't do either of those (i.e. you're already logged in on a previous version), things should largely work.

[–] thatcasualgamingguy@lemmy.nerdcore.social 2 points 1 year ago (1 children)

For me, saving a post also crashes the app. But when I open the app again the post is saved. So at least the saving itself works.

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 year ago

Yeah, it's a problem largely with understanding the response. A lot of little things changed, and Jerboa doesn't use all of them, so the breakage can seemingly be random.

[–] shortwavesurfer@monero.town 2 points 1 year ago (1 children)

I got the error and it would not stay on my "subscribed" feed so i logged out and back in - or tried to anyway - only to discover i cant login. Writing this from the web ui and somewhat annoyed. Downgrading until my instance updates i guess.

[–] Coeus@coeus.sbs 1 points 1 year ago* (last edited 1 year ago)

It seems like there are a lot of bugs going around but Jerboa works well