52
Voyager constantly crashing (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by to c/voyagerapp@lemmy.world
29 comments fedilink hide all child comments
 

So, apparently for no reason, my Voyager app started crashing this morning whenever I touched any of the replies to my comments.

I tried with and without VPN, custom DNS, automatic DNS, Rethink enabled and disabled, and it just keeps crashing.

Yes, I cleared data, un-installed and reinstalled, and it is still happening.

Anyone else having this issue? I thought I'd ask here first before opening a bug report on Github.

Edit: Forgot to mention I'm on version 2.8.0 from Github.

Edit 2: Available version from F-Droid, 2.6.0, does not preset this issue.

Edit 3: Finally got to reporting it. Sorry for the delay.

all 31 comments

sorted by: hot top controversial new old
[–] 32 points 2 years ago (1 child)

Dude it's like billions of miles away and 50 years old, give it a break

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 2 years ago* (last edited 2 years ago) (3 children)

    May be for you, as the post mentions, this just happened to me for the first time. With all due respect, I'm choosing to keep this civil and just ignore your ignorant comment (see what I did there?).

    Edit: Gotta give it to you. This went entirely over my head. In my defense... BS, I have no way to defend myself. Good one, you totally got me.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    (see what I did there?)

    Ironic how you didn’t see what they did there

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] 16 points 2 years ago* (1 child)

    As the app is suggesting, open a github report with the crash data. That is the only way to help the dev resolve this because even if others are having the issue, more data is always better.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 11 points 2 years ago (2 children)

    13 minutes from crash report to deployed bug fix. That is an insane response time @aeharding@vger.social.

    https://github.com/aeharding/voyager/issues/1458

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
    • [+] 7 points 2 years ago* (last edited 2 years ago)
    [deleted]
  • permalink
  • fedilink
  • source
    •
    [–] 6 points 2 years ago (2 children)

    What version? I have 2.7.1 on iOS with no problems.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 years ago

    I apologize I did not mention that part, thanks for the reminder. I'm on version 2.8.0 for Android. Direct download from Github, so not even from a store. I'll try installing it from F-Droid to see if that could be it. Thank you both.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 3 points 2 years ago (2 children)

    Honestly, atleast you all know how to open issues on GitHub. The amount of times I see people try to report issues in Discord, either for other apps or my own, is kind of staggering, and when you tell them to open an issue in GitHub, the response is often “well I don’t know how to use GitHub, GitHub is complicated, why is everything on GitHub? Why can’t you just give us the app instead of requiring us to compile from source‽ wah wah wah wah wah wah wahhhhhh”

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 years ago (1 child)

    Most people come from "normie" apps. When they find themselves in an environment such as github, codeberg and the likes, they immediately think it's some magic mumbo jumbo that requires some advanced level of wizardry to understand.

    I find it funny. I mean, I'm no developer, but one of my hobbies is going in the git repositories of some of the apps I use, look at the compares of the current version vs the previous one, and look up some of the code on the internet, and I can already tell what some things do (very little, since there are so many different programming languages and styles) which makes me respect developers more and more every time.

    You guys are super heroes in my book.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] 3 points 2 years ago (1 child)

    You should open the issue with crash data as the app says, everything else is just a guessing game...

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 3 points 2 years ago (1 child)

    2.6.0 on Android from F-Droid working fine

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 2 points 2 years ago

    Gah!

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 2 years ago (1 child)

    Coincidentally I am also having another crash issue just recently, but with a different reason. Also going to open an issue for that.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 1 point 2 years ago

    Yeah I’m having issues too. Crashes every time I try to open my inbox with an unread message. Won’t let me open a GitHub report for some reason. Every time I try GitHub tells me something went wrong

  • permalink
  • fedilink
  • source
    •