Connectivity Checker Pro

Connectivity Checker Pro observes native Android and iOS network state and turns it into explicit, event-driven evidence for offline UI, retry policy, download decisions, diagnostics, and repeatable QA. It sends no HTTP, DNS, ping, latency, speed, or throughput probes and collects no user data. Your real application request remains the source of truth for login, payments, cloud saves, matchmaking, and every other critical backend operation. Drive offline and degraded-connection UI from explicit evidence. Inform retry and download policies with availability, validation, captive, constrained, metered, VPN, quality, and stability state. Keep diagnostics honest about what Android or iOS actually exposed. Let independent game modules share monitoring without stopping one another. Reproduce inconvenient network journeys inside the Unity Editor. Open Tools > Connectivity Checker Pro > Connectivity Simulator and apply offline, Android unvalidated, Android captive-portal, iOS path-only, constrained, metered, VPN, and flapping states through the same managed reducer used by the runtime. Version 1.2 adds reusable Simulation Scenario assets, deterministic timeline playback, and a bounded 100-entry state history with per-field diffs and redacted clipboard export. These Editor-only tools send no requests and do not replace Android or iOS device validation. Android uses the default network and NetworkCapabilities for availability, OS-validated internet evidence, captive-portal state, transports, metered and constrained state, VPN-related state, bandwidth/signal estimates when available, and Good/Poor quality labelled OsEstimate. iOS uses NWPathMonitor and public system signals for path state, Wi-Fi, cellular and Ethernet transports, expensive/constrained state, optional cellular details, best-effort VPN evidence, and Good/Poor quality labelled PathHeuristic. An iOS satisfied path is path evidence, not captive-portal detection or endpoint validation. Android validation is also OS evidence, not proof that your own API, DNS route, certificate, account, or region works. Use ConnectivityPro.AcquireMonitoring() for modular ownership. The first lease starts native monitoring and disposing the last lease stops it, so one subsystem cannot stop another subsystem's active session. Existing integrations can keep using the idempotent BeginMonitoring() / EndMonitoring() pair. No network requests or active probes. No analytics, identifiers, diagnostics, or connectivity state are collected or transmitted. No user tracking. Source-accurate iOS privacy manifest included. Compatibility: Unity 2022.3 LTS or newer, Android API 24 (Android 7.0) or newer, iOS 15.0 or newer, Mono and IL2CPP, Asset Store import under Assets or UPM installation under Packages, R8-minified Android builds through bundled consumer ProGuard rules. Samples are optional and require Unity UI (com.unity.ugui). The Editor Simulator uses Unity's built-in UI Toolkit module. Runtime monitoring has no downloadable feature-package dependency. IMPORTANT LIMITATIONS: Passive evidence does not prove that a customer endpoint works. iOS does not expose captive-portal or endpoint validation through NWPath. Android bandwidth and signal are OS estimates, not measured speed or latency. iOS quality is a coarse path heuristic without bandwidth or latency input. VPN and cellular details can be unavailable due to OS, device, carrier, or permission constraints. Editor simulation is deterministic integration support, not device QA.