Post

Replies

Boosts

Views

Activity

NWListener fails to start within a CoreMediaIO Virtual Camera Extension
Hi. Our NWListener runs fine and accepts connections successfully when it's run in a standalone app, however, the same code fails when moved into the System Extension code. Specifically, we get the error: The operation couldn’t be completed. (Network.NWError error 0.) ... let listener = try NWListener(using: params!) listener.service = NWListener.Service(name: "service",                                 type: "_service._tcp") listener.stateUpdateHandler = { newState in switch newState {     case .ready:       if let port = listener.port {           self.receiveIncomingDataOnConnection()          }       case .failed(let error):       listener.cancel()          print("Listener - failed with %{public}@, restarting", error.localizedDescription) // Getting the error ^        default:         break             }  } ... We have checked that the App Sandbox permissions for inbound and outbound connections are set in the entitlements file. At this point, we are stumped at what's limiting our listener when it's running in the extension. Thanks!
8
0
1.6k
May ’22
NWProtocolFramer fails with 'Not enough bytes to fragment' for UDP
We've been hitting a problem with sending frames over UDP that over 50k bytes despite writing a NWProtocolFramer based on the code in this thread The error is coming from the stack with: nw_protocol_ipv6_frame_output_finalizer [C1.1.1:3] Not enough bytes to fragment 55616 I was under the impression that NWProtocolFramer is the way to fragment the frame for the specific use case but I'm confused at this 50k limit that we seem to be hitting. Any ideas? Thanks!
5
0
950
Jun ’22