Credential refresh failures now report which specific thing went wrong instead of just failing.
What's wrong with this entry?
Refreshing host credentials throws with a distinct error for each failure mode: the credential file failing to re-read, an endpoint variable changing between reads, and a refresh that came back without the bearer key. All three previously returned null.
host-creds refresh dropped the bearer key
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