Your login token is re-read from the keychain only when it genuinely changed, not on every check.
What's wrong with this entry?
The cached OAuth token is now held per host alongside the last credentials modification time, credentials version and last keychain access token, so a change check that cannot read a version falls back to comparing the keychain token itself and only invalidates the cache when it genuinely differs.
- Replaces a set of memoized functions cleared piecemeal with a single per-host object exposing
clear()andresetChangeCheck(). - The object also holds the in-flight fetch promise, so concurrent callers share one refresh.
lastKeychainAccessToken
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