Post not yet marked as solved
Post marked as unsolved with 5 replies, 738 views
I’m trying to use NWPathMonitor in my watchOS 6 app. The weird thing is that it works fine in Simulator, but is never ‘satisfied’ on a real device. Is there a reason why this is so? If it is a limitation of a real device, then perhaps Simulator should reflect that limitation. If it’s not a limitation, then how can I coax the device to return ‘satisfied’?