{"version":"2.1.223","anchor":"credential-read-errors-are-classified-by-errno","canonical_anchor":"credential-read-errors-are-classified-by-errno","heading":"Credential read errors are classified by errno","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/credential-read-errors-are-classified-by-errno","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Credential read errors are classified by errno\n\nA temporary failure reading your credentials no longer looks like being logged out.\n\n**What**\n\nA failed credentials read is now distinguished from an empty credential store, so a transient read failure no longer causes token refresh to proceed as if you had no credentials.\n\n**Details**\n\n- ENOENT, EISDIR and ENOTDIR return null, meaning no credentials\n- EACCES and EPERM return null on non-Windows\n- anything else returns the READ_FAILED sentinel, which token refresh treats as transient\n- the plaintext backend's strict read routes its errno through the new helper\n\n**Evidence**\n\n`secureStorage.READ_FAILED`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}