Login token refreshes now survive laptop sleep and long suspends more reliably.
What's wrong with this entry?
Scheduled token refreshes no longer rely on one long setTimeout, which makes them more reliable across long sleeps and machine suspends.
- A repeating chunked timer re-evaluates the remaining time against a 60000ms cap.
- The refresh only fires when a generation token still matches, so stale timers from a superseded schedule are ignored.
Scheduled token refresh for sessionId=
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