@ppix That's strange - I resolved this issue by only accepting the connection that reached .ready. The other three end up .canceled

Thanks for the reply! I'd been hesitating to migrate to Network.framework but after reading your reply, I decided to give it a shot. It only took a few hours, and now this problem (and several others!) are resolved.

Has anything changed with this answer with the announcement of iOS 18? Thanks!

Thanks for the quick response, and the suggestion. If I went that route, would it still have to be two separate, spaced-out taps, i.e. one tap to focus, then we enable the menu, then the user taps again? Would a double-tap always get picked up as a single double-tap gesture?

This worked for me. It's a pain to not have wi-fi on my MacBook, but at least debugging works again. Thank you!

Thanks for getting back. In that case, what is the default policy if there's a conflict between the local data and what's stored on the server? And is there any way to handle broken references (a local model refers to another model, which has been deleted from the server by some other device)?

Thanks, but that doesn't specifically answer my question about SwiftData. I'm aware of how to resolve conflicts with CloudKit, but since SwiftData handles CloudKit syncing internally, I'm looking for a method that works with SwiftData.

Won't UIApplication#open actually open the other app?

Thanks - this works for me! Definitely looks like a bug.

Thanks - this solved my problem!

Thanks for the quick response! Is it helpful to file a radar for it?

I can confirm that by moving from NetService to NWBrowser/NWListener (as you suggest), you do get notified of this problem in the NWBrowser#stateUpdateHandler callback. This is very helpful for me, but I'm not sure how to check that a specific NWBrowser.State instance represents waiting(-65570: PolicyDenied). I can only see this information when I print the debugDescription or print the value in the LLDB console, but how do I check specifically that the state is PolicyDenied?

Thank you!