No the verify block is not called from the method sec_protocol_options_set_verify_block, but only on iOS 13. Not sure why this would happen. I am using the same queue as the one NWConnection is using. What would cause the block not to be called?

I decided to take another look at this since iOS 16 is out of beta. There is a developer comment on the property now. Only certain devices are supported, like the comment mentioned above. Here is a current list of supported devices. This property returns true for iPad Pro (4th generation), iPad Pro (5th generation) and iPad Air (5th generation). Hopefully Apple will help us out further in the future or make it easier to gain access to the entitlement for this feature.

Really? That is interesting. I have tried on iPhone XR. I have not tried on Mac yet. I have several devices I could try on, but I am not sure why trying on a iPhone >= XR wouldn't work. Any suggestions or any other successful test cases?

The documentation states, _"Starting in iOS 16, your app can use the camera while multitasking by setting the isMultitaskingCameraAccessEnabled property to true on supported systems. Do we have a scenario needed or a list of supported systems. This seems to be quite ambiguous.

Ah ok I see. Hey thanks a bunch. The memory footprint is certainly better. Much appreciated! Question: Is free(destinationBuffer.data) preferred over destinationBuffer.data.deallocate()?