Is anyone else getting reports that Voyager is crashing frequently? I’m using Voyager version 1.27.0 on my Android phone, and I’m using the native app, not the PWA.

This issue has persisted for about a week now, even after several reboots. I have also tried clearing the application cache, with no results.

  • Sentau@feddit.de
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    I haven’t faced this issue. Is there any more information you can provide¿? Does the app actually crash during usage¿? Maybe this a Samsung thing.

    • radix@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      No, but I do notice that it takes longer than it used to for the content of the app to return when I switch away from it and switch back. While the content loads, it’s just a black screen, I think. I’ll try to remember to take a screenshot of it next time it happens.

    • radix@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Huh. I think that might be a different thing because my app doesn’t bug out or anything, it just gives me that notification and is relatively slow to return to content. Also, I’m on Android 13 on Samsung.

      • radix@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I did recently update my phone. Maybe that was it. Unfortunately, I don’t know of any way to downgrade it. Also, I would expect others to have similar issues if that were the case. It seems unlikely that I’m the only Samsung user on Voyager.

        • FelipeFelop@discuss.online
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          There have been reports of Samsungs on the newest OneUI giving that message with React apps and some notifications.

          That is how I guessed you had a Samsung.

          Sorry, I haven’t heard how this can be resolved l, it might need Samsung to do an update.