hasCompletedHttpSetup property

@TagNumber.new(10) bool get hasCompletedHttpSetup

Explicit two-phase HTTP-setup completion flag, decoupled from services-init completion so SDKs that initialize offline (no connectivity) can still report success=true with has_completed_http_setup=false and retry HTTP later via the SDK_INIT_PHASE_RETRY_HTTP path. Mirrors RunAnywhere.swift:37 (internal static var hasCompletedHTTPSetup) and is the canonical signal Flutter / Web / RN consume to decide whether the next download/authenticated call can proceed without a retryHTTP step.

Distinct from http_configured (field 4) which historically meant "HTTP transport wired up at this phase's call site"; this field is the cross-phase latched bit that survives between phase calls.

Implementation

@$pb.TagNumber(10)
$core.bool get hasCompletedHttpSetup => $_getBF(9);

@TagNumber.new(10) set hasCompletedHttpSetup (bool value)

Implementation

@$pb.TagNumber(10)
set hasCompletedHttpSetup($core.bool value) => $_setBool(9, value);