I see that only when we call startVpnTunnel() API the NE process gets forked. Also if the StopVpnTunnel() API gets called the process gets killed. Could you correct my understanding? Is there any API that can spawn the NE tunnel process as any init() call or something ?
Secondly, Is it possible to create a file in NE and access that in App side ? Since I can't get any prints in console wanted to know if I can write the loggings into a file so that can be refered for debugging any issues.
So I presume that your question is for the same context as your previous thread, that is, an NE appex on iOS.
I see that only when we call
startVPNTunnelAPI the NE process gets forked. Also if thestopVPNTunnelAPI gets called the process gets killed.
Yes.
Well, on Apple systems it’s best not to think in terms of ‘forking’ because most processes, including the process running your NE appex, are spawn by launchd and that’s very different from the traditional Unix fork model. For some background on this, see the discussion at the top of the launchd.plist man page.
Note An NE appex is, under the covers, most like an XPC Service. See the xpcservice.plist man page for more on that.
Is there any API that can spawn the NE tunnel process as any
initcall or something ?
No.
Why do you want to do that?
Is it possible to create a file in NE and access that in App side ?
Yes, using an App Group.
Since I can't get any prints in console wanted to know if I can write the loggings into a file so that can be refered for debugging any issues.
As I mentioned in your other thread, you’d be better off routing your log messages via the unified logging system.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
