Returns true when the cached x-meta-usdid is missing, malformed, or its
embedded <timestamp> (= JWS exp - 2, the second dot-separated part in
both the three-part 429 form and the four-part 448+ form) has already
elapsed.
This is a question about the cached value, not the app's re-registration
rule: the warm launch of a process that begins with a stored session
registers the device whatever the cached value's remaining life, and whether
a long-running process re-registers when the header expires is not modelled.
No flow uses this as its trigger today.
The library's own reader of the cached value's lifetime. It is not
part of the published surface — a caller has no use for it — and it is not a
trigger.
Returns true when the cached
x-meta-usdidis missing, malformed, or its embedded<timestamp>(= JWSexp - 2, the second dot-separated part in both the three-part 429 form and the four-part 448+ form) has already elapsed.This is a question about the cached value, not the app's re-registration rule: the warm launch of a process that begins with a stored session registers the device whatever the cached value's remaining life, and whether a long-running process re-registers when the header expires is not modelled. No flow uses this as its trigger today.
The library's own reader of the cached value's lifetime. It is not part of the published surface — a caller has no use for it — and it is not a trigger.