just updated to the v0.0.35 f-droid build and jerboa started to consistently crash at seemingly random times. likewise, I would get web UI error notifications while using the web frontend.

did a little testing and noticed that it may be related to the “show avatars” setting being enabled.

turning “show avatars” off and saving the settings seems to have eliminated the issues on both web and app.

will continue to test and update the post if needed. any others able to confirm or refute this particular issue might be helpful.

edit: there are still crashes related to editing a post, but crashes while scrolling through posts and comments seem to be much reduced. any feedback is welcome.

edit2: further poking suggests the underlying cause may be jerboa not handling server response timeouts well. turning off avatars may reduce the number of API calls and therefore the number of potentially mishandled timeouts. crash frequency is likely variable as a result of variable server load. if others also experience reduced crash frequency with avatars turned off then I can either create a github issue or add info to an existing one.

  • godless@latte.isnot.coffeeEnglish
    7·
    1 year ago

    Make sure you report the issues on github as well, so the devs can actively work on them.

    https://github.com/dessalines/jerboa/issues/ (just check if a duplicate already exists). Is the instance where your account is registered already migrated to 0.18.0? Apparently using Jerboa 0.0.35 with 0.17.4 (and older) causes problems due to a change in API handling. At least that was the reply I got to some of my reported issues, since my home instance is not yet upgraded.

    • qprimed@lemmy.mlOPEnglish
      4·
      1 year ago

      I am on lemmy.ml which is currently at v0.18.0 so it should be cool. wanted to crowd source some feedback before I open a github issue - dont want to waste dev time on non-reproducible ghosts.

      • godless@latte.isnot.coffeeEnglish
        2·
        1 year ago

        Well, if it crashes your phone repeatedly, it’s already worth reporting even if it’s not affecting anyone else for now. Better to fix it early than to leave a critical bug in the code that might affect other functions further down the line, you never know how and where they eventually interlink.