I have encountered the same problem, it has shown that the provider registration is successful, but no traffic information is captured. I was wondering if you have resolved this issue and how?

Hello, I am trying to use the example (SimpleFirewall) of the network extension. Now I have completed the necessary profile configuration and other content. After I try to run, a corresponding small window will pop up, but no matter how long after I click start, no matter what connection I send, it does not respond and display. I would like to know how your step 3 is achieved? How can I make it display the proper function?

I'm facing the same messages during debug of my swift Mac app which use the storyboard. I would like to know if anyone solved it ?

Stop and start it how? I realized the capture of traffic information after rewriting with https://github.com/cntrump/SimpleFirewall. My question is as follows: Step1: Start the program (start the active scheme) from xcode, and the program interface will appear. The ui interface of the sample program provided by simplefirewall contains a button start/stop. step2: Click the button start (the button display switches to stop after clicking) to start monitoring. So I get the flow information. Step3: Click the button stop (the button display switches to start after clicking) to stop monitoring. step4: Click the button start again, and no new traffic information will be captured after that. (It is worth noting that this startup only starts from the interface button, not start the active scheme.)

On a separate machine than the machine that you are you doing your development on, do you see the same result if you build your container app and system extension and run this from the /Applications directory? Yes. Even I build it and run it from the /Applications directory.

And when I tried to refactor the whole project from scratch, I found that I could activate the extension：(myteam is my project, and lulu is the objective-see inc. project.) $ systemextensionsctl list 2 extension(s) --- com.apple.system_extension.network_extension enabled active teamID bundleID (version) name [state] * * myteamID com.myteam.Extension (1.0/1) NExtension [activated enabled] * * VBG97UB4TA com.objective-see.lulu.extension (2.5.0/2.5.0) Extension [activated enabled] but it didn't start the corresponding process $ ps -eaf | grep "com.objective-see" /Library/SystemExtensions/4B156F9A-3ECF-49B9-8A68-02D328502CFB/com.objective-see.lulu.extension.systemextension/Contents/MacOS/com.objective-see.lulu.extension grep com.objective-see` ps -eaf | grep "com.myteam" grep com.myteam

Thanks!! But I also want to ask a question that has nothing to do with distribution, because when I test in local xcode and manually configure the profile of the developer id, an error is also displayed: Provisioning profile "xxxx" doesn't match the entitlements file's value for the com. apple.developer.networking.networkextension entitlement. But what I can be sure of is that when I build the identifier, I choose the necessary system extension and network extension, and realize the correct association when the profile is created. I guess this has nothing to do with distribution? But how to solve it?

After I change the com. apple.developer.networking.networkextension in Xcode from Content Filter to content-filter-provider-systemextension, I have successfully build the archive to distribute. But when I run it on the other development, it has the sys log : sysextd attempt to realize extension xxxx. My app bundle id is com.company.name.app and the extension bundle id is com.company.name.Extension. Container.app Contents/ Library/ SystemExtensions/ com.company.name.Extension.systemextension Maybe this is still a permissions issue? How can I solve it? Are there any suggestions?

I solved my problem, it seems that the granting of permissions is uniquely confirmed by bundle identifier and product name, and a program with the same bundle identifier and product name previously existed in my environment. Although I deleted the old version of the program, The conflict appears to remain. Therefore, after I modified the bundle identifier and product name of the new program, I was able to successfully authorize it and it ran normally. But I can't confirm whether this is the root cause. If there is a more elegant solution, please suggest it. Grateful！