Enum RunnerTransportError 

pub enum RunnerTransportError {
    FetchFailed {
        endpoint: String,
        source: Error,
    },
    NonSuccessStatus {
        endpoint: String,
        status: u16,
        body: String,
    },
    NonJsonBody {
        endpoint: String,
        source: Error,
    },
    MalformedBody {
        endpoint: String,
        detail: String,
    },
    Unreachable {
        endpoint: String,
        message: String,
    },
    AppUnavailable {
        endpoint: String,
        target: Option<String>,
        reason: Option<String>,
    },
    RunnerDegraded {
        window: usize,
        non_success_recent: usize,
        last_endpoint: String,
        last_error: String,
    },
    RunnerDied {
        last_seen_ms: u64,
        last_error: String,
    },
}

Transport-level failure (network, non-2xx, malformed body). Mirrors TS RunnerTransportError 1:1.

Variants

FetchFailed

Fields

endpoint: String

source: Error

NonSuccessStatus

Fields

endpoint: String

status: u16

body: String

NonJsonBody

Fields

endpoint: String

source: Error

MalformedBody

Fields

endpoint: String

detail: String

Unreachable

Fields

endpoint: String

message: String

AppUnavailable

The runner returned {"ok":false,"error":"snapshot_unavailable"} (or the enriched body with target/reason fields). This is not a network failure — it means XCUITest could not snapshot the app the client asked about. Callers that see this after all retries can surface an AI-readable hint about foreground state.

Fields

endpoint: String

target: Option<String>

reason: Option<String>

RunnerDegraded

Client-side rolling-window observation: consecutive requests have been failing (5xx, unreachable, non-JSON). The runner is still responding to the transport, but its answers are unsound — surfacing this instead of silently returning stale bodies is the whole point of HttpRunnerClient::with_liveness_window.

Fields

window: usize

non_success_recent: usize

last_endpoint: String

last_error: String

RunnerDied

Client-side observation of a hard runner death. Triggered when a is_connect() error fires AND a /health probe times out or returns a non-2xx within 1 s. Distinct from RunnerTransportError::Unreachable which fires on the initial reachability probe; RunnerDied fires mid-session after ensure_reachable had already succeeded.

Fields

last_seen_ms: u64

last_error: String

Trait Implementations

impl Debug for RunnerTransportError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for RunnerTransportError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for RunnerTransportError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.