{"version":"2.1.257","anchor":"oauth-callback-server-errors-now-carry-distinct-user-facing","canonical_anchor":"oauth-callback-server-errors-now-carry-distinct-user-facing","heading":"OAuth callback server errors now carry distinct user-facing names","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/oauth-callback-server-errors-now-carry-distinct-user-facing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### OAuth callback server errors now carry distinct user-facing names\n\nOAuth callback failures such as port-in-use or timeout now carry distinct short names.\n\nErrors from the local OAuth callback listener, covering port-in-use, server failure, timeout, and unexpected auth result, now carry a distinct short `name` alongside the detailed message instead of being plain `Error` objects.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}