I have a VPN app that has an embedded Network Extension. I wish to create a Widget based on the Network Extensions status. i.e Connect and what server/Country. If I take the traditional route of embedding the widget in the main app and call WidgetCenter.shared.reloadTimelines in the extension it works as expected, but ONLY if the parent app is still alive. The minute the parent app goes away calling WidgetCenter.shared.reloadTimelines does nothing. I have tried embedding the plugin inside of the Network Extension plugin but this as expected does not work. Is this a limitation of WidgetKit ( No ability to be updated from a running plugin)? Or is there a better way to update this widget

I'm having some issues tracking down the reason for the crash. It's affecting a ton of users but it seems to be a Swift runtime issue in Apples library. Can anyone help me out? Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001e920823c Exception Note: EXC_CORPSE_NOTIFY Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [5315] Triggered by Thread: 0 Kernel Triage: VM - Compressor failed a blocking pager_get Thread 0 name: Thread 0 Crashed: 0 BaseBoard 0x00000001e920823c -[_BSActionResponder action_sendResponse:] + 600 (BSActionResponder.m:127) 1 BaseBoard 0x00000001e9208234 -[_BSActionResponder action_sendResponse:] + 592 (BSActionResponder.m:127) 2 BaseBoard 0x00000001e9200e0c -[BSAction sendResponse:] + 92 (BSAction.m:311) 3 UIKitServices 0x00000001e8bea830 -[UISFetchContentInBackgroundAction sendResponse:] + 104 (UISFetchContentInBackgroundAction.m:53) 4 UIKitCore 0x00000001e6fd68b0 __91-[UIApplication _handleNonLaunchSpecificActions:forScene:withTransitionContext:completion:]_block_invoke_3 + 76 (UIApplication.m:10725) 5 UIKitCore 0x00000001e639cd38 -[_UIAfterCACommitBlock run] + 72 (_UIAfterCACommitQueue.m:137) 6 UIKitCore 0x00000001e62b00c8 -[_UIAfterCACommitQueue flush] + 192 (_UIAfterCACommitQueue.m:228) 7 UIKitCore 0x00000001e61d98e8 _runAfterCACommitDeferredBlocks + 644 (UIApplication.m:3038) 8 UIKitCore 0x00000001e61da00c _cleanUpAfterCAFlushAndRunDeferredBlocks + 132 (UIApplication.m:3002) 9 UIKitCore 0x00000001e61da1bc _afterCACommitHandler + 60 (UIApplication.m:3053) 10 CoreFoundation 0x00000001e3c45bb4 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 (CFRunLoop.c:1804) 11 CoreFoundation 0x00000001e3c14b70 __CFRunLoopDoObservers + 592 (CFRunLoop.c:1917) 12 CoreFoundation 0x00000001e3c0fc2c __CFRunLoopRun + 1052 (CFRunLoop.c:2979) 13 CoreFoundation 0x00000001e3c236b8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 14 GraphicsServices 0x00000001ffcbd374 GSEventRunModal + 164 (GSEvent.c:2200) 15 UIKitCore 0x00000001e6588e88 -[UIApplication _run] + 1100 (UIApplication.m:3511) 16 UIKitCore 0x00000001e630a5ec UIApplicationMain + 364 (UIApplication.m:5064) 17 Speedify 0x00000001047fb268 main + 88 (main.m:14) 18 dyld 0x0000000104b79ce4 start + 520 (dyldMain.cpp:879) [2022-04-20_14-33-40.1406_+0430-6f4f1f1ef853d8feea4fcea2cab39dba1183a769.crash](https://developer.apple.com/forums/content/attachment/f6a77cce-1618-4b7b-a027-368340a6ab7f)

Hello all, WWDC 2025 introduced Wi‑Fi Aware (NAN) support on iOS 26 for peer-to-peer discovery and direct connections, but I noticed macOS Tahoe doesn’t include it. I couldn’t find any references to Wi‑Fi Aware APIs or framework support in the macOS SDK. Is Apple planning to bring Wi‑Fi Aware to macOS? If so, will this come in a future update to macOS 26 (e.g., 26.x), or is it deferred to macOS 27 or beyond? Thanks for any insights!

How can I hide "App Frameworks" documentation? Seems like it's just cluttering my documentation, especially since I want to host on a website. O just want my imported documentation. I want to hide this:

We are using an NEPacketTunnel provider for our custom VPN solution, and doing so we are setting NEPacketTunnelNetworkSettings with setting IPv4 and IPv6 default routes. We are then setting DNS networkSettings.dnsSettings?.matchDomains = [""] However, apps like FaceTime still go around the VPN. Once you set setTunnelNetworkSettings is there no way to ask the system to return what the current saved configuration? Testing, Ive also tried turning off IPv6 on my home network and cell data to force all traffic to my IPv4 default routes. Ive seen FaceTime work on one session, relaunch the app and never again. Note: IncludeAllNetworks does work, but comes with a lot of downsides too. Our goal is to securely and redundantly help with video calls , streaming apps etc.

I’m working with the NEHotspotHelper API in my iOS app, and I noticed the following log message in Console: "(BUNDLE ID ) is using NEHotspotHelper API and it's unresponsive to API's evaluate command. The API gives 45 seconds to 3rd party apps to respond, and then it launches WebSheet to allow user to interact with the portal." I have two different apps that both register a NEHotspotHelper handler: App A checks for .evaluate and calls createResponse(.unsupportedNetwork) if we don’t manage that particular network. App B registers for hotspot events but does not handle .evaluate at all. In App A, whenever I see that “unresponsive” or “45 seconds” log, the system eventually launches the standard captive portal WebSheet. In App B, I never see those logs. I have a few questions: Are these “unresponsive” logs indeed triggered by the .evaluate command specifically? In other words, do we only see that 45-second timeout and the subsequent WebSheet message if our app is registered to handle Evaluate but doesn’t respond quickly (or responds with .unsupportedNetwork)? Is it best practice (or required) to always respond to .evaluate—for example, sending .unsupportedNetwork if we don’t plan on managing the user’s login or captive portal? Does ignoring .evaluate lead to other unexpected behavior or logs? Should we still explicitly respond to Evaluate with .unsupportedNetwork? Or is it okay to skip Evaluate handling entirely on every app or invocation? I’d love to confirm whether .evaluate handling is the direct cause of these logs, and how best to avoid the “unresponsive”/“45 seconds” fallback if our app isn’t intended to manage the portal. Thanks in advance for any insights!

Am I able to add a subscriber inside of my Network Extension to receive reports?

I'm not quite understanding why my application would be receiving this error Error Domain=NEHotspotConfigurationErrorDomain Code=13 "already associated." UserInfo={NSLocalizedDescription=already associated.} The helper seems to work but when this error occurs the command and network list is nil Any help would be appreciated, thank you!

Users can now access the WiFi settings right from the control center and by long pressing the WiFi icon. I noticed when a user accesses the WiFi list in this manner the Hotspot Helper callback functions do not get invoked. Is this intended behavior? Thank you for your time

I have an app that utilizes the Network Extension ( Packet Tunnel Provider ), but also uses MDNS to find local devices for data transfer via Network Extensions. However, once connected over Peer to Peer using AWDL0 or NWConnections, it works as expected until a user shuts the screen down. It looks like there's a difference in behavior when the device is plugged in vs when it's on just battery alone. So we can be happily sending data over p2p ( awdl0 ) then a screen shuts off and it kills the connection. Is this expected behavior and if so is there documentation? Also, Network Extensions do not appear to be able to discover over P2P, they can only connect to endpoints directly. Is this expected behavior? My thoughts; If a user allows both the Network Extension Permission and Local Network Permissions that the Network Extension should be able to discover peers via p2p. The connections ( if not asleep ) should stay active while in use.