The network a rendered device presents: a client network (Wi-Fi or cellular),
or the Ethernet NIC of the emulator a render runs on (x-ig-connection-type: Ethernet).
It is not a client network and never reaches a client type:
MobileNetwork, MobileDeviceState.network, the client options
and the snapshot schema stay on Wi-Fi and cellular. The render tooling owns
it: it attaches the network to the device it renders with
(setCaptureNetwork), and the render-only wire tables (androidNetworkWire,
…) accept it; the reference names it because those signatures carry it. The
connection-type headers spell Ethernet and x-fb-network-propertiesValidated;; every other network-dependent value is left absent rather than
borrowed from Wi-Fi or LTE. The x-fb-appnetsession-* pair is not part of the
network: it is a state of the process (whether it began with a stored
session), so a render takes its presence from the scenario's process start,
and only the word after the comma is the network's own.
The network a rendered device presents: a client network (Wi-Fi or cellular), or the Ethernet NIC of the emulator a render runs on (
x-ig-connection-type: Ethernet).It is not a client network and never reaches a client type: MobileNetwork, MobileDeviceState.network, the client options and the snapshot schema stay on Wi-Fi and cellular. The render tooling owns it: it attaches the network to the device it renders with (
setCaptureNetwork), and the render-only wire tables (androidNetworkWire, …) accept it; the reference names it because those signatures carry it. The connection-type headers spellEthernetandx-fb-network-propertiesValidated;; every other network-dependent value is left absent rather than borrowed from Wi-Fi or LTE. Thex-fb-appnetsession-*pair is not part of the network: it is a state of the process (whether it began with a stored session), so a render takes its presence from the scenario's process start, and only the word after the comma is the network's own.