It seems that sometimes the pathUpdateHandler block is called even though the NWPath data is unchanged. Is this known? Or is there some unexposed change to the NWPath struct?
2023-08-23 14:16:02.149962+0900 NWPath -> status: satisfied, unsatisfiedReason: notAvailable, availableInterfaces: ["(type: wifi, name: en0, kernel index: 11)", "(type: cellular, name: pdp_ip0, kernel index: 3)"], isExpensive: false, isConstrained: false, supportsIPv4: true, supportsIPv6: false, supportsDNS: true, gateways: ["(description: 192.168.0.1:0, interface: nil, txtRecord: nil)"], localEndpoint: nil, remoteEndpoint: nil
2023-08-23 14:19:12.077079+0900 NWPath -> status: satisfied, unsatisfiedReason: notAvailable, availableInterfaces: ["(type: wifi, name: en0, kernel index: 11)", "(type: cellular, name: pdp_ip0, kernel index: 3)"], isExpensive: false, isConstrained: false, supportsIPv4: true, supportsIPv6: false, supportsDNS: true, gateways: ["(description: 192.168.0.1:0, interface: nil, txtRecord: nil)"], localEndpoint: nil, remoteEndpoint: nil
2023-08-23 14:19:16.065005+0900 NWPath -> status: satisfied, unsatisfiedReason: notAvailable, availableInterfaces: ["(type: wifi, name: en0, kernel index: 11)", "(type: cellular, name: pdp_ip0, kernel index: 3)"], isExpensive: false, isConstrained: false, supportsIPv4: true, supportsIPv6: false, supportsDNS: true, gateways: ["(description: 192.168.0.1:0, interface: nil, txtRecord: nil)"], localEndpoint: nil, remoteEndpoint: nil