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
[–] godless@latte.isnot.coffee 3 points 1 year ago (2 children)

Never crashed for me on login, but there are some showstopper bugs:

You can't up/downvote a post when you enter the comment view.

Replying to a PM from the inbox will instead send the reply to yourself.

[–] JohnnyCanuck@sh.itjust.works 4 points 1 year ago (1 children)

What version? I haven't seen this. (currently on 34, from Google Play)

[–] godless@latte.isnot.coffee 2 points 1 year ago (1 children)

https://github.com/dessalines/jerboa/releases

With an alpha version that's releasing updates every 3-8 days, it's generally better to get it directly from the source. Google play takes one week to verify new releases, which doesn't matter for established apps, but with rapid release cycles in active development, it can be annoying.

They are also pushing updates to F-Droid though if you want to have some app store behind it, they publish updates within hours of releasing.

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

But I'm not running into showstopper bugs like you're mentioning...

[–] godless@latte.isnot.coffee 1 points 1 year ago

That's good for you, I suppose, and the reason why bug trackers exist. They are not universally applicable.

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

I upvoted your comment from the comment view and it registered, I verified on the web.

I'm replying to your comment from the inbox, let's see if it goes to you or me!

[–] godless@latte.isnot.coffee 3 points 1 year ago* (last edited 1 year ago) (1 children)

Comment reply works, and upvoting comments as well.

It's replying to DMs that's bugged, and voting on posts that causes the crash.

I've reported them both with screenshots and video evidence, you can check it here:

https://github.com/Coffee-Viking (scroll down to the bottom to 'reported issues').

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

Ah gotcha! Voting on posts and comments are working fine for me but I haven't ever messaged anyone and missed the DM bit in your comment, my bad.