this post was submitted on 23 Jun 2023
41 points (100.0% liked)

Jerboa

10299 readers
2 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
41
Work around: upgrade to 0.0.35 and avoid crashing (lemmy.one)
submitted 1 year ago* (last edited 1 year ago) by curioushom@lemmy.one to c/jerboa@lemmy.ml
28 comments fedilink hide all child comments
 

I've been seeing a lot of posts about people being stuck between server (lemmy 0.18) and client (Jerboa 0.0.33—35) versions (not installed from IzzyOnDroid and logged in) with Jerboa crashing. Here's a way to avoid that issue while still being able to log in and browse both Lemmy 0.18 or older instances.

  • Add IzzyOnDroid repo to F-Droid
  • Delete app data from Android app info (edit)
  • Uninstall current version of Jerboa
  • Install 0.0.33 IzzyOnDroid version of Jerboa
  • Set phone to Airplane mode
  • Open Jerboa and use the hamburger menu to add your account
  • Fill in server, username, and password
  • Turn off Airplane mode
  • Login

You'll get a old server version notification of your server hasn't updated but you'll be able to use Jerboa regardless of server version.

Hope this helps!

you are viewing a single comment's thread
view the rest of the comments
[–] curioushom@lemmy.one 1 points 1 year ago (1 children)

Go to app info in Android and delete the app data, hope that works. I think I did that, I'll add that as a step, it won't hurt.

[–] DivergentHarmonics@sopuli.xyz 2 points 1 year ago (1 children)

Force stop -- clear cache -- clear storage -- airplane mode -- No luck.

[–] curioushom@lemmy.one 1 points 1 year ago (1 children)

So you cleared storage and then installed 0.0.33? That crashed? Or were you able to login with 0.0.33 then update to 0.0.35 and then it crashed?

If it's the latter, then I'm out of ideas, sorry!

[–] DivergentHarmonics@sopuli.xyz 2 points 1 year ago* (last edited 1 year ago) (1 children)

I did various things already. Upgraded to 35 yesterday, which made it crash. Today i uninstalled and re-installed older versions and the latest several times, tried different combinations of cache wiping and offline startup. ~~As i see it seems to work for other people, i'm a bit worried. Wanted to wait for the next update.~~

Edit: It works! It had to do with that old issue with Orbot in VPN mode. Android 11 ... some applications seem to expect VPN to be active and won't work until i turn TOR on and off. -- Written from Jerboa 0.0.35. :-)

[–] curioushom@lemmy.one 1 points 1 year ago

Nice! Glad you got it figured out.