Overview

General: Forums subtopic: App & System Services > Networking DevForums tag: Network Extension Network Extension framework documentation Routing your VPN network traffic article Filtering traffic by URL sample code Filtering Network Traffic sample code TN3120 Expected use cases for Network Extension packet tunnel providers technote TN3134 Network Extension provider deployment technote TN3165 Packet Filter is not API technote Network Extension and VPN Glossary forums post Debugging a Network Extension Provider forums post Exporting a Developer ID Network Extension forums post Network Extension Framework Entitlements forums post Network Extension vs ad hoc techniques on macOS forums post Network Extension Provider Packaging forums post NWEndpoint History and Advice forums post Extra-ordinary Networking forums post Wi-Fi management: Understanding NEHotspotConfigurationErrorInternal forums post See also Networking Resources for general networking resources, including information about Wi-Fi. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi. In my app a need do change launch screen. During development sometime in when I install new version of app over old version sometimes I see old launch screen. Is it possible that this situation will happen on production when I will publish app to App Store? Is Launch screen somehow cached?

Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as "You receive this error when the system prompts a person and they decide not to share their age range with your app. ", as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorithm to test given feature for macOS (mock region, mock age, mock source of approval, revoke declared range, etc). Now I get a review with rejection, stating that I don't have age verification mechanisms present in my app. Also I found out that after filling the App Information regarding Age Ratings it spreads to all fresh releases, so even though my newest macOS release doesn't contain age verification mechanisms yet, it should, as iOS release has got this functionality up and running already and I had to check this when filling Age Ratings questionnaire. Now I'm stuck between removing this capability from App Information, so the macOS release can pass and stalling macOS releases until there is a proper usable API to implement Declared Age Range verification properly (at least the same way as on iOS). How should I properly develop and test this feature for macOS before releasing it publicly?

Hi team, I am having an issue with paying for my apple developer enrolment program. Error message is: Your payment authorisation failed on card XXXX. Please verify your information and try again, or try another payment method. Things I have tried and has not worked: Multiple company visa card Multiple personal visa card Ensuring billing address matches my visa cards Turn off VPN Try my personal IOS device My company and personal cards should work because I have paid for other products and apple products with it. I do not think this is an isolated incident and that Apple should look into this immediately to prevent blocking developer enrolment. Other similar threads: https://developer.apple.com/forums/thread/817892?page=1#878707022 https://www.reddit.com/r/applehelp/comments/1m5fj6q/how_to_fix_your_payment_authorization_failed_on/ https://developer.apple.com/forums/thread/814065

Hello everyone, I’m running into an issue with my Apple Developer Program enrollment and hoping someone here or an Apple staff member can point me in the right direction. I tried to pay the annual fee, but my account status wasn't updating. Thinking the transaction had failed, I tried to make the payment a second time a few days later. Because of this, my credit card was actually charged twice. The charges appear on my bank statement as: February 19 (R$ 543.16 BRL) February 23 (R$ 536.70 BRL) Despite both payments clearing on my end, it is now March 16 and my account still shows as pending. My enrollment has not been approved yet. Has anyone else experienced this kind of delay? What is the best way to get Apple to activate the account using one of these payments and issue a refund for the duplicate charge? I have all the bank statements ready to show support, but the process has been completely stuck. Thank you in advance for any advice.

Hello, I enrolled in the Apple Developer Program as an individual through the developer.apple.com website. The payment was successfully charged from my credit card and I also received the official Apple invoice. However, my membership status is still showing as "Pending" in my developer account and I cannot access App Store Connect. It has now been more than 7 days since the purchase. Order Number: W1568033429 I also contacted Apple Developer Support but have not received any response yet. Has anyone experienced a similar issue or delay? Is there anything else I should do to resolve this? Thank you.

Hi Developer support team, I tried to subscribe the developer program through both the app and the website. Howe ver, the app shows me a grey button for enroll now and the website said Your enrollment in the Apple Developer Program could not be completed at this time. What should I do next?

I want to publish an app, but my developer account is under Bashir Sons Group. When I visit developer.apple.com/account and go to Enroll, it shows my personal name instead of the company name, and I get this error: 'Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.'

As a company, we would like to implement digital passes in the Apple Wallet. We're wondering which option we should follow to be able to do so. Our company creates and manages access control devices to put on waste drop-off points. Our goal is to give the opportunity to our final users to unlock these drop-off points with their iphone. A contact told us to use the NFC & SE but this solution seems not to be available in France and not directly integrated with the Apple Wallet. We've seen Apple Wallet Access and Apple Wallet VAS as alternatives but we're not sure any of these two are really matching our usecase. We definitely want our passes to be directly integrated within the wallet, without an app.

Hi, I've been trying to get a call back from apple on a couple of issues but I'm unable to do so. The "Call" button in the contact us form keeps appearing and disappearing at random times. Since I'm in India, I believe the Singaporean team handles the developer support queries. The operating hours mentioned on apple's website are 09:00–17:00 SGT but the "call" button's appearance and disappearance is NOT at all according to this. Now when I was finally able to login into apple developer support at the right time (when call button was visible), and entered my details to get a call back from them. It says "We're calling you shortly" but I receive no call at all. It's been two hours since that. Previously, when i requested a call back for other issues, I got the call immediately. Now it's been so long and there's still no call. And the thing is, I'm also unable to request a call back again for the same issue until some time passes. I think there's some sort of cooldown. The phone/call button disappears again and I'm only left with the email option. Which I NEVER got a reply from unless it's after a call back. There's also no way to call developer support directly. I tried calling back on the number i previously received the call from, but it gets connected to normal support and they say they cannot transfer or connect the call with the developer support team. I don't know what to do. I urge apple to kindly look into this issue and kindly fix it as soon as possible.

I am developing a macOS application using SwiftUI (with an iOS version as well). One feature we are exploring is displaying an avatar that reads or speaks dynamically generated text produced by an AI service. The basic flow would be: Text generated by an AI service Text converted to speech using a TTS engine An avatar (2D or 3D) rendered in the app that animates lip movement synchronized with the speech Ideally the avatar would render locally on the device. Questions: What Apple frameworks would be most appropriate for implementing a speaking avatar? SceneKit RealityKit SpriteKit (for 2D avatars) Is there any recommended way to drive lip-sync animation from speech audio using Apple frameworks? Does AVSpeechSynthesizer expose phoneme or viseme timing information that could be used for avatar animation? If such timing information is not available, what is the recommended approach for synchronizing character mouth animation with speech audio on macOS/iOS? Are there examples of real-time character animation synchronized with speech on macOS/iOS? Any architectural guidance or references would be greatly appreciated.

log Results(using my own SIR(0.0)Lengua Canonical host programming language using Swifty Complier) 14 Billion Operations on an iPhone 12: The SIR(0.0)Lengua Benchmark The Accomplishment I have successfully benchmarked a "bare-metal" implementation of the SIR+Nexus protocol on an iPhone 12 (A14 Bionic). I am currently seeking funding/grants to move from this high-performance core into a full production-ready registry ecosystem. If you are interested in supporting a project that brings supercomputer-grade verification to the edge, I’d love to connect ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:46:13 +0000 🔁 NONCE: CBECB308-2E3C-48FA-989D-AD129E27A74C ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772815573.139092 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013537406921386719 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 2 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.30783951282501 seconds Total Executed Canons: 14000000000 Throughput: 338918717 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:40:18 +0000 🔁 NONCE: 6968F42F-5646-4DE9-BCD4-02F6D53426E2 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772815218.9165797 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014863014221191406 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 1 Actions per Engine: 7000000000 Cores: 2 Execution Time: 40.646605491638184 seconds Total Executed Canons: 7000000000 Throughput: 172216103 canons/sec Checksum: 18213274789747570432 ===================================l ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:26:21 +0000 🔁 NONCE: 83BFC05F-9582-4EDF-8154-7FC88A925CE7 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814381.243969 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013855695724487305 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 591428 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.8350967168808 seconds Total Executed Canons: 14000000000 Throughput: 334647248 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:33:17 +0000 🔁 NONCE: 808B2B4D-A69A-4062-B2BC-D546B0DCBCAA ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814797.3462362 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014896392822265625 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.28380227088928 seconds Total Executed Canons: 14000000000 Throughput: 339116051 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:18:13 +0000 🔁 NONCE: B8B6575E-DBB3-44C4-95D2-D7D22DC87075 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772813893.3843408 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014749765396118164 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 64 Actions per Engine: 512 Cores: 2 Execution Time: 15.000059366226196 seconds Total Executed Canons: 4791923200 Throughput: 319460282 canons/sec Checksum: 160388065465600 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:21:29 +0000 🔁 NONCE: 4C5E58E7-CC42-487C-A972-00666A6DA78A ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814089.8965917 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014749765396118164 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 70000 Cores: 2 Execution Time: 15.00032925605774 seconds Total Executed Canons: 5049660000 Throughput: 336636610 canons/sec Checksum: 23152360350731280 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:22:42 +0000 🔁 NONCE: 8B8125E3-71EB-43FB-8DB5-9749192C2C9D ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814162.3418667 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013689994812011719 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 700000 Cores: 2 Execution Time: 15.00326406955719 seconds Total Executed Canons: 5138700000 Throughput: 342505469 canons/sec Checksum: 235609058415150000

I am currently running iOS 26.4 Beta and have encountered a critical issue with the in-app purchase system. Due to a system malfunction in this beta version, I was charged multiple times for the same purchase. I have already submitted a formal refund request through the official channels; however, the request was rejected/not processed. Has anyone else experienced similar billing issues on this specific beta build? Any advice on how to escalate this, given that the standard refund process has failed?

I’m implementing a custom playback pipeline using AVSampleBufferAudioRenderer together with AVSampleBufferRenderSynchronizer. hasSufficientMediaDataForReliablePlaybackStart appears to be the intended signal for determining when enough media has been queued to start playback. For local playback, this works well in practice — the property becomes true after a reasonable amount of media is enqueued. However, when the output route is AirPlay, using this property becomes difficult: AirPlay requires significantly more buffered media before the renderer reports sufficient data. The required preroll amount is much larger than for local playback. For short assets, it is possible to enqueue the entire audio track and still never observe hasSufficientMediaDataForReliablePlaybackStart == true. In that situation there is no more media data to enqueue, but the renderer still reports that playback is not ready. Given this behavior, what is the recommended way to determine playback readiness when using AVSampleBufferAudioRenderer with AirPlay?

Hi everyone, I am trying to understand the reporting capabilities available in the iOS ecosystem for auto-renewable subscriptions via App Store Connect / Apple subscription reports. Does Apple provide country-wise active subscriber counts for auto-renewable subscriptions? The requirement is to understand how many currently active subscribers exist in each country. Is there any reporting available at the subscription productID level by country? For example, if we have multiple subscription SKUs (monthly / yearly), can we see the country-wise distribution per productID. In the available reports, are new subscriptions and renewals split separately? We want to differentiate first-time subscription conversions vs recurring renewals. Is there a metric that represents currently active subscriptions at a specific point in time? Most reports seem to show transactions or events, but we are trying to find a metric representing active subscriber base (snapshot) rather than cumulative transactions. Thanks

I am working on offline license support for FairPlay. I am trying to identify offline vs. live streaming requests. How do I do that? Is there any way to identify the request type (offline or streaming) from SPC?

We are evaluating the new behavior mentioned in the Nearby Interaction documentation for iOS 18.4+, which states: “In iOS 18.4 and later, your app can continue ranging in the background with any supported device if the app starts a Live Activity as it goes to the background." Could you clarify what situations are considered “can continue ranging” versus cases where it will not continue? Specifically, if my app: starts a NISession in the foreground starts a Live Activity with that data then the app goes to background should the NI session still deliver ranging updates so the app can update the Live Activity? also, my app already enable Background Modes capability

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 5, 2026, every single build we have uploaded (8 builds total) has been stuck in the "Processing" state for over 4 days. For our project, due to the large binary size, processing usually takes about 4 to 6 hours normally. However, we now have a long queue of builds that haven't transitioned to "Ready to Submit" for up to 80+ hours. Stuck Builds List: 1.0.0 (444): Mar 8, 3:09 PM (Processing) 1.0.0 (443): Mar 8, 5:36 AM (Processing) 1.0.0 (440): Mar 7, 6:37 AM (Processing) 1.0.0 (438): Mar 6, 5:01 PM (Processing) 1.0.0 (434): Mar 6, 12:04 AM (Processing) 1.0.0 (433): Mar 5, 6:26 PM (Processing) 1.0.0 (432): Mar 5, 10:51 AM (Processing) 1.0.0 (431): Mar 5, 6:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4, which processed within the expected 6-hour window.) There have been no changes to our project settings, Info.plist, or entitlements since the last successful build. This is completely halting our scheduled update release. Is anyone else experiencing a similar backlog with large macOS binaries? Or is there a known issue with the App Store Connect pipeline for the macOS platform recently? Any help or investigation from Apple engineers would be greatly appreciated. (Feedback ID: FB22156358)

I need to validate whether specific menu items are correctly enabled/disabled. The XCUIAutomation elements for my menu items do not appear in the tree shown by displaying the XCUIApplication object in the debugger when building and testing the iPadOS version of my application. When running the application in an iPad simulator, I can make the menu bar appear by swiping down. The testing works as expected for the MacOS build and test. I did try to use the recording feature, but was not successful in creating a series of commands that worked for a test run.

Hello DTS team, the request review from StoreKit is not working in iOS 26.4 beta 3. I have filed a feedback (FB22157147). Sample code: import SwiftUI import StoreKit struct ContentView: View { @Environment(\.requestReview) private var requestReview @State private var count = 0 var body: some View { VStack { Button("Increase Count") { count += 1 } Text(count, format: .number) .font(.largeTitle) } .onChange(of: count) { if count == 3 { Task { try await Task.sleep(for: .seconds(2)) requestReview() print("Request Review triggered!") // On iPadOS 26.4 beta 2 & 3, requestReview() does not trigger any review system sheet when testing in Xcode 26.3 // Works on iOS 26.3.1 } } } } }