[saagarjha]

Bad error messages is kind of an institutional problem at Apple. Somehow there’s a push to “simplify” the error process and it invariably means that some part of e pipeline has good error info that is, if you’re lucky, dropped in a log somewhere and just completely swallowed if you’re not. In the UI you’ll just get a generic “something went wrong” or a “translated” error that isn’t bijective at all, or sometimes not even an indication that something went wrong (particularly around ambient operations like syncing). It’s really quite frustrating how often I need to go through a truly awful amount of spelunking just to figure out what a “user friendly” message means, which is pretty much the opposite of user friendliness.

[can16358p]

I get user friendliness for non tech-savvy users, but they should definitely have something like "details" that you can expand for power users, especially somewhere like custom domain management/DNS record checker where there are probably power users using it.