To add a little context on the environment: MacOS: 15.3.2 Xcode: 16.0

I had runtime code signing error occuring for some reason, upgraded my MacOS hoping that would resolve the issue. Well, now my Xcode crashes when I try to upload for notarization. I am not surprised anymore because by now I have realized that instability is an expected behavior across this platform.

The reason for setTunnelNetworkSettings not being called was because I was passing nil as the options argument for startVPNTunnelWithOptions method of the connection object that is available in NETunnelProviderManager.

I need to make correction to my previous post, I still see CS_PLATFORM_BINARY set but not AppleSigned; prompt policy is Deny from tccd process

Thanks a lot for quick response, Does that mean I have to be enrolled to Apple Developer Porgram? The only reason I used Sign to Run Locally was to avoid that and if everything works fine in my local machine, then enroll to the program so I can distribute the application( not through App Store ). I thought that Sign to Run Locally would give me all the capabilities but only to my machine, and if that is not the case I don't know what is preventing Apple to give such option. Because at this moment I am not even sure, if Apple provides all the capabilities that my application would need even with paid developer account and apart from that I don't even know if Apple provides backward compatibility with the release of their new OS, because I have read that some Apps stopped working properly with newer MacOS. My application is a cross platform application written in C++, and the OS specific parts are small and done specifically for that OS. So, the whole idea was whether providing Mac/iOS version of the App would be something feasible or not.