Whether this app process has registered the device's USDID.
The registration is a device binding the app performs at most once per
process, at the first point where it does: the pre-login flow of a process
that begins logged out, or the warm launch of a process that starts holding
a stored session. A session a login created here without running the
pre-login registers nothing in this process — it leaves the identity
unregistered and no request carries x-meta-usdid — because that start is
not observed. The registration brick reads and claims
this fact itself before it sends; a launch does not read it. Process state,
one per runtime layer — the Android and iOS layers install it; only Android
runs a flow that writes it — never in the session snapshot: a restored
session's process has registered nothing. This fact and the session origin
are process facts a checkpoint carries (its own task); a checkpoint gate does
not change them.
Whether this app process has registered the device's USDID.
The registration is a device binding the app performs at most once per process, at the first point where it does: the pre-login flow of a process that begins logged out, or the warm launch of a process that starts holding a stored session. A session a login created here without running the pre-login registers nothing in this process — it leaves the identity unregistered and no request carries
x-meta-usdid— because that start is not observed. The registration brick reads and claims this fact itself before it sends; a launch does not read it. Process state, one per runtime layer — the Android and iOS layers install it; only Android runs a flow that writes it — never in the session snapshot: a restored session's process has registered nothing. This fact and the session origin are process facts a checkpoint carries (its own task); a checkpoint gate does not change them.