Please help to understand the below crash better Incident Identifier: 2420C89E-A8C9-4E23-BBEA-FE3995C57495 Hardware Model: iPhone12,8 Process: PacketTunnelProvider [3824] Path: /private/var/containers/Bundle/Application/636BECFF-E199-48A0-A3F3-3AC9BA735CE0/masked masked for Endpoint.app/PlugIns/PacketTunnelProvider.appex/PacketTunnelProvider Identifier: com.masked.masked_company.tunnel Version: 1.1.38010102 (1.1.38010102) Code Type: ARM-64 (Native) Role: Unspecified Parent Process: launchd [1] Coalition: com.masked.masked_company.tunnel [835] Date/Time: 2023-02-06 18:28:41.8259 +0100 Launch Time: 2023-02-06 18:28:41.4521 +0100 OS Version: iPhone OS 14.3 (18C66) Release Type: User Baseband Version: 2.03.04 Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000038 VM Region Info: 0x38 is not in any region. Bytes before following region: 4302618568 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10074c000-100750000 [ 16K] r-x/r-x SM=COW ...unnelProvider Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [3824] Triggered by Thread: 3 Thread 3 name: Thread 3 Crashed: 0 SharedFramework 0x0000000100810364 details::purge_cache() + 72 (AppConnectionInfo.mm:31) 1 SharedFramework 0x0000000100810334 details::current_time() + 4 (AppConnectionInfo.mm:21) 2 SharedFramework 0x0000000100810334 details::purge_cache() + 24 (AppConnectionInfo.mm:28) 3 SharedFramework 0x000000010081515c __60-[GCDTimer initWithInterval:repeat:leeway:queue:completion:]_block_invoke + 28 (GCDTimer.m:31) 4 libdispatch.dylib 0x0000000186e84db0 _dispatch_client_callout + 20 (object.m:559) 5 libdispatch.dylib 0x0000000186e8812c _dispatch_continuation_pop + 416 (inline_internal.h:2548) 6 libdispatch.dylib 0x0000000186e99c08 _dispatch_source_invoke + 1260 (source.c:570) 7 libdispatch.dylib 0x0000000186e8bfd8 _dispatch_lane_serial_drain + 272 (inline_internal.h:2589) 8 libdispatch.dylib 0x0000000186e8cc5c _dispatch_lane_invoke + 408 (queue.c:3862) 9 libdispatch.dylib 0x0000000186e96d78 _dispatch_workloop_worker_thread + 708 (queue.c:6601) 10 libsystem_pthread.dylib 0x00000001d2adb804 _pthread_wqthread + 276 (pthread.c:2207) 11 libsystem_pthread.dylib 0x00000001d2ae275c start_wqthread + 8 (:-1) Relevant code block for the same     const auto now = std::chrono::system_clock::now();     const auto msecs = std::chrono::duration_cast<std::chrono::microseconds>(now.time_since_epoch()).count();     return msecs; } void purge_cache() {     // TODO : check for the more optimisations here.     auto now = current_time();     // TODO : 31045550 : add an aggregated telemetry of cache size here, this requires changes in TelemetryAggregator     for (auto it = _cache.begin(); it != _cache.end();) {         if (now - it->second.first > CONNECTION_TIMEOUT) {             // if last timestamp of connection is greater than 10 seconds, then it would mean there is no outgoing packet from the socket for more than 10 seconds             _cache.erase(it++);         } else {             ++it;         }     } } Crash is happening here if (now - it->second.first > CONNECTION_TIMEOUT). This is happening for iOS devices less than 15.0

What can be the possible reasons for the IPA size differences observed from the archived IPA vs the App Store connect reported for the same device variant ? While generating the archive below options are enabled to generate the archive. We are observing a difference of approximately 6 MB, where the IPA size read from the App-thinning.plist has a higher value. <key>compileBitcode</key> <true/> <key>uploadBitcode</key> <false/> <key>uploadSymbols</key> <false/> <key>destination</key> <string>export</string> <key>method</key> <string>development</string> <key>signingCertificate</key> <string>Apple Development</string> <key>signingStyle</key> <string>manual</string> <key>stripSwiftSymbols</key> <true/> <key>thinning</key> <string>iPhone10,1</string>

While generating the Xcode build with Address Sanitizer enabled, I am unable to launch the PacketTunnelProvider provider. The process is getting killed by the Operating System with the below exception "Thread 1: EXC_RESOURCE RESOURCE_TYPE_MEMORY (limit=50 MB, unused=0x0)" I understood that since Packettunnel Provider extension has only a memory limit of 50 MB, Operating System is killing the process. Is there any other way, we can overcome this limitation and perform Address Sanitizer testing ?

Pleasehelp me find out crash reason? I have attached the crash stack. report-2517633556170009999-ca213e2e-5d93-4607-bfbb-99f87a8b98c1.txt This is where we write to user defaults `18 Foundation 0x00000001844fb754 -[NSUserDefaults(NSUserDefaults) setObject:forKey:] + 80 19 ControlFilter 0x000000010054cfd8 -[FilterControlProvider startFilterWithCompletionHandler:] (FilterControlProvider.mm:101)`

Can anyone help me with how to interpret this crash log? I have attached the crash stack, it is reported only a particular user device and was reported multiple times. I have masked few keywords in the stack trace for confidentiality purpose Last Exception Backtrace: 0 CoreFoundation 0x197a67928 __exceptionPreprocess + 216 (NSException.m:199) 1 libobjc.A.dylib 0x1ab804480 objc_exception_throw + 56 (objc-exception.mm:565) 2 CoreFoundation 0x197975380 +[NSException raise:format:arguments:] + 96 (NSException.m:146) 3 Foundation 0x198cadef8 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 128 (NSException.m:231) 4 UIKitCore 0x19a30c274 -[UIApplication _performBlockAfterCATransactionCommits:] + 400 (UIApplication.m:3031) 5 UIKitCore 0x19a34c320 -[UIWindow _noteOverlayInsetsDidChange] + 140 (UIWindow.m:2276) 6 UIKitCore 0x199c3d4b0 -[UIViewController _setContentOverlayInsets:andLeftMargin:rightMargin:] + 608 (UIViewController.m:856) 7 UIKitCore 0x199c3ee9c __121-[UIViewController __updateContentOverlayInsetsWithOurRect:inBoundsOfAncestorViewController:viaImmediateChildOfAncestor:]_block_invoke + 424 (UIViewController.m:1175) 8 UIKitCore 0x199c3e5a4 -[UIViewController __updateContentOverlayInsetsWithOurRect:inBoundsOfAncestorViewController:viaImmediateChildOfAncestor:] + 2620 (UIViewController.m:1236) 9 UIKitCore 0x199c3e9ec -[UIViewController _updateContentOverlayInsetsFromParentIfNecessary] + 612 (UIViewController.m:1025) 10 UIKitCore 0x199c3d718 -[UIViewController _updateContentOverlayInsetsForSelfAndChildren] + 84 (UIViewController.m:900) 11 UIKitCore 0x199c49f90 -[UIViewController _updateLayoutForStatusBarAndInterfaceOrientation] + 636 (UIViewController.m:4013) 12 UIKitCore 0x199c4eb24 -[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:] + 208 (UIViewController.m:5447) 13 UIKitCore 0x19a8040dc -[UIView(Internal) _didMoveFromWindow:toWindow:] + 1244 (UIView.m:15144) 14 UIKitCore 0x19a7f8804 __45-[UIView(Hierarchy) _postMovedFromSuperview:]_block_invoke + 136 (UIView.m:11860) crash.txt

Due to loopback VPN implemented using PacketTunnelProvider, we observed issues regarding failing to update WatchOS. Is there any workaround for this ? Does WatchOS update is supported using proxy or VPN using Packet tunnel Provider ?

Hello I would like to know if Apple might reject an app during review if there is a navigation from App to settings programatically, as we have seen few stack-overflow links for the same. The below code will be executed on button press which takes the user to settings. if let appSettings = URL(string: UIApplication.openSettingsURLString) { UIApplication.shared.open(appSettings, options: [:], completionHandler: nil) Please let me know if any there is any chance of rejection with the above code.

While trying to add a new VPN configuration , the ios Network Extension fails for a particular device with my App with the following error default 23:34: 34.140388-0400 Adding 918D08B1-2814-47C0-AAA9-0A0A8C92049C to the loaded configurations  error 23:34:41.386023-0400 nehelper : Cannot save configuration , the total size of the NetworkExtension configuration is to large (2643248 bytes)  default 23:34:41.510241-0400 kernel memorystatus: set assertion priority(10) error The same behaviour is seen with other VPN Providers like Tunnel Bear. Question: As this issue is seen only on a particular device. Has anyone seen this issue/able to mitigate , and also shed more details why this issue happens.