IGPAPI
    Preparing search index...

    Interface AndroidHeaderSessionState

    State the edge reads to derive request features: session state, and the rendered navigation chain from NavigationWire. The resolver itself never sees either.

    interface AndroidHeaderSessionState {
        navChain?: string;
        processStartedWithSession?: boolean;
        rmd?: MobileRmdState;
        sessionStartPhase?: "starting";
        zeroInterface?: boolean;
    }

    Hierarchy

    • Pick<MobileSessionState, "rmd" | "zeroInterface" | "sessionStartPhase">
      • AndroidHeaderSessionState
    Index

    Properties

    navChain?: string

    The rendered navigation chain; present once the app recorded a screen of the session.

    processStartedWithSession?: boolean

    Whether this app process began with a stored session (MobileProcessStart).

    Routing-map (RMD) state reported on every request once the app has started evaluating its routing map. Absent until then.

    sessionStartPhase?: "starting"

    Set while the app is running the jobs it launches at user-session creation (see RequestScope's session-start). Requests issued in this window omit the x-pigeon-session-id header: the 448 capture carries it on the pre-login and late-session families but not on the post-login session-start burst (sequences 23–35), where it reappears from the request after the burst.

    zeroInterface?: boolean

    Set once the app has started its zero-rating campaign evaluation; the zero-http-network-interface header is reported from then on. A separate concept from MobileSessionState.rmd: the 448 capture carries x-fb-rmd already on the Loom config request but the network interface only from the zero-campaign request that follows it (see StartZeroInterface).