Options of the live API client: apiTransportClientOptions plus the
platform's transport profile (always passed; the transport requires it and
never chooses a platform itself), the protocol mode (the caller's, else the
platform's) passed as is, and the x-fb-appnetsession-nid pair's network type,
derived from the device's network (the transport has no network of its own).
For the presented 451 build the pair's presence is the process fact
startedWithSession (whether the process began with a stored session), which
the entry that builds the process passes in (ProcessStart) — never a
derivation from the snapshot's authorization. The Android profile — which
defaults to off — is opted in exactly then, as the app does (451 warm launch
of a stored session: pair; 451 launch and the 448 login-recovery process on LTE,
both created inside themselves: none; the 450/451 Wi-Fi apps of
stored sessions: pair).
The network decides only the word after the comma. The 448 build additionally
sent the pair on cellular only (a stored Wi-Fi process sent none); the
library presents the 451 build, which follows the
process-start rule. The iOS profile keeps its own default (the iOS app has no
known created-process start).
The caller's network is a client network; the conformance tooling renders a
device whose own network the client state cannot hold through
captureTransportClientOptions (client.transport-options.ts).
Options of the live API client: apiTransportClientOptions plus the platform's transport profile (always passed; the transport requires it and never chooses a platform itself), the protocol mode (the caller's, else the platform's) passed as is, and the
x-fb-appnetsession-nidpair's network type, derived from the device's network (the transport has no network of its own).For the presented 451 build the pair's presence is the process fact
startedWithSession(whether the process began with a stored session), which the entry that builds the process passes in (ProcessStart) — never a derivation from the snapshot's authorization. The Android profile — which defaults to off — is opted in exactly then, as the app does (451 warm launch of a stored session: pair; 451 launch and the 448 login-recovery process on LTE, both created inside themselves: none; the 450/451 Wi-Fi apps of stored sessions: pair). The network decides only the word after the comma. The 448 build additionally sent the pair on cellular only (a stored Wi-Fi process sent none); the library presents the 451 build, which follows the process-start rule. The iOS profile keeps its own default (the iOS app has no known created-process start).The caller's network is a client network; the conformance tooling renders a device whose own network the client state cannot hold through
captureTransportClientOptions(client.transport-options.ts).