MAHDemo-2023-12-05-173312.ips MAHDemo-2023-12-05-174227.ips MAHDemo-2023-12-05-172152.ips I have obtained 3 crash reports, hopefully they will be of some help.

This Crash can be reproduced in the debug status of XCode. However, it seems that relevant information cannot be obtained through Analytics in this way. So, I tried to reproduce it by installing Archive, but a new problem came up during the installation: Error installing '/Users/xxxx/Desktop/temp/MAHDemo 2023-12-04 10-42-16/MAHDemo.ipa', ERROR: Error Domain=com.apple.dt.CoreDeviceError Code=3002 "Failed to install the app on the device." UserInfo={NSURL=file:///Users/xxxxxxx/Desktop/temp/MAHDemo%202023-12-04%2010-42-16/MAHDemo.ipa, NSUnderlyingError=0x60002205f810 {Error Domain=com.apple.dt.CoreDeviceError Code=3000 "The item at MAHDemo.ipa is not a valid bundle." UserInfo={NSURL=file:///Users/xxxxxxx/Desktop/temp/MAHDemo%202023-12-04%2010-42-16/MAHDemo.ipa, NSLocalizedFailureReason=Failed to read the bundle., NSLocalizedDescription=The item at MAHDemo.ipa is not a valid bundle.}}, NSLocalizedDescription=Failed to install the app on the device.} Domain: com.apple.dt.DVTCoreDevice Code: -1 User Info: { ​ DVTErrorCreationDateKey = "2023-12-04 02:45:13 +0000"; } System Information macOS Version 13.6.1 (Build 22G313) Xcode 15.0.1 (22266) (Build 15A507) Timestamp: 2023-12-04T10:45:13+08:00 The same IPA installed on iOS 15, 16 system will not appear.

Crash occur in different places, but this code is often seen.

How does your SDK work? Does it implement a HTTP proxy? Or is it using an NSURLProtocol subclass? Or something else? This SDK listens to 2 ports and implements an HTTP/HTTPS proxy locally. Then, NSURLSession is asked to proxy requests through by setting the proxy configuration of NSURLSessionConfiguration. Currently, we are not using NSURLProtocol. This issue, specifically, tends to occur after the first launch of an installed APP.

After explaining the purpose of the VPN to the reviewer, it has been approved. The End....

The user is unwilling to cooperate in obtaining the logs. We only have information that the user's iOS system is 16.0.3 and the device model is iPhone13,4. We hope this helps you.

I have found the reason why it didn't work. It seems that the content cannot contain Apple's domain name.

Please ignore or delete this post. I intended to publish something else, but after clicking the submit button, there was no response, so I tested by posting this message.

OK, so you see, this is why Matt wrote TN3120 Expected use cases for Network Extension packet tunnel providers. When you try to use a packet tunnel provider as a content filter, you will run into all sorts of weird and wonderful problems. This is just one example of such problems. Thanks. I understand, so if we want both VPN and traffic control, we must use different provider to achieve it.

I’m confused by your goal here. If an app creates a connection to a peer that’s directly connected to the local Wi-Fi, why does your VPN need to get involved? Because our APP not only provides a VPN service to users, but also provides a safe access environment. So we need access control for the device. So we don't want any traffic from the device to bypass our VPN and go straight out.

What platform are you testing on? iOS

Thanks for your help, I got a issue log the issue log It seems to be stuck by nw_path_necp_update_evaluator_block_invoke could you tell me what is this, and how can I avoid this.

The trick here is to have the user trigger a sysdiagnose log as soon as they see the problem. Then can then pass this on to your for analysis. For more information about this, see Your Friend the System Log. this can get entire iOS system log ? I don't find the way to do this after I read the documents. I said before: because APP can't get the iOS system log means, the log of my app is no useful, because the APP seems ok. The job to start the NetworkExtension Process is not the host APP（ MY APP). Host APP only setup the configuration and call the system API, and the log of my app show nothing wrong here. The log of my APP shows: when after call startVPNTunnelWithOptions: success, the NEVPNStatus change from NEVPNStatusDisconnected to NEVPNStatusConnecting (from NEVPNStatusDidChangeNotification) but long time (about 1 mins) the VPN Process not created, and status change to disconnect. So I think if i want to known why the VPN process not create success, I need to got the entiry iOS system log, this may show why the iOS system start the process fail.

Not work for me to ,    [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(__onRadioAccessTechonologyDidChanged) name:CTServiceRadioAccessTechnologyDidChangeNotification object:nil]; __onRadioAccessTechonologyDidChanged not called, when i switch 5G to 4G in IOS Setting

Finally, I fix this problem. After delete some Third-party libraries and remove some unnecessary classes, The IPA from the testflight work find ( this bug won't show by debug mode or local install IPA) Could you tell me, is there any way to avoid this problem happen again( like how many OC classes in VPN process is safe, or should keep the VPN pack below a specific size)。