Under the hood
Useful2 Signal3
Trusted-device proof is renewed once per run instead of just reloaded from disk.
What's wrong with this entry?
Anonymous. No account, no email.
What
The client that streams sessions now renews its trusted-device proof once per run, re-enrolling with the previous token rather than only reloading whatever was on disk. If renewal produces nothing, the stored token is cleared.
Details
- Renewal runs at most once, guarded by an internal flag, and falls back to a plain token load if re-enrolment fails.
- A failure is logged and the client simply sends no trusted-device header, so requests continue unauthenticated by device rather than erroring.
Evidence
[SessionsV2Client] device proof renewal 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