A temporary failure reading your credentials no longer looks like being logged out.
What's wrong with this entry?
A 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.
- ENOENT, EISDIR and ENOTDIR return null, meaning no credentials
- EACCES and EPERM return null on non-Windows
- anything else returns the READ_FAILED sentinel, which token refresh treats as transient
- the plaintext backend's strict read routes its errno through the new helper
secureStorage.READ_FAILED
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth