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?
You must log in or register to comment.
What are you planning to do with information about the error? It’s not like these places have customer support. Usually it’s something like a caching layer failing, and there’s literally nothing you can do about that.
If it’s an error code I’ve worked around before, apply same troubleshooting.
If its a new errror code, search the error code to see how other people solved it.
If no one else has solved the error code, try analogous troubleshooting, post results online with the error code name, successful or not.
Error messages are a common way for hackers to gain information about a system. Useless error messages are recommended for security.
If you enter your username as Robert’'); DROP TABLE Students;-- giving the error “Oops, something went wrong” is better than “NoSuchTable: ‘Students’ Table doesn’t exist in the database” because now the hacker knows you’re using a database that interprets SQL commands and inputs aren’t being sanitized.
Hacking programs like Burp Suite have functions that spam sites with all kinds of garbage data and uses error messages and delays in response times to highlight potential vulnerabilities.
This comment belongs on masterhacker
So in short it’s used to mask the developers errors?
Because 99% of the time these errors are caused by something on their end that the user is unable to fix, even on the off chance that they understand the problem in the first place. So there isn’t any need to give you more information than “something went wrong, please wait a minute and/or try again”.
OK but then inherent in what you’re saying is also the message, “… and don’t contact us about this, because we don’t want to deal with it” which is also mildly infuriating to me.
Iit’s an internal error that is not handled properly. They don’t want to tell you the exact error message and detailed information around that, because it would expose the internal state of the backend and that would be a security issue. There is really nothing more that they can tell you, except that a developer needs to look at this (and possibly thousands to tens or hundreds of thousands of similar logged errors) and they probably already are.
Maybe then, the message could be, “An internal error has occurred and we’re going to work on fixing it but there’s nothing you can do to fix it yourself right now”. It’s the “Oops” that fries my grits.
If you’re tech-savvy enough to want detailed error messages, you should also be tech-savvy enough to understand the implied message you just typed out. The ‘Oops’ isn’t for you, it’s for the average user.
I do agree, the whole “oops sowwy” with a sad Labrador vibe is a little irritating. But I guess they do it cause it’s a harmless and layman-friendly response.
LMFAO. I probably have to truncate at least five error log files a week on various vps servers at my company because they fill the SSD and crash the OS. We rent servers we don’t dev them for our cx.
Largest error file I’ve seen so far is 32 GB
Site owners are normally clueless. Site developers normally can’t give a single fuck and systems administrators like me. Get to pick up the pieces and tell them to tell their Deb to fix it and then we pick it up again and tell them to tell their Dev to fix it let me know when you sense a pattern
You’re assuming they aren’t already aware of the issue.
Sorry but how does that help me?
What I’m saying is that when you see one of these messages you should interpret it as “something is wrong on our end, nothing you can or need to do on your end, please hang tight as we’re aware of the issue and working on it”. They don’t give you more info than that because that average person is probably not a dev and doesn’t have any need for more details than that.
But it’s MY Internet, and I want it NOW!!
You’re giving an incredibly large allowance for companies that have continuously calculated exactly how much they can fuck over their customers for more money before we decide to use some other product.
How does telling someone about a problem they’re already aware of help you?
Of course if their servers and whatnot are shit they won’t straight up tell you they are shit.
It’s why modern multiplayer games don’t even show everyone’s latency anymore. It would let players know imperically that their servers are shit.
In theory, maybe. In practice, I’ve had a lot of errors in that vein that very much wouldn’t go away, and where made much harder to diagnose by their obtuseness.
Honestly, I even dislike the mindset. Just make a big header with the generic error message and a little one below that gives some details. Having users interested in how your software works is not a bad thing.
I give my users instructions on how to report an error if they seek assistance. It’s regularly ignored. Instead we get the ubiquitous “Something bad happened … somewhere. HALP!”
“I got an error”
“What did it say?”
“I don’t know, just something went wrong”
“👍”
Exactly, it’s especially infuriating on newpipe. WHAT went wrong? It’s an error 500 from YouTube (rare, unfixable, try again) or Google changed something and need to wait for a client fix? Or simply Google blacklisted the IP address or put some captcha that prevents playing the video??
Users ignore error messages.
I have seen my users request support, proceed to demonstrate the issue they’re having, and click through error messages so fast there isn’t even enough time for me to say “WAIT!” Forget about being able to actually read even one word of the message before it’s dismissed from the screen.
They treat the error messages like they are just an annoying mosquito to be swatted away as quickly as possible. This despite the fact that the whole reason I’m standing behind them is so I can see what it’s going wrong and, you know, read the error messages.
That’s Windows’ training bearing fruit.
Them:
“What? Oh that? That always happens”
Me:
Grrrrr
Yeah, you’re right, but I still would prefer to see something telling me whether something I did caused the problem or something went wrong in the software / on the server. From this thread, I’m getting that my wishes will not be heard.
Most common place I see those is when the site doesn’t want to talk to a known VPN endpoint. Like another mentioned site owners don’t want to given any more info to what they perceive as a possible threat than needed, so they just give a generic failure page.
Reminds me of the old “Oopsie woopsie we made a fucky wucky!!” post
Ringtone for when work calls/texts:
If it doesn’t tell you what error it is, isn’t an error message, it’s just a message that says that something went wrong. Even a calculator has proper error messages that show you actual information about what is wrong
What I hate even more are error codes
Precise, easily searchable codes that describe the problem? What a ball ache!
Not on Windows, no. “This error code could indicate this or that or something”.
This is the only error message I need
