@alaaugustine Are you able to programmatically capture Console logs? Can you please explain how you are doing it?

How the server logs should help here? Most chances that packets are not sent in this scenario

Thanks! I checked it, and seems that Charles configuring the macOS system proxy settings. They also have a checkbox "Enable macOS proxy". However, I don't see any new profile at the network preferences (so no new VPN..) So according to those findings, it should work with a Packet Tunnel Provider VPN, right? (It doesn't work for me, but still trying to check if it's even should work..)

New details/ question: I can't see the launcher app under the user's Login Items (at System Preferences), but anyway - the launcher is working after each restart, and it's opening my app. The questions: Why I can't see it at the Login Items? The really important question: Even that the app is now at the foreground after Mac restarts, It's not really active - applicationDidFinishLaunching() is not getting called, so I can't listen to notifications from the extension. Any way to make it work?

Hi, it's the same for me - so far this crash reproduces only on a VM with Monterey (in my case, version 12.0.1)

So just to be sure - you and Matt are saying that I need to drag the dylibs into my sysExt, and also to add it to the embedded frameworks at the sysExt, is it correct? If this is what you meant, I already tried it, but I still got the 'Library not loaded' error..

Well, I had a very similar issue- after getting the ENOBUFS error, all traffic stopped. This error probably suggested that the queues to the kernel were full, so maybe there's still some shared code for both L3 and L4. Anyway, not to hijack this thread, I'll just follow the responses here.

Thanks! This is the behavior I saw, but I couldn't explain if it was the expected one. Now it's clearer.

Please ignore this. I resolved this (silly) problem. I'll update about the NWConnection experiment.

Thanks for the great answer!

Thanks for the answer! I'll file the enhancement request and post the bug number later on.

It was something in my code, so no need for a bug report. Thanks!

Thanks! If it reproduces, I'll ask the user to enable logging and update the information here.