This is a rant about how so many apps on many different platforms (TVs, mobile devices, computers, etc…) have decided to not actually show detailed errors any more. Instead, we get something along the lines of:

Oops, somehting went wrong. Please try again later

… and then, well, we get to figure out what just happened and what in the world we need to do about it. And good luck with that, since you have no idea what just failed.

Why software developers?!? Why have you forsaken us?

EDIT 24 hours later: I feel like I need to clarify a few things:

I’ve worked for 8 software companies over 30+ years. I know why putting a DB error into the message users see is a bad idea. I know that makes me uncommon, but I still want more info from these messages.

You all are answering as if there are only two ways this can work: (a) what we have now (which is useless), and (b) a detailed error listing showing a full stack trace. I think the developers could meet me half-way.

What I want is either (a) “Something went wrong on the server, you can’t fix it, but we will” or (b) “Something on your end didn’t work. Check your network or restart the app or do something differently and then try the same thing again”. And if they’re blocking me because I’m using a VPN, fucking say so (but that’s a whole separate thing…)

Some apps do provide enough info so I have a clue what I should do next, and I appreciate the effort they put into helping me. I think what I am really ranting about is I want more developers to take the time to do this instead of reporting all errors with “Oops, try again”. (If the error is in their server, why should I try again?) Give me a hint as to the problem, so I have something to go on.

Cheers y’all. Still love you my techy brothers and sisters.

    • NABDad@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      I wasn’t saying it was a solution, I was just offering a possible explanation. I understand why someone wouldn’t bother telling the user what’s happening. For my code, I log everything that happens, and tell the user to call me. When I get the call, I check the log and use that to figure out what went wrong.

      Distressingly typical user communication:

      User: There was an error message.

      Me: What did the error say?

      User: I don’t know. Something about the problem.