"nw_endpoint_handler_set_adaptive…" coming from XPC service

I’ve got an application, which uses (a couple of) XPC service(s) to accomplish various tasks. Since recently, I don’t know when exactly but probably after some macOS update, I started seeing these messages coming out when XPC services are used:

[connection] nw_endpoint_handler_set_adaptive_read_handler [C1.1 140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en1, ipv4, dns)] unregister notification for read_timeout failed

or

[connection] nw_endpoint_handler_set_adaptive_write_handler [C1.1 140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en1, ipv4, dns)] unregister notification for write_timeout failed

This happens when the service want’s to use outgoing connection. Not that it only happens in Xcode during debugging, but the deployment version of the application/XPC emits these messages to the console as well. However, everything works correctly as it has before. I’d like to surpass those messages going into the console, but I’d also like to understand what they actually mean and why they appear in the first place. Searching the Internet didn’t really revealed any useful info, so I hope someone here can help me. Anyone else seeing those?

  • 2021-06-03 17:26:59.239540+0800 douyin[4227:14099😎 [connection] nw_endpoint_handler_set_adaptive_read_handler [C1576 103.39.232.15:80 ready socket-flow (satisfied (Path is satisfied), viable, interface: en21, ipv4, dns)] unregister notification for read_timeout failed

    2021-06-03 17:26:59.239681+0800 douyin[4227:14099😎 [connection] nw_endpoint_handler_set_adaptive_write_handler [C1576 103.39.232.15:80 ready socket-flow (satisfied (Path is satisfied), viable, interface: en21, ipv4, dns)] unregister notification for write_timeout failed

    me too

Add a Comment

Replies

will this also get fixed for BigSur?

I can’t offer specific predictions about The Future™. My general experience, however, is that once a major OS release ships any future updates for a previous release are focused on security and interoperability improvements.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

This is still an issue on Xcode 13.1 with the latest Monterey (12.1 beta 4 21C5045a) at the time of this writing so no, unfortunately it is still not fixed.