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!

  • godless@latte.isnot.coffee
    3·
    1 year ago

    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.

    • curioushom@lemmy.oneOP
      2·
      1 year ago

      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·
        1 year ago

        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.oneOP
          1·
          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.

  • Noedel@lemmy.ml
    2·
    1 year ago

    I was really hoping 0.18 would make things better but now it has both the app and the website unstable.

    Any timeline on 18.1?

    • curioushom@lemmy.oneOP
      1·
      1 year ago

      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.

        • curioushom@lemmy.oneOP
          1·
          1 year ago

          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!

          • ᗪIᐯEᖇGEᑎTᕼᗩᖇᗰOᑎIᑕᔕ@sopuli.xyz
            2·
            1 year ago

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

  • RandomLegend@lemmy.dbzer0.com
    2·
    1 year ago

    Doesn’t work for me sadly…i am on an instance that is on 0.17. I updated to 0.35 and it didn’t work. Now whenever i install some older version it automatically crashes no matter what.

    I cleared caches, deleted files, restarted, tried airplane mode - nothing works.

    I can only start the 0.35 version if i download the apk directly from the website of izzy and nothing else works now…