Work around: upgrade to 0.0.35 and avoid crashing

curioushom@lemmy.one to Jerboa@lemmy.ml – 41 points –

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!

30

You are viewing a single comment

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.

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

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.

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

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

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!

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').

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.