Does migrating from Reachability to NWPathMonitor resolve simulator‑device reachability update discrepancies?

Answer to the question

Switching from the legacy SCNetworkReachability-based Reachability class to NWPathMonitor does not guarantee identical behavior on the simulator and on a physical device. On iOS 12 and later, NWPathMonitor delivers immediate, accurate callbacks for interface changes on a device, eliminating the stale‑flag problem that plagued Reachability. However, the simulator still exhibits a small latency (often 0.5–1 s) when toggling Wi‑Fi or cellular, because the simulator’s network stack is a thin proxy and does not propagate changes to NWPathMonitor> as promptly as a real device.

Confirmed facts

• NWPathMonitor is available from iOS 12.0, macOS 10.14, tvOS 12, watchOS 5.
• On a physical device, the pathUpdateHandler fires within <1 s of an interface change.
• In the simulator, callbacks can be delayed by up to 1 s, but the overall logic remains reliable.
• For iOS 11 or earlier, NWPathMonitor is unavailable; a fallback to SCNetworkReachability is required.

Practical steps for your app

1. Detect the OS version at runtime. Use #available(iOS 12.0, *) or if #available to decide which monitor to instantiate.

   if #available(iOS 12.0, *) {
       startNWPathMonitor()
   } else {
       startReachability()
   }
   

2. Configure the NWPathMonitor.

   let monitor = NWPathMonitor()
   let queue = DispatchQueue(label: "NetworkMonitorQueue")
   monitor.pathUpdateHandler = { [weak self] path in
       DispatchQueue.main.async {
           self?.handlePath(path)
       }
   }
   monitor.start(queue: queue)
   

   • Always capture self weakly to avoid retain cycles.
   • Dispatch UI updates to the main queue.
3. Implement a fallback for iOS 11. Keep the existing Reachability class, but only activate it when #available fails.

   func startReachability() {
       guard let reachability = Reachability() else { return }
       reachability.whenReachable = { _ in
           DispatchQueue.main.async { self.handleReachable() }
       }
       reachability.whenUnreachable = { _ in
           DispatchQueue.main.async { self.handleUnreachable() }
       }
       try? reachability.startNotifier()
   }
   

4. Test on both targets. Verify that toggling airplane mode, Wi‑Fi, or cellular triggers the handler within the expected window on a device, and note the simulator latency. Adjust your UI or user‑feedback logic if you need sub‑second responsiveness in the simulator.

When a dual‑implementation is necessary

If your app’s Deployment Target is set to iOS 11 or lower, you must keep Reachability as a fallback. For all supported releases (iOS 12+), prefer NWPathMonitor because it is future‑proof and not deprecated.

Missing diagnostic detail

To fine‑tune the fallback strategy, could you confirm the exact minimum iOS version your app currently supports? This will determine whether the dual‑implementation path is truly necessary.