Networking

RSS for tag

Explore the networking protocols and technologies used by the device to connect to Wi-Fi networks, Bluetooth devices, and cellular data services.

Networking Documentation

Posts under Networking subtopic

Post

Replies

Boosts

Views

Activity

Networking Resources
General: Forums subtopic: App & System Services > Networking TN3151 Choosing the right networking API Networking Overview document — Despite the fact that this is in the archive, this is still really useful. TLS for App Developers forums post Choosing a Network Debugging Tool documentation WWDC 2019 Session 712 Advances in Networking, Part 1 — This explains the concept of constrained networking, which is Apple’s preferred solution to questions like How do I check whether I’m on Wi-Fi? TN3135 Low-level networking on watchOS TN3179 Understanding local network privacy Adapt to changing network conditions tech talk TCP and UDP ports used by Apple software products support article Understanding Also-Ran Connections forums post Extra-ordinary Networking forums post Foundation networking: Forums tags: Foundation, CFNetwork URL Loading System documentation — NSURLSession, or URLSession in Swift, is the recommended API for HTTP[S] on Apple platforms. Moving to Fewer, Larger Transfers forums post Testing Background Session Code forums post Network framework: Forums tag: Network Network framework documentation — Network framework is the recommended API for TCP, UDP, and QUIC on Apple platforms. WWDC 2025 Session 250 Use structured concurrency with Network framework — This is a great introduction to the new Network framework API introduced in appleOS 2026. Building a custom peer-to-peer protocol sample code (aka TicTacToe) Implementing netcat with Network Framework sample code (aka nwcat) Configuring a Wi-Fi accessory to join a network sample code Moving from Multipeer Connectivity to Network Framework forums post NWEndpoint History and Advice forums post Wi-Fi (general): How to modernize your captive network developer news post Wi-Fi Fundamentals forums post Filing a Wi-Fi Bug Report forums post Working with a Wi-Fi Accessory forums post — This is part of the Extra-ordinary Networking series. Wi-Fi (iOS): TN3111 iOS Wi-Fi API overview technote Wi-Fi Aware framework documentation Building peer-to-peer apps sample code WirelessInsights framework documentation iOS Network Signal Strength forums post Network Extension Resources Wi-Fi on macOS: Forums tag: Core WLAN Core WLAN framework documentation Secure networking: Forums tags: Security Apple Platform Security support document Preventing Insecure Network Connections documentation — This is all about App Transport Security (ATS). WWDC 2017 Session 701 Your Apps and Evolving Network Security Standards [1] — This is generally interesting, but the section starting at 17:40 is, AFAIK, the best information from Apple about how certificate revocation works on modern systems. WWDC 2025 Session 314 Get ahead with quantum-secure cryptography Available trusted root certificates for Apple operating systems support article Requirements for trusted certificates in iOS 13 and macOS 10.15 support article About upcoming limits on trusted certificates support article Apple’s Certificate Transparency policy support article What’s new for enterprise in iOS 18 support article — This discusses new key usage requirements. Prepare your network environment for stricter security requirements support article — This is primarily of interest to folks developing management software, for example, an MDM server. Technote 2232 HTTPS Server Trust Evaluation Technote 2326 Creating Certificates for TLS Testing QA1948 HTTPS and Test Servers Miscellaneous: More network-related forums tags: 5G, QUIC, Bonjour On FTP forums post Using the Multicast Networking Additional Capability forums post Investigating Network Latency Problems forums post Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] This video is no longer available from Apple, but the URL should help you locate other sources of this info.
0
0
6.9k
Sep ’26
macOS: supported absolute deadline at final network egress, including queued bytes?
Hi, I’m assessing feasibility before implementing a small macOS HTTPS snapshot client. The requirement is strict: every request-bearing byte must cross the final controlled network-egress boundary before an absolute deadline. A byte crossing at or after the deadline fails. For context, the intended deadline is 07:41:00 Europe/London on a specified date, converted to UTC. This concerns request transmission, not response completion. An application precheck or a deadline to begin sending would not satisfy it. Is there a supported macOS API or mechanism with a documented guarantee covering this requirement? Specifically: Where is the enforcement boundary? Does expiry cover request bytes already queued in TLS/TCP, kernel, driver or NIC buffers, partially transmitted requests, and retransmitted request payload? Does enforcement remain fail-closed if the client or enforcement process is suspended, hangs or crashes, or the Mac sleeps and wakes? Can queued bytes resume transmission after expiry? What clock and deadline semantics apply, including equality, uncertainty, clock steps/regression and unavailable or unreliable time? Can connection reuse or buffering bypass expiry? Application retries, redirects and additional requests would be prohibited. How could an implementation observe and qualify the actual controlled egress boundary, rather than an earlier callback or queue? I have reviewed documentation for: NWConnection.ContentContext.expirationMilliseconds, which describes expiry for beginning transmission; NWConnection.SendCompletion.contentProcessed; Network Extension packet filtering, delayed-packet verdicts and provider lifecycle; TN3134 and TN3165. I have not found a documented end-to-end guarantee covering the cases above. I am not assuming that filters, cancellation, timers or socket timeouts provide it. Could an Apple engineer point to the applicable supported contract and platform restrictions, or clarify that this strict guarantee is not provided? If a mechanism is applicable, please identify supported macOS versions, required entitlements and any relevant interface or hardware limitations. This is a documentation/feasibility question only. No external service, account, credentials or capture is involved. An authoritative reference—or an explicit statement of unsupported cases—would be helpful. Many thanks in advance.
0
0
12
1h
Network Extension Issue - No cfil verdict callback registered - (27.3 beta 2)
I've filed FB25612343 in case others see it as well where 27.3b2 seems to cause issues with our network extension transparent proxy. The sysdiagnose shows the failure inside Network Extension, in the redirector process. Those lines (flow is closed for writes, Failed to write flow Data, No cfil verdict callback registered) are Apple's. There is no crash.Has anyone else seen issues on the latest beta?
6
0
132
1d
NEURLFilter: neagent keeps every prefilter in memory and is killed at ~90 MiB when a VPN shares it
Hello, We are building a URL filter with NEURLFilterControlProvider and PIR on iOS 27.2. Our blocklist needs to scale to 50 million URLs at a 0.1% false-positive rate. Following the documented Bloom filter format, that is a prefilter of 718,879,379 bits with 10 hash functions (89,859,923 bytes), which we return from fetchPrefilter(existingPrefilterTag:) as NEURLFilterPrefilter.PrefilterData.temporaryFilepath. On an iPhone 17 running iOS 27.2, we see two behaviours that make a prefilter of this size unreliable for users who also run a VPN. neagent keeps each prefilter it receives in its own memory and does not release the previous one After the first handover, neagent's memory footprint was 89.6 MiB, almost all of it anonymous memory, even though lookups are served from the mmap'd file under /private/var/db/urlPrefilter/. Each time we returned a new prefilter (with a new tag), the footprint grew by the size of the new bitmap, in the same neagent process: 89.6 MiB, then 150.8 MiB after a 64 MB prefilter, then 236.9 MiB after another 90 MB prefilter. It stayed at that level for the more than 25 minutes we observed. With no other network extension installed, neagent was not terminated at 236.9 MiB. When a packet tunnel VPN shares the same neagent, neagent is terminated at about 90 MiB With a packet tunnel VPN enabled (Tailscale), which iOS hosts in the same neagent process as our URL filter, neagent was terminated with JETSAM_REASON_MEMORY_HIGHWATER while holding a single prefilter at 89.4–89.7 MiB. This happened 11 and 35 minutes after start in our latest runs, with no PIR lookups and no new prefilter, and repeatedly in earlier runs (between 3 seconds and 52 minutes after start). Each termination stops both sessions: the URL filter with "Plugin failed" and the VPN with "Plugin initiated". Both restart a few seconds later, and the cycle repeats. Because a new prefilter adds a full copy (finding 1), any prefilter update also takes neagent over this limit straight away. Our questions: What is the largest NEURLFilterPrefilter that iOS supports, and does the limit depend on the device? Is neagent meant to keep the whole bitmap in its own memory, rather than read it from the mmap'd file? Should the previous prefilter's memory be released when a new one is installed? If not, how often should a control provider return a new prefilter? Is neagent's memory limit lower when a VPN shares the process, and is that intended? Can a URL filter run in its own neagent process? What approach do you recommend for a blocklist of tens of millions of URLs at a 0.1% false-positive rate? Thank you, David. Apple Developer Team ID: SSYCLSN43U
0
0
43
2d
Network Extension URL Filter registration pending review for more than a month
Hello, I am writing about a Network Extension URL Filter configuration submitted through the Identity & Trust section of the CloudKit Console on 5 September 2026 Status shown: In Review / Waiting for Approval Last Modified: 5 September 2026 (unchanged since submission) It has now been 37 days with no response — no approval, no rejection, and no request for changes. The PIR server , Privacy Pass issuer and HTTP/2 OHTTP gateway have been live and serving since the day of submission, configured per the Onboarding.md guidance in Apple's PIR service example, including the apple-url-filter DNS TXT record on the service URL and the url-filter-test validation entry. Could anyone please let me know: Whether this configuration is actually in a review queue, and the expected timeframe; Whether anything further is required from our side — if so, we will act on it the same day. The URL filter is a core protection feature of our app, which is currently in App Store review; the feature stays disabled for users until this registration is approved, so the delay is holding up what we can ship. Thank you for your help.
5
0
319
2d
Local Push Connectivity entitlement request — no response after a month (again)
Hi all, I’m hoping someone from Apple can point me in the right direction. We submitted a request for the Local Push Connectivity entitlement about a month ago and haven’t heard anything back. No approval, no rejection, just silence. Unfortunately this is the second time; we tried back in 2023 and the same thing happened. After requesting the entitlement multiple times, we gave up on the project. A bit about what we’re building: we make a nurse call system for long-term care facilities. When a resident needs help, they press a wireless call device, our on-prem server raises an alert, and our iOS app would notify the caregivers on shift. The catch is that a most of these facilities put their life safety systems on air-gapped networks with no internet access at all, so APNs just isn’t an option. Even where there is internet, the system has to keep working if the connection goes down. We understand other vendors in our industry use Local Push Connectivity for this same scenario, so we’re hopeful this is just a matter of our request getting lost somewhere. As far as I can tell, this is exactly what Local Push Connectivity was made for. The WWDC20 session that introduced it (“Build local push connectivity for restricted networks”) actually names hospitals as one of the example environments where APNs may be unreachable, and talks about keeping notifications working in constrained networks “when it matters most to the users.” A resident calling for help is about as close to that as it gets. Our App ID already has the Critical Alerts entitlement, but there’s no “Network Extensions (additional values)” option under Additional Capabilities, so Xcode, understandably, complains that the profile doesn’t match the com.apple.developer.networking.networkextension value in our entitlements file. Is there a way to check on the status of a request like this, or a better place to follow up? I’m happy to share our team and app details privately. Any help would be really appreciated. We’ve been trying to get this going for a while now. Thanks!
0
0
41
2d
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
7
0
347
3d
macOS Transparent Proxy fails to start before login on Wi-Fi: "No network available"
I'm investigating an issue when deploying my VPN agent via Jamf during initial setup on clean macOS machines. The Network Extension process starts immediately after installation, but its Transparent Proxy provider starts only after a user logs in. I tried to reboot, and still observed the transparent proxy start fails. 10:00:52 === system boot 10:00:57.535 NESMTransparentProxySession[Primary Tunnel:Prisma Access Agent:68CAC11B-...]: Received a start command from PASrv[303] 10:00:57.538 NESMTransparentProxySession[...]: No network available <<<<<<<<< 10:00:57.541 NESMTransparentProxySession[...]: status changed to disconnected, last stop reason No network available <<<<<<<<< 10:01:21.541 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:01:26.373 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:06:01.293 NESMTransparentProxySession[...]: Received a start command from user_context[1547] 10:06:01.615 NESMTransparentProxySession[...]: status changed to connectedOur product requires pre-login functionality. Is this behavior expected, and how can we enable the Transparent Proxy provider before user login? I suspect a race between network availability and the attempt to start the Transparent Proxy. The issue does not occur with Ethernet, possibly because connectivity becomes available earlier than with Wi-Fi. Should we call startVPNTunnel again once connectivity becomes available? If so, what is the recommended way to detect this network transition?
5
0
156
4d
Local Network Privacy Child Process Behavior
I have a Java Swing application that is bundled into an app bundle using jpackage. The app basically launches a newer version of itself, when there is a new version downloaded in the users installation directory. I have noticed a regression or change in behavior with how LocalNetwork privacy works now. Previously, we would launch our Java application using the .app bundle. This is a launcher that checks for updates and will launch another JVM instance using any new jars it downloads when updating. So, it is closing the original process and spawning a new process using the downloaded jar. The new process is where the app connects to a server on the Local Network. This new process cannot access the Local Network even when the entry in privacy and security is enabled for the parent process. I have changed the behavior of my launcher application so that it keeps the process alive after launching the client application. When doing this, Local Network access works. So, my question is: is it required for the parent process to be running in order for a child process to have Local Network access? In previous macOS versions, this was not an issue, so something has changed with Local Network security across all the latest versions 26 and 27.
8
0
256
5d
WCSession.sendMessage is crashing when a reply or error handler is attached, why?
The following code should send a message from the watch to the iPhone. Unfortunately, it is crashing. I have no clue why. if WCSession.isSupported() { let session = WCSession.default if ((session.activationState == .activated) && session.isReachable) { session.sendMessage(["SimpleMessages":["start"]], replyHandler:{reply in _ = 0 }, errorHandler:nil) } } If the reply handler is set to nil, the code does not crash. Anyway, in both cases the message is correctly sent from the watch to the phone. The code itself is run on the main thread (verified). I am running watchOS 26.6 and iOS 27. Here is the crash : Stack trace
4
0
386
5d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
1
0
106
5d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
5
0
341
5d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
1
0
92
5d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
3
0
380
6d
MobileVLCKit (3.7.3) triggering Local Network permission
The problem manifests itself from 16 to 18 iOS not inclusive Versions from 18 up to and including do not cause this problem. When initializing the player, a request for permission to use the local network appears. The application does not use a local network as a capability, even in plist there is no such key. Apple has granted permission to use multicast networking, and the corresponding capability has also been added. The player is assembled as let player = VLCMediaPlayer() player.media = mediaHaving previously collected media with the options "clock-synchro=..." "avcodec-threads=..." "rtsp-tcp" "network-caching=..." "live-caching=..." "-vv" "clock-jitter=..."and "no-audio", "--no-sout-audio" to mute the audio for the picture during the call How to prevent a library from accessing the local network?
1
0
64
1w
iPhone 16e on iOS 27.2.1 intermittently misses BLE extended advertisements until Reset Location & Privacy
I’m investigating intermittent discovery of QuadSense V40.0 sensors on an iPhone 16e running iOS 27.2.1 (24B156). Legacy advertising units remain discoverable, but the phone sometimes misses the V40 units entirely. I’ve also seen intermittent discovery in BLESerial. The V40 uses connectable BLE 5.0 extended advertising, with a 1M primary PHY, 2M secondary PHY, and an advertising interval of about 1 second. The advertisement includes the QuadSense local name and manufacturer data with ID 0xFF02 and a 25-byte payload. During the failure: A native CBCentralManager scan with no service filter and duplicate reports enabled received 4,821 discovery callbacks in 90 seconds, including a legacy QuadSense, but zero matching extended reports. A nearby Mac received 25 matching advertisements during its overlapping scan. The iPhone probe bypassed our Flutter scan and filtering code. After Reset Location & Privacy: The same iPhone reported two V40.0 units within 1.6 seconds. Both were reported as connectable. Core Bluetooth delivered 11 matching advertisements in 10 seconds, and our app accepted both units. Bluetooth authorization was .allowedAlways in both runs. I saw the related extended advertising thread, where Apple clarified that r.188123531 affects iPhone 17 and newer. I’m posting separately because this reproduction is on a 16e and 16. Has anyone seen this on the 16e, or found a way to isolate what changes after Reset Location & Privacy when Bluetooth authorization was already granted? I’m setting up controller traces to compare a working scan with the next failure before resetting again. I’d appreciate guidance on which trace events and sysdiagnose details would be most useful to Apple.
2
0
158
1w
Choosing a TLS server identity by client address with NWListener
I run an HTTPS server on NWListener (iOS and macOS) that serves several identities from one listener on port 443, picked per handshake in sec_protocol_options_set_challenge_block, as suggested in this thread. That works well for every handshake that carries a server name. The trouble is handshakes without one. Clients on the LAN connect by IP address, so they send no SNI (RFC 6066 keeps IP literals out of it), and they trust a self-signed certificate through a configuration profile. Internet clients and scanners that reach the public address through the router's port forward also often arrive without SNI. The two groups should get different certificates, and the only thing that tells them apart is the client's address. The listener knows it in newConnectionHandler, but the challenge block never sees it. What I tried: sec_protocol_metadata_t has accessors for the server name, ALPN, version, cipher suite and so on, but I can't find one for the connection's endpoints. Setting a challenge block on the accepted connection's own TLS options before start(): listener.newConnectionHandler = { connection in let remote = connection.endpoint if let tls = connection.parameters.defaultProtocolStack.applicationProtocols .compactMap({ $0 as? NWProtocolTLS.Options }).first { sec_protocol_options_set_challenge_block(tls.securityProtocolOptions, { _, complete in complete(identity(for: remote)) }, queue) } connection.start(queue: queue) }This block never runs. The listener's own block answers every handshake (tested on macOS 27.2). My questions: Is there a supported way to choose the server identity per connection based on its endpoints, short of terminating TLS myself? Is the challenge block supported under TLS 1.3 by now? I also see it run twice for every handshake; is that expected? When a server-side handshake fails, connection.metadata(definition: NWProtocolTLS.definition) returns nil. Is there any way to learn which server name a failed handshake asked for, so it can be logged? I filed FB25541009 with a small sample project that shows all three.
2
0
90
1w
URL Filter (Oblivious HTTP) configuration In Review for almost a week with no feedback
Hello, I submitted a Network Extension URL Filter (Oblivious HTTP) configuration in CloudKit Console almost a week ago. It still says In Review / Waiting for Approval and I haven't heard anything back since the submission notice. I wanted to check whether anything is missing on my end. Just in case, the configuration ID is 60802ed4-abfa-4b20-a64e-0d35230f478a. The app is an open-source ad and tracker blocker from the developers of an existing content blocker with a large user base. On iPhone and iPad its system-wide blocking runs entirely through the URL filter. Until the configuration is approved the iOS app can't block anything at all, and our testers are left with a Mac-only product in the meantime. Because lookups go through Apple's relay to our own PIR server, we never learn which sites anyone visits. All four endpoints have been live since the day I submitted and the TXT records are in place. Every database we build also includes the www.apple.com/url-filter-test validation entry. Is there anything else I need to provide, or a rough timeline I should expect? Thank you in advance!
1
0
86
1w
BLE IOS27. When the device is connected to headphones, the Bluetooth controller does not tend to perform normal scheduling on BLE
We have an internet app that uses BLE COC to synchronize the call audio of Android devices to the iPhone side microphone. All of this functions normally, but if two conditions are met: upgrading to IOS27; Connect iPhone to headphones. So the up and down latency of our BLE COC data will be significant and increase proportionally with time. Through the analysis of the air interface logs, it can be seen that the number of retries for COC data on the air interface has significantly increased, and the interval between the other two packets is very large (far greater than the 30 millisecond conn interval). I would like to ask if Apple has adjusted the scheduling strategy of the Bluetooth controller on iOS 27, and how can we adapt to this situation? The attachment is a screenshot of the air interface log. The packet circled in the picture is sent from iPhone to Android, with an interval of 300+ms. It can be inferred that the iPhone protocol stack and Bluetooth controller have already squeezed a large amount of data, and our business bitrate is not high, only about 10K per second
4
0
160
1w
[macOS 27.2]: System-Wide DNS Resolution Failures After Sleep/Wake – mDNSResponder and NETransparentProxyProvider
Summary Recent macOS release observed intermittent system-wide DNS failures after sleep/wake on multiple devices running Global Secure Access (GSA) with NETransparentProxyProvider. Previously successful DNS lookups time out after wake across applications, including browsers and GSA. Two captures contain failure-time evidence of the mDNSResponder resolver queue predominantly waiting in close()/kernel. Other captures show similar DNS failures, but a shared root cause has not been established. Call chain, from thread entry to kernel wait: start_wqthread + 8 _pthread_wqthread + 292 _dispatch_workloop_worker_thread + 720 _dispatch_root_queue_drain_deferred_wlh + 284 _dispatch_lane_invoke + 392 _dispatch_lane_serial_drain + 332 _dispatch_source_invoke + 920 _dispatch_source_cancel_callout + 208 _dispatch_continuation_pop + 596 _dispatch_client_callout + 16 close + 8 fleh_synchronous + 72 sleh_synchronous (sleh.c:1610) unix_syscall (systemcalls.c:181) fp_close_and_unlock_with_action (kern_descrip.c:1874) fg_drop (kern_descrip.c:287) soclose (uipc_socket.c:1345) soclose_locked (uipc_socket.c:1138) cfil_sock_close_wait (content_filter.c:5743) soflow_db_apply (socket_flows.c; line unavailable) cfil_filters_udp_attached_per_flow (content_filter.c:6675) _sleep (kern_synch.c:213) lck_mtx_sleep_deadline (locks.c:1583) thread_block_reason (sched_prim.c:4060) thread_invoke (sched_prim.c:3443) Steps to reproduce The issue is intermittent. These steps describe the observed sequence, not a deterministic minimal reproduction. Run the GSA client using NETransparentProxyProvider. The affected configurations also have Microsoft Defender network extensions active. Verify that a system DNS lookup succeeds for a known hostname. Allow the Mac to sleep, including maintenance DarkWake cycles. Wake the Mac and repeat system DNS lookups or use applications requiring hostname resolution. Observe repeated approximately 30-second lookup timeouts, sometimes longer. Observed results November 5, 2026 - UTC+05:30 capture User-reported impact: Recurrence of the same sleep/wake connectivity symptoms. OS: macOS 27.2 (26B123). Incident window: 20:38-20:41 IST / 15:08-15:11 UTC. The same Chrome client/name A lookup succeeds earlier in 12.984 ms but times out after wake in 29,999.705 ms. The DNS service/server route changed, so this is not a controlled identical-network comparison. The resolver records 1,007 timeout callbacks during the incident window, across browsers, Teams, GSA, Defender and other processes. The failure-time spindump at 20:40:21.009-20:40:31.013 IST shows the original mDNSResponder PID 78534 with 715/715 resolver-queue samples under dispatch-source cancellation → close() → kernel → lck_mtx_sleep_deadline. Source: spindump.txt:75998-76093. This establishes a sampled wait, not a permanent deadlock or proof of the same root cause as November 2. The file descriptor and kernel/filter wait owner remain unidentified. A later matching Chrome lookup returns an address at 20:43:18.191816 IST on the same resolver PID, without a recorded resolver restart. This establishes some recovery, not that every application or tunnel recovered. November 2, 2026 - UTC-08:00 capture User-reported impact: No network upon wake. This eventually resolves without a reboot, after approximately 5 to 15 minutes of waiting. OS: macOS 27.2 (26B123). Incident window: 09:40-09:45 PST / 17:40-17:45 UTC. The same Edge A lookup succeeds before sleep in 19.346 ms but times out after wake in 29,999.826 ms. The resolver records 1,403 timeout callbacks during the incident window. The failure-time spindump shows 770/777 resolver-queue samples under dispatch-source cancellation → close() → kernel; 769 include lck_mtx_sleep_deadline. This establishes a dominant sampled wait, not a permanent deadlock. The file descriptor and kernel/filter wait owner remain unidentified. November 3, 2026 - UTC-08:00 capture (Mihai) Evidence: mihai_gsa_error.tar.gz The following example records a failure resolving GSA’s own control-plane endpoint, whose DNS lookup is not intercepted by the GSA tunnel. Times in these excerpts are local (UTC-08:00). GSA error [2026-11-03 10:13:58.463] Network connection to the Global Secure Access Edge could not be established StreamId: ControlStream Hostname: <tenant>.auth.client.globalsecureaccess.microsoft.com:443 Error: hostname lookup error: Address lookup failed os_error: nodename nor servname provided, or not known syscall: getaddrinfo mDNSResponder records 10:13:19.663661 [R125367->DupQ50990->Q38408] Duplicate question <private> dn:04wpeA (Addr) 10:13:58.468519 [R125367] DNSServiceQueryRecord STOP -- name hash: dn:04wpeA, duration: 39s 10:13:59.078847 [R125340] QueryRecordOpCallback: Question <private> dn:04wpeA (Addr) timing out, InterfaceID 0x0 Additional observations The original resolver records 11 timeout callbacks across GSA, Defender, Spotify and the system time service. A GSA A-query returns a positive result in 1.282 ms earlier (cache-compatible, not a cold upstream baseline), then the same client/name/qtype/flags times out after 41.865784 wall-clock seconds; that interval includes sleep. The DNS service/server set changes, so this is not a controlled same-network comparison. At 09:40 PST the Wi-Fi interface becomes inactive and loses its IPv4 address, followed by no-dns-service results. The first native lookup errors precede this link loss; it does not explain the entire case. Four GSA A/AAAA timeout transactions have matching late UDP replies. For one A-query, the reply is logged 25.095999 seconds after its matching send and 7.197434 seconds after the API timeout, during shutdown. 48 acceptable UDP response records appear within 1.467 ms. The location of the delay is not identified.
5
1
465
1w
Is it safe to strip with All Symbols for a content filter?
We would like to minimise the amount of code exposed in the product we have developed and an obvious option is to configure our build setting to use the All Symbols for Strip Style. Some investigation with an AI tool reports there are possible problems doing so. ContentFilter: non-global → all — risky. The NetworkExtension and XPC subsystems load your bundle and look up classes by name through the ObjC runtime, which uses __objc_classlist and friends (not the Mach-O symbol table), so in principle all works. In practice it occasionally breaks bundle loading in edge cases. If you try this, test specifically that systemextensionsctl activates the bundle and the filter actually traps packets. Is it safe to use All Symbols with a content filter or do we need to accept Non-Global symbols? Thanks, Dave
1
0
176
1w
Networking Resources
General: Forums subtopic: App & System Services > Networking TN3151 Choosing the right networking API Networking Overview document — Despite the fact that this is in the archive, this is still really useful. TLS for App Developers forums post Choosing a Network Debugging Tool documentation WWDC 2019 Session 712 Advances in Networking, Part 1 — This explains the concept of constrained networking, which is Apple’s preferred solution to questions like How do I check whether I’m on Wi-Fi? TN3135 Low-level networking on watchOS TN3179 Understanding local network privacy Adapt to changing network conditions tech talk TCP and UDP ports used by Apple software products support article Understanding Also-Ran Connections forums post Extra-ordinary Networking forums post Foundation networking: Forums tags: Foundation, CFNetwork URL Loading System documentation — NSURLSession, or URLSession in Swift, is the recommended API for HTTP[S] on Apple platforms. Moving to Fewer, Larger Transfers forums post Testing Background Session Code forums post Network framework: Forums tag: Network Network framework documentation — Network framework is the recommended API for TCP, UDP, and QUIC on Apple platforms. WWDC 2025 Session 250 Use structured concurrency with Network framework — This is a great introduction to the new Network framework API introduced in appleOS 2026. Building a custom peer-to-peer protocol sample code (aka TicTacToe) Implementing netcat with Network Framework sample code (aka nwcat) Configuring a Wi-Fi accessory to join a network sample code Moving from Multipeer Connectivity to Network Framework forums post NWEndpoint History and Advice forums post Wi-Fi (general): How to modernize your captive network developer news post Wi-Fi Fundamentals forums post Filing a Wi-Fi Bug Report forums post Working with a Wi-Fi Accessory forums post — This is part of the Extra-ordinary Networking series. Wi-Fi (iOS): TN3111 iOS Wi-Fi API overview technote Wi-Fi Aware framework documentation Building peer-to-peer apps sample code WirelessInsights framework documentation iOS Network Signal Strength forums post Network Extension Resources Wi-Fi on macOS: Forums tag: Core WLAN Core WLAN framework documentation Secure networking: Forums tags: Security Apple Platform Security support document Preventing Insecure Network Connections documentation — This is all about App Transport Security (ATS). WWDC 2017 Session 701 Your Apps and Evolving Network Security Standards [1] — This is generally interesting, but the section starting at 17:40 is, AFAIK, the best information from Apple about how certificate revocation works on modern systems. WWDC 2025 Session 314 Get ahead with quantum-secure cryptography Available trusted root certificates for Apple operating systems support article Requirements for trusted certificates in iOS 13 and macOS 10.15 support article About upcoming limits on trusted certificates support article Apple’s Certificate Transparency policy support article What’s new for enterprise in iOS 18 support article — This discusses new key usage requirements. Prepare your network environment for stricter security requirements support article — This is primarily of interest to folks developing management software, for example, an MDM server. Technote 2232 HTTPS Server Trust Evaluation Technote 2326 Creating Certificates for TLS Testing QA1948 HTTPS and Test Servers Miscellaneous: More network-related forums tags: 5G, QUIC, Bonjour On FTP forums post Using the Multicast Networking Additional Capability forums post Investigating Network Latency Problems forums post Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] This video is no longer available from Apple, but the URL should help you locate other sources of this info.
Replies
0
Boosts
0
Views
6.9k
Activity
Sep ’26
macOS: supported absolute deadline at final network egress, including queued bytes?
Hi, I’m assessing feasibility before implementing a small macOS HTTPS snapshot client. The requirement is strict: every request-bearing byte must cross the final controlled network-egress boundary before an absolute deadline. A byte crossing at or after the deadline fails. For context, the intended deadline is 07:41:00 Europe/London on a specified date, converted to UTC. This concerns request transmission, not response completion. An application precheck or a deadline to begin sending would not satisfy it. Is there a supported macOS API or mechanism with a documented guarantee covering this requirement? Specifically: Where is the enforcement boundary? Does expiry cover request bytes already queued in TLS/TCP, kernel, driver or NIC buffers, partially transmitted requests, and retransmitted request payload? Does enforcement remain fail-closed if the client or enforcement process is suspended, hangs or crashes, or the Mac sleeps and wakes? Can queued bytes resume transmission after expiry? What clock and deadline semantics apply, including equality, uncertainty, clock steps/regression and unavailable or unreliable time? Can connection reuse or buffering bypass expiry? Application retries, redirects and additional requests would be prohibited. How could an implementation observe and qualify the actual controlled egress boundary, rather than an earlier callback or queue? I have reviewed documentation for: NWConnection.ContentContext.expirationMilliseconds, which describes expiry for beginning transmission; NWConnection.SendCompletion.contentProcessed; Network Extension packet filtering, delayed-packet verdicts and provider lifecycle; TN3134 and TN3165. I have not found a documented end-to-end guarantee covering the cases above. I am not assuming that filters, cancellation, timers or socket timeouts provide it. Could an Apple engineer point to the applicable supported contract and platform restrictions, or clarify that this strict guarantee is not provided? If a mechanism is applicable, please identify supported macOS versions, required entitlements and any relevant interface or hardware limitations. This is a documentation/feasibility question only. No external service, account, credentials or capture is involved. An authoritative reference—or an explicit statement of unsupported cases—would be helpful. Many thanks in advance.
Replies
0
Boosts
0
Views
12
Activity
1h
Network Extension Issue - No cfil verdict callback registered - (27.3 beta 2)
I've filed FB25612343 in case others see it as well where 27.3b2 seems to cause issues with our network extension transparent proxy. The sysdiagnose shows the failure inside Network Extension, in the redirector process. Those lines (flow is closed for writes, Failed to write flow Data, No cfil verdict callback registered) are Apple's. There is no crash.Has anyone else seen issues on the latest beta?
Replies
6
Boosts
0
Views
132
Activity
1d
NEURLFilter: neagent keeps every prefilter in memory and is killed at ~90 MiB when a VPN shares it
Hello, We are building a URL filter with NEURLFilterControlProvider and PIR on iOS 27.2. Our blocklist needs to scale to 50 million URLs at a 0.1% false-positive rate. Following the documented Bloom filter format, that is a prefilter of 718,879,379 bits with 10 hash functions (89,859,923 bytes), which we return from fetchPrefilter(existingPrefilterTag:) as NEURLFilterPrefilter.PrefilterData.temporaryFilepath. On an iPhone 17 running iOS 27.2, we see two behaviours that make a prefilter of this size unreliable for users who also run a VPN. neagent keeps each prefilter it receives in its own memory and does not release the previous one After the first handover, neagent's memory footprint was 89.6 MiB, almost all of it anonymous memory, even though lookups are served from the mmap'd file under /private/var/db/urlPrefilter/. Each time we returned a new prefilter (with a new tag), the footprint grew by the size of the new bitmap, in the same neagent process: 89.6 MiB, then 150.8 MiB after a 64 MB prefilter, then 236.9 MiB after another 90 MB prefilter. It stayed at that level for the more than 25 minutes we observed. With no other network extension installed, neagent was not terminated at 236.9 MiB. When a packet tunnel VPN shares the same neagent, neagent is terminated at about 90 MiB With a packet tunnel VPN enabled (Tailscale), which iOS hosts in the same neagent process as our URL filter, neagent was terminated with JETSAM_REASON_MEMORY_HIGHWATER while holding a single prefilter at 89.4–89.7 MiB. This happened 11 and 35 minutes after start in our latest runs, with no PIR lookups and no new prefilter, and repeatedly in earlier runs (between 3 seconds and 52 minutes after start). Each termination stops both sessions: the URL filter with "Plugin failed" and the VPN with "Plugin initiated". Both restart a few seconds later, and the cycle repeats. Because a new prefilter adds a full copy (finding 1), any prefilter update also takes neagent over this limit straight away. Our questions: What is the largest NEURLFilterPrefilter that iOS supports, and does the limit depend on the device? Is neagent meant to keep the whole bitmap in its own memory, rather than read it from the mmap'd file? Should the previous prefilter's memory be released when a new one is installed? If not, how often should a control provider return a new prefilter? Is neagent's memory limit lower when a VPN shares the process, and is that intended? Can a URL filter run in its own neagent process? What approach do you recommend for a blocklist of tens of millions of URLs at a 0.1% false-positive rate? Thank you, David. Apple Developer Team ID: SSYCLSN43U
Replies
0
Boosts
0
Views
43
Activity
2d
Network Extension URL Filter registration pending review for more than a month
Hello, I am writing about a Network Extension URL Filter configuration submitted through the Identity & Trust section of the CloudKit Console on 5 September 2026 Status shown: In Review / Waiting for Approval Last Modified: 5 September 2026 (unchanged since submission) It has now been 37 days with no response — no approval, no rejection, and no request for changes. The PIR server , Privacy Pass issuer and HTTP/2 OHTTP gateway have been live and serving since the day of submission, configured per the Onboarding.md guidance in Apple's PIR service example, including the apple-url-filter DNS TXT record on the service URL and the url-filter-test validation entry. Could anyone please let me know: Whether this configuration is actually in a review queue, and the expected timeframe; Whether anything further is required from our side — if so, we will act on it the same day. The URL filter is a core protection feature of our app, which is currently in App Store review; the feature stays disabled for users until this registration is approved, so the delay is holding up what we can ship. Thank you for your help.
Replies
5
Boosts
0
Views
319
Activity
2d
Local Push Connectivity entitlement request — no response after a month (again)
Hi all, I’m hoping someone from Apple can point me in the right direction. We submitted a request for the Local Push Connectivity entitlement about a month ago and haven’t heard anything back. No approval, no rejection, just silence. Unfortunately this is the second time; we tried back in 2023 and the same thing happened. After requesting the entitlement multiple times, we gave up on the project. A bit about what we’re building: we make a nurse call system for long-term care facilities. When a resident needs help, they press a wireless call device, our on-prem server raises an alert, and our iOS app would notify the caregivers on shift. The catch is that a most of these facilities put their life safety systems on air-gapped networks with no internet access at all, so APNs just isn’t an option. Even where there is internet, the system has to keep working if the connection goes down. We understand other vendors in our industry use Local Push Connectivity for this same scenario, so we’re hopeful this is just a matter of our request getting lost somewhere. As far as I can tell, this is exactly what Local Push Connectivity was made for. The WWDC20 session that introduced it (“Build local push connectivity for restricted networks”) actually names hospitals as one of the example environments where APNs may be unreachable, and talks about keeping notifications working in constrained networks “when it matters most to the users.” A resident calling for help is about as close to that as it gets. Our App ID already has the Critical Alerts entitlement, but there’s no “Network Extensions (additional values)” option under Additional Capabilities, so Xcode, understandably, complains that the profile doesn’t match the com.apple.developer.networking.networkextension value in our entitlements file. Is there a way to check on the status of a request like this, or a better place to follow up? I’m happy to share our team and app details privately. Any help would be really appreciated. We’ve been trying to get this going for a while now. Thanks!
Replies
0
Boosts
0
Views
41
Activity
2d
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
Replies
7
Boosts
0
Views
347
Activity
3d
macOS Transparent Proxy fails to start before login on Wi-Fi: "No network available"
I'm investigating an issue when deploying my VPN agent via Jamf during initial setup on clean macOS machines. The Network Extension process starts immediately after installation, but its Transparent Proxy provider starts only after a user logs in. I tried to reboot, and still observed the transparent proxy start fails. 10:00:52 === system boot 10:00:57.535 NESMTransparentProxySession[Primary Tunnel:Prisma Access Agent:68CAC11B-...]: Received a start command from PASrv[303] 10:00:57.538 NESMTransparentProxySession[...]: No network available <<<<<<<<< 10:00:57.541 NESMTransparentProxySession[...]: status changed to disconnected, last stop reason No network available <<<<<<<<< 10:01:21.541 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:01:26.373 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:06:01.293 NESMTransparentProxySession[...]: Received a start command from user_context[1547] 10:06:01.615 NESMTransparentProxySession[...]: status changed to connectedOur product requires pre-login functionality. Is this behavior expected, and how can we enable the Transparent Proxy provider before user login? I suspect a race between network availability and the attempt to start the Transparent Proxy. The issue does not occur with Ethernet, possibly because connectivity becomes available earlier than with Wi-Fi. Should we call startVPNTunnel again once connectivity becomes available? If so, what is the recommended way to detect this network transition?
Replies
5
Boosts
0
Views
156
Activity
4d
Local Network Privacy Child Process Behavior
I have a Java Swing application that is bundled into an app bundle using jpackage. The app basically launches a newer version of itself, when there is a new version downloaded in the users installation directory. I have noticed a regression or change in behavior with how LocalNetwork privacy works now. Previously, we would launch our Java application using the .app bundle. This is a launcher that checks for updates and will launch another JVM instance using any new jars it downloads when updating. So, it is closing the original process and spawning a new process using the downloaded jar. The new process is where the app connects to a server on the Local Network. This new process cannot access the Local Network even when the entry in privacy and security is enabled for the parent process. I have changed the behavior of my launcher application so that it keeps the process alive after launching the client application. When doing this, Local Network access works. So, my question is: is it required for the parent process to be running in order for a child process to have Local Network access? In previous macOS versions, this was not an issue, so something has changed with Local Network security across all the latest versions 26 and 27.
Replies
8
Boosts
0
Views
256
Activity
5d
WCSession.sendMessage is crashing when a reply or error handler is attached, why?
The following code should send a message from the watch to the iPhone. Unfortunately, it is crashing. I have no clue why. if WCSession.isSupported() { let session = WCSession.default if ((session.activationState == .activated) && session.isReachable) { session.sendMessage(["SimpleMessages":["start"]], replyHandler:{reply in _ = 0 }, errorHandler:nil) } } If the reply handler is set to nil, the code does not crash. Anyway, in both cases the message is correctly sent from the watch to the phone. The code itself is run on the main thread (verified). I am running watchOS 26.6 and iOS 27. Here is the crash : Stack trace
Replies
4
Boosts
0
Views
386
Activity
5d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
Replies
1
Boosts
0
Views
106
Activity
5d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
Replies
5
Boosts
0
Views
341
Activity
5d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
Replies
1
Boosts
0
Views
92
Activity
5d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
Replies
3
Boosts
0
Views
380
Activity
6d
MobileVLCKit (3.7.3) triggering Local Network permission
The problem manifests itself from 16 to 18 iOS not inclusive Versions from 18 up to and including do not cause this problem. When initializing the player, a request for permission to use the local network appears. The application does not use a local network as a capability, even in plist there is no such key. Apple has granted permission to use multicast networking, and the corresponding capability has also been added. The player is assembled as let player = VLCMediaPlayer() player.media = mediaHaving previously collected media with the options "clock-synchro=..." "avcodec-threads=..." "rtsp-tcp" "network-caching=..." "live-caching=..." "-vv" "clock-jitter=..."and "no-audio", "--no-sout-audio" to mute the audio for the picture during the call How to prevent a library from accessing the local network?
Replies
1
Boosts
0
Views
64
Activity
1w
iPhone 16e on iOS 27.2.1 intermittently misses BLE extended advertisements until Reset Location & Privacy
I’m investigating intermittent discovery of QuadSense V40.0 sensors on an iPhone 16e running iOS 27.2.1 (24B156). Legacy advertising units remain discoverable, but the phone sometimes misses the V40 units entirely. I’ve also seen intermittent discovery in BLESerial. The V40 uses connectable BLE 5.0 extended advertising, with a 1M primary PHY, 2M secondary PHY, and an advertising interval of about 1 second. The advertisement includes the QuadSense local name and manufacturer data with ID 0xFF02 and a 25-byte payload. During the failure: A native CBCentralManager scan with no service filter and duplicate reports enabled received 4,821 discovery callbacks in 90 seconds, including a legacy QuadSense, but zero matching extended reports. A nearby Mac received 25 matching advertisements during its overlapping scan. The iPhone probe bypassed our Flutter scan and filtering code. After Reset Location & Privacy: The same iPhone reported two V40.0 units within 1.6 seconds. Both were reported as connectable. Core Bluetooth delivered 11 matching advertisements in 10 seconds, and our app accepted both units. Bluetooth authorization was .allowedAlways in both runs. I saw the related extended advertising thread, where Apple clarified that r.188123531 affects iPhone 17 and newer. I’m posting separately because this reproduction is on a 16e and 16. Has anyone seen this on the 16e, or found a way to isolate what changes after Reset Location & Privacy when Bluetooth authorization was already granted? I’m setting up controller traces to compare a working scan with the next failure before resetting again. I’d appreciate guidance on which trace events and sysdiagnose details would be most useful to Apple.
Replies
2
Boosts
0
Views
158
Activity
1w
Choosing a TLS server identity by client address with NWListener
I run an HTTPS server on NWListener (iOS and macOS) that serves several identities from one listener on port 443, picked per handshake in sec_protocol_options_set_challenge_block, as suggested in this thread. That works well for every handshake that carries a server name. The trouble is handshakes without one. Clients on the LAN connect by IP address, so they send no SNI (RFC 6066 keeps IP literals out of it), and they trust a self-signed certificate through a configuration profile. Internet clients and scanners that reach the public address through the router's port forward also often arrive without SNI. The two groups should get different certificates, and the only thing that tells them apart is the client's address. The listener knows it in newConnectionHandler, but the challenge block never sees it. What I tried: sec_protocol_metadata_t has accessors for the server name, ALPN, version, cipher suite and so on, but I can't find one for the connection's endpoints. Setting a challenge block on the accepted connection's own TLS options before start(): listener.newConnectionHandler = { connection in let remote = connection.endpoint if let tls = connection.parameters.defaultProtocolStack.applicationProtocols .compactMap({ $0 as? NWProtocolTLS.Options }).first { sec_protocol_options_set_challenge_block(tls.securityProtocolOptions, { _, complete in complete(identity(for: remote)) }, queue) } connection.start(queue: queue) }This block never runs. The listener's own block answers every handshake (tested on macOS 27.2). My questions: Is there a supported way to choose the server identity per connection based on its endpoints, short of terminating TLS myself? Is the challenge block supported under TLS 1.3 by now? I also see it run twice for every handshake; is that expected? When a server-side handshake fails, connection.metadata(definition: NWProtocolTLS.definition) returns nil. Is there any way to learn which server name a failed handshake asked for, so it can be logged? I filed FB25541009 with a small sample project that shows all three.
Replies
2
Boosts
0
Views
90
Activity
1w
URL Filter (Oblivious HTTP) configuration In Review for almost a week with no feedback
Hello, I submitted a Network Extension URL Filter (Oblivious HTTP) configuration in CloudKit Console almost a week ago. It still says In Review / Waiting for Approval and I haven't heard anything back since the submission notice. I wanted to check whether anything is missing on my end. Just in case, the configuration ID is 60802ed4-abfa-4b20-a64e-0d35230f478a. The app is an open-source ad and tracker blocker from the developers of an existing content blocker with a large user base. On iPhone and iPad its system-wide blocking runs entirely through the URL filter. Until the configuration is approved the iOS app can't block anything at all, and our testers are left with a Mac-only product in the meantime. Because lookups go through Apple's relay to our own PIR server, we never learn which sites anyone visits. All four endpoints have been live since the day I submitted and the TXT records are in place. Every database we build also includes the www.apple.com/url-filter-test validation entry. Is there anything else I need to provide, or a rough timeline I should expect? Thank you in advance!
Replies
1
Boosts
0
Views
86
Activity
1w
BLE IOS27. When the device is connected to headphones, the Bluetooth controller does not tend to perform normal scheduling on BLE
We have an internet app that uses BLE COC to synchronize the call audio of Android devices to the iPhone side microphone. All of this functions normally, but if two conditions are met: upgrading to IOS27; Connect iPhone to headphones. So the up and down latency of our BLE COC data will be significant and increase proportionally with time. Through the analysis of the air interface logs, it can be seen that the number of retries for COC data on the air interface has significantly increased, and the interval between the other two packets is very large (far greater than the 30 millisecond conn interval). I would like to ask if Apple has adjusted the scheduling strategy of the Bluetooth controller on iOS 27, and how can we adapt to this situation? The attachment is a screenshot of the air interface log. The packet circled in the picture is sent from iPhone to Android, with an interval of 300+ms. It can be inferred that the iPhone protocol stack and Bluetooth controller have already squeezed a large amount of data, and our business bitrate is not high, only about 10K per second
Replies
4
Boosts
0
Views
160
Activity
1w
[macOS 27.2]: System-Wide DNS Resolution Failures After Sleep/Wake – mDNSResponder and NETransparentProxyProvider
Summary Recent macOS release observed intermittent system-wide DNS failures after sleep/wake on multiple devices running Global Secure Access (GSA) with NETransparentProxyProvider. Previously successful DNS lookups time out after wake across applications, including browsers and GSA. Two captures contain failure-time evidence of the mDNSResponder resolver queue predominantly waiting in close()/kernel. Other captures show similar DNS failures, but a shared root cause has not been established. Call chain, from thread entry to kernel wait: start_wqthread + 8 _pthread_wqthread + 292 _dispatch_workloop_worker_thread + 720 _dispatch_root_queue_drain_deferred_wlh + 284 _dispatch_lane_invoke + 392 _dispatch_lane_serial_drain + 332 _dispatch_source_invoke + 920 _dispatch_source_cancel_callout + 208 _dispatch_continuation_pop + 596 _dispatch_client_callout + 16 close + 8 fleh_synchronous + 72 sleh_synchronous (sleh.c:1610) unix_syscall (systemcalls.c:181) fp_close_and_unlock_with_action (kern_descrip.c:1874) fg_drop (kern_descrip.c:287) soclose (uipc_socket.c:1345) soclose_locked (uipc_socket.c:1138) cfil_sock_close_wait (content_filter.c:5743) soflow_db_apply (socket_flows.c; line unavailable) cfil_filters_udp_attached_per_flow (content_filter.c:6675) _sleep (kern_synch.c:213) lck_mtx_sleep_deadline (locks.c:1583) thread_block_reason (sched_prim.c:4060) thread_invoke (sched_prim.c:3443) Steps to reproduce The issue is intermittent. These steps describe the observed sequence, not a deterministic minimal reproduction. Run the GSA client using NETransparentProxyProvider. The affected configurations also have Microsoft Defender network extensions active. Verify that a system DNS lookup succeeds for a known hostname. Allow the Mac to sleep, including maintenance DarkWake cycles. Wake the Mac and repeat system DNS lookups or use applications requiring hostname resolution. Observe repeated approximately 30-second lookup timeouts, sometimes longer. Observed results November 5, 2026 - UTC+05:30 capture User-reported impact: Recurrence of the same sleep/wake connectivity symptoms. OS: macOS 27.2 (26B123). Incident window: 20:38-20:41 IST / 15:08-15:11 UTC. The same Chrome client/name A lookup succeeds earlier in 12.984 ms but times out after wake in 29,999.705 ms. The DNS service/server route changed, so this is not a controlled identical-network comparison. The resolver records 1,007 timeout callbacks during the incident window, across browsers, Teams, GSA, Defender and other processes. The failure-time spindump at 20:40:21.009-20:40:31.013 IST shows the original mDNSResponder PID 78534 with 715/715 resolver-queue samples under dispatch-source cancellation → close() → kernel → lck_mtx_sleep_deadline. Source: spindump.txt:75998-76093. This establishes a sampled wait, not a permanent deadlock or proof of the same root cause as November 2. The file descriptor and kernel/filter wait owner remain unidentified. A later matching Chrome lookup returns an address at 20:43:18.191816 IST on the same resolver PID, without a recorded resolver restart. This establishes some recovery, not that every application or tunnel recovered. November 2, 2026 - UTC-08:00 capture User-reported impact: No network upon wake. This eventually resolves without a reboot, after approximately 5 to 15 minutes of waiting. OS: macOS 27.2 (26B123). Incident window: 09:40-09:45 PST / 17:40-17:45 UTC. The same Edge A lookup succeeds before sleep in 19.346 ms but times out after wake in 29,999.826 ms. The resolver records 1,403 timeout callbacks during the incident window. The failure-time spindump shows 770/777 resolver-queue samples under dispatch-source cancellation → close() → kernel; 769 include lck_mtx_sleep_deadline. This establishes a dominant sampled wait, not a permanent deadlock. The file descriptor and kernel/filter wait owner remain unidentified. November 3, 2026 - UTC-08:00 capture (Mihai) Evidence: mihai_gsa_error.tar.gz The following example records a failure resolving GSA’s own control-plane endpoint, whose DNS lookup is not intercepted by the GSA tunnel. Times in these excerpts are local (UTC-08:00). GSA error [2026-11-03 10:13:58.463] Network connection to the Global Secure Access Edge could not be established StreamId: ControlStream Hostname: <tenant>.auth.client.globalsecureaccess.microsoft.com:443 Error: hostname lookup error: Address lookup failed os_error: nodename nor servname provided, or not known syscall: getaddrinfo mDNSResponder records 10:13:19.663661 [R125367->DupQ50990->Q38408] Duplicate question <private> dn:04wpeA (Addr) 10:13:58.468519 [R125367] DNSServiceQueryRecord STOP -- name hash: dn:04wpeA, duration: 39s 10:13:59.078847 [R125340] QueryRecordOpCallback: Question <private> dn:04wpeA (Addr) timing out, InterfaceID 0x0 Additional observations The original resolver records 11 timeout callbacks across GSA, Defender, Spotify and the system time service. A GSA A-query returns a positive result in 1.282 ms earlier (cache-compatible, not a cold upstream baseline), then the same client/name/qtype/flags times out after 41.865784 wall-clock seconds; that interval includes sleep. The DNS service/server set changes, so this is not a controlled same-network comparison. At 09:40 PST the Wi-Fi interface becomes inactive and loses its IPv4 address, followed by no-dns-service results. The first native lookup errors precede this link loss; it does not explain the entire case. Four GSA A/AAAA timeout transactions have matching late UDP replies. For one A-query, the reply is logged 25.095999 seconds after its matching send and 7.197434 seconds after the API timeout, during shutdown. 48 acceptable UDP response records appear within 1.467 ms. The location of the delay is not identified.
Replies
5
Boosts
1
Views
465
Activity
1w
Is it safe to strip with All Symbols for a content filter?
We would like to minimise the amount of code exposed in the product we have developed and an obvious option is to configure our build setting to use the All Symbols for Strip Style. Some investigation with an AI tool reports there are possible problems doing so. ContentFilter: non-global → all — risky. The NetworkExtension and XPC subsystems load your bundle and look up classes by name through the ObjC runtime, which uses __objc_classlist and friends (not the Mach-O symbol table), so in principle all works. In practice it occasionally breaks bundle loading in edge cases. If you try this, test specifically that systemextensionsctl activates the bundle and the filter actually traps packets. Is it safe to use All Symbols with a content filter or do we need to accept Non-Global symbols? Thanks, Dave
Replies
1
Boosts
0
Views
176
Activity
1w