Whether the process a client is built for began with a stored session: the
one process-start fact both layers read. The entry that builds the process
decides it:
continuing a checkpoint carries the fact the checkpoint stores
(MobileProcessStart.startedWithSession), because a checkpoint of a
process that signed in inside itself holds an authorization while that
process began without a session;
launching derives it from the session it starts from
(session.authorization !== undefined, through startedWithSessionOf), so
a pre-login stored state launches as a created process.
The same fact feeds the native transport's x-fb-appnetsession-* pair and
the TypeScript header model (MobileProcessStart), so one process cannot
send the pair on one layer and not on the other.
Whether the process a client is built for began with a stored session: the one process-start fact both layers read. The entry that builds the process decides it:
MobileProcessStart.startedWithSession), because a checkpoint of a process that signed in inside itself holds an authorization while that process began without a session;session.authorization !== undefined, throughstartedWithSessionOf), so a pre-login stored state launches as a created process.The same fact feeds the native transport's
x-fb-appnetsession-*pair and the TypeScript header model (MobileProcessStart), so one process cannot send the pair on one layer and not on the other.