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).
The pair is emitted on cellular and not on Wi-Fi, reproducing the correlation
the 448 recordings show (in the app presence is a state of the process/device
network session, not a network fact): appNetSession: true is passed exactly
on a cellular network, so the Android profile — which defaults to off — opts
in on LTE and keeps its off default on Wi-Fi, while the iOS profile keeps its
on default on both (the explicit true is a no-op there).
The caller's network is a client network; the capture tooling renders a
device whose recorded 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).The pair is emitted on cellular and not on Wi-Fi, reproducing the correlation the 448 recordings show (in the app presence is a state of the process/device network session, not a network fact):
appNetSession: trueis passed exactly on a cellular network, so the Android profile — which defaults to off — opts in on LTE and keeps its off default on Wi-Fi, while the iOS profile keeps its on default on both (the explicittrueis a no-op there).The caller's network is a client network; the capture tooling renders a device whose recorded network the client state cannot hold through
captureTransportClientOptions(client.transport-options.ts).