Title is the post

  • Lycan@beehaw.org
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    Yeah. Beehaw isn’t on version 0.18 and Jerboa isn’t compatible with anything below that version, so I figured that’s why I went from no crashes to a bunch of 'em. I switched to Liftoff for now.

  • giloronfoo@beehaw.org
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    I had a couple crashes.

    It might have something to do with the update haveing changes that require Lemmy 0.18 and Beehaw is still running 0.17.4.

    I assume they’re waiting for the 0.18.1 version that restores support for captchas.

    • Unruffled [he/him]@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Initially, Jerboa was crashing for me whenever I clicked on any link. Turned out it was because I had disabled the default Chrome browser in Android (I default to use Mull, a Firefox fork) and it seems to be a dependency because the second I re-enabled it, Jerboa stopped crashing. So that’s something to check - there must be a dependency somewhere.

  • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    There were tons of crashing complaints so I stayed on the previous Jerboa version until my instance upgraded to 18.0.

    Haven’t had any crashes since updating but the app is starting to feel less polished, doing a lot of reloading and no longer returning to the last position in a thread when pressing back… will likely jump ship when some more 3rd party apps finish baking.

    • marx2k@beehaw.orgOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Yeah each time I respond it either crashes or brings me to the top of the thread

  • maggio@discuss.tchncs.de
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    What version are you currently using?

    I think the app is getting better with every update, and the latest version 0.0.35 is quite good.

    Remember that the app is still in an development stage.

    • marx2k@beehaw.orgOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’m on 0.0.35. Just noticed this last night and this morning.

      I get that it’s in development and that’s fine. I was just wondering if it was me or them ;)

  • flatbield@beehaw.org
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Other related posts:

    My experience is that 0.0.35 crashes a lot, but looks a lot more finished. Also the default view settings seem ignored but I can manually to whatever I want. I have always found posting unreliable on both the old and new apps. I use the PWA (Progressive Web App) for posting or just do it on my workstation. Hoping 0.0.35+ stabilize either by new releases OR Beehaw updates will fix some of the issues. Some say that 0.0.35+ just does not work on Beehaw until they migrate to a new server version (probably next week or so), but I do not have that issue.

  • I haven’t experienced any crashes. I’m just getting annoyed with it resetting the view when I rotate my phone by accident. It takes me back to Local and changes my filter back to default. Painful.

  • Banzai51@midwest.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    My problem with the app is that it won’t respect my default view (subscribed, new). But neither will Connect.

    Growing pains.

    • ryanlovescooljeans@beehaw.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      That’s weird. Because when I open the app, Jerboa says that my instance is on version 0.174 (or maybe 0.17.4) and that I need to contact my admin to upgrade to 0.18. I’ve been getting this message very time I log in for the last few days.

      Sounds like you’re damned if you do and damned if you don’t.