{"version":"2.1.248","anchor":"trusted-device-proof-is-renewed-not-just-reloaded","canonical_anchor":"trusted-device-proof-is-renewed-not-just-reloaded","heading":"Trusted-device proof is renewed, not just reloaded","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/trusted-device-proof-is-renewed-not-just-reloaded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Trusted-device proof is renewed, not just reloaded\n\nTrusted-device proof is renewed once per run instead of just reloaded from disk.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Renewal runs at most once, guarded by an internal flag, and falls back to a plain token load if re-enrolment fails.\n- A failure is logged and the client simply sends no trusted-device header, so requests continue unauthenticated by device rather than erroring.\n\n**Evidence**\n\n`[SessionsV2Client] device proof renewal failed: `\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}