The login credential cache now has a slot to remember read failures, but nothing uses it yet.
A lastReadFailure field exists on the credential cache and is reset alongside the others, but nothing reads or writes it.
What's wrong with this entry?
The credentials cache carries a new field for recording a read failure, with nothing reading it yet.
lastReadFailure: nulladded to the cache object literal and to its reset routine- sits alongside the existing
cache,generationandreadInFlightfields - nothing else in the bundle reads or writes it, so there is no observable effect in this build
lastReadFailure
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