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"

Hey everyone, I’m looking for advice from anyone who’s been through something similar. My Apple Developer account was recently terminated due to what Apple described as “concept or feature switching.” After digging into it more, I believe this happened because I made updates to my app after it was approved without submitting a new version for review. Here’s what I changed: Added a new screen (friends list) that required navigation changes Updated parts of the UI (visual improvements) Added a feature (button that helps users structure a plan) Enabled Google sign-in I did not change payments, subscriptions, or the core purpose of the app. At the time, I didn’t fully understand that these kinds of changes (especially anything affecting navigation or features) need to go through a new App Store submission rather than being updated remotely. I now understand how Apple could see this as bypassing the review process. Since then, I’ve: Stopped all over-the-air/runtime updates Made sure the app matches the last reviewed version Put a plan in place to use proper versioning for all future changes I submitted an appeal, but it was denied and my account has now been terminated. Apple mentioned I can submit a petition for reinstatement. I’d really appreciate any guidance on: Has anyone successfully gotten their account reinstated after something like this? What helped your case? Anything I should emphasize (or avoid) in the reinstatement petition? I’m trying to fully align with the guidelines moving forward and just want to handle this the right way. Thanks in advance 🙏

My app has been in "In Review" for 30 days now. I have e-mailed once with no reply and called twice with no helpful information. I have also requested a Expedited Review but that hasn't helped. If App Review could respond and help out in any way that would be greatly appreciated, thank you.

There is a long-standing, structural issue with the iPadOS Korean IME when using a hardware keyboard. The IME forcibly intercepts the " (quote) keydown event and injects Unicode smart/curved quotes (“ or ”) directly into the text field. This hardcoded behavior ignores both: User Settings: The global "Smart Punctuation" toggle in [Settings > General > Keyboard] is completely ignored. Developer APIs: Setting UITextInputTraits.smartQuotesType = .no on a UITextView or UITextField has absolutely no effect when the Korean keyboard is active. Steps to Reproduce: Set smartQuotesType = .no on a standard UITextView. Connect a hardware keyboard. Switch input language to English -> Press the quote key. (Result: ASCII straight quote " - Correct behavior) Switch input language to Korean -> Press the quote key. (Result: Unicode curved quote “ - Incorrect behavior) Impact on Developers & Users: Because the OS IME forcefully injects the curved Unicode character before the app can process the raw key event, developers building code editors, markdown editors, or specific word processors (like Google Docs) cannot prevent this behavior. We cannot provide a standard text-editing experience for Korean users without forcing them to manually toggle their keyboard language to English just to type a straight quote. Expected Behavior: The Korean hardware keyboard IME must respect UITextInputTraits.smartQuotesType and the global OS toggle. Please provide a mechanism for developers and users to bypass this forced CJK typography rule.

Hi App Review Team, I would like to raise a concern regarding the review process for our app update (Version 2.0.0), which has now been pending for over two weeks. We completely understand the importance of the review process, but the extended delay is starting to impact our business. This update is not a major change—the app already exists on the App Store, and Version 2.0.0 mainly includes UI improvements. The core functionality remains the same as the currently approved version. Additionally, the app has been rejected multiple times with the status “Information Needed.” We have been promptly providing all the requested information each time, but the repeated cycle is significantly extending the overall review timeline. We kindly request guidance on how to move forward more efficiently, or if there is anything specific we can provide upfront to avoid further delays. If possible, we would also appreciate support in expediting the review. Any help or clarification would be greatly appreciated, as this delay is leading to business loss. Thank you.

I'm a developer from Nigeria trying to complete payment for the Apple Developer Program (organization enrollment). This has been ongoing for over 2 weeks with no resolution. My enrollment is fully approved. D-U-N-S verified. The only issue is the payment. Here's what I've experienced: Multiple payment attempts with two different USD cards (Grey, Chipper Cash) Payments either fail silently (no error shown, order acknowledgement email received, but no charge on card and account not activated) or return "Duplicate Order" error A $0.00 card verification charge went through on one attempt, but the actual $99 was never charged The enrollment page keeps showing "Complete your purchase" every time I log in I submitted a support email request over 3 weeks ago — zero response I have a completed app ready for App Store submission being delayed by this Organization enrollment, D-U-N-S verified, all enrollment steps completed. Only the payment step remains. I've seen many developers in these forums reporting the same issue since February 2026. Is there a known issue with the enrollment payment system? Can an Apple team member please look into my case or clear the duplicate order so I can retry with a fresh transaction? Any help from the community or Apple staff would be greatly appreciated. This is blocking my entire product launch.

描述：低等级会员在 7 天免费期内订阅了高级会员 预期：低级会员的 7 天免费试用结束，高级会员直接扣费生效，苹果的升级通知如下： { "extra_info": { "quantity": 1, "expiresDate": 1754627893000, "purchaseDate": 1754623693000, "transactionId": "2000000979349440", "offerDiscountType": null, "originalTransactionId": "2000000979347229", // 升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "decodedPayload": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "2000000979347229" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 228000, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1754623696459, "storefront": "CHN", "environment": "Sandbox", "expiresDate": 1754627293000, "purchaseDate": 1754623693000, "storefrontId": "143465", "transactionId": "2000000979349440", "appTransactionId": "704742096472000913", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "2000000107917134", "originalPurchaseDate": 1754623472000, "originalTransactionId": "2000000979347229", "subscriptionGroupIdentifier": "21729756" } } 异常 case：苹果通知升级到高级会员且继续剩余试用时间，例如：低等级会员7 天免费试用期剩余 4 天，升级到 4 天的高等级会员的免费试用，收到的通知消息如下： "extra_info": { "quantity": 1, "expiresDate": 1773109207000, "purchaseDate": 1772708455000, "transactionId": "550002836609836", "offerDiscountType": "FREE_TRIAL", "originalTransactionId": "550002832625469", //升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "purchase_type": "upgrade", "decodedPayload": { "signedTransactionInfo": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "550002832625469" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 0, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "offerType": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1772708460325, "storefront": "CHN", "environment": "Production", "expiresDate": 1773108607000, "offerPeriod": "P7D", "purchaseDate": 1772708455000, "storefrontId": "143465", "transactionId": "550002836609836", "appTransactionId": "705330723507531368", "offerDiscountType": "FREE_TRIAL", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "550001244481732", "originalPurchaseDate": 1772507407000, "originalTransactionId": "550002832625469", "subscriptionGroupIdentifier": "21729756" } } 请问是苹果的会员试用的策略发生了变化吗

This is a generic, non-developer related macOS issue, but reporting here as well so it has more visibility since. It is an embarrassing bug that has not been fixed since the earliest versions of macOS Tahoe. Issue description: When Dock Magnification is enabled, the Dock Folder abruptly jumps approx. 10-15pixels down as the user moves the cursor after a brief pause). Video about the issue (see the last second of the small video and observe the entire grid popup jump abruptly): https://forums.macrumors.com/threads/macos-tahoe-26-4-release-candidate-now-available.2479503/post-34494643 Related FB: FB20761846 (opened in October, 2025) The issue is easily reproducible and confirmed by many. The lack of this issue being fixed for so long is indicative in the eyes of many of the lack of attention to details in macOS Tahoe's Glass interface.

I have been experiencing many issues trying to integrate the Apple AlarmKit in my app. I essentially keeping getting authorization errors. I was wondering if anyone else was experiencing issues like this and if anyone had guidance or a fix for what I am experiencing. I was under the impression that any devices IOS26+ could use the AlarmKit but maybe I am mistaken. Getting (com.apple.AlarmKit.Alarm error 1.) every time I try and enable alarms.

Our app's status has been completely frozen for both App Store Distribution and TestFlight. No status changes are occurring, which is preventing us from releasing updates to conduct beta testing. Or upload the app to App Store.  App Details: App Name: Memento - where you’ve been Apple ID of the app:  6758897827 Issue since: February 8, 2026 Current stuck status:  "Waiting for Review" for both distribution and TestFlight  Steps already taken: submitted more then 3 tickets to Apple support (No response) App review expedite ticket . we addressed some issues that could have been causing the delay in distribution (bugs and fixes) and uploaded the app for review again. We made sure any app information were clear in the review draft ( our data usage, features of the app, our privacy policy, support URL ) Given the duration and business impact of this issue, I am requesting that this be escalated to the appropriate review team for investigation. any help would be greatly appreciated

Hello, I’m experiencing a situation with my app Waspp that I’m trying to understand. The app was approved by App Review on Feb 24, 2026 and is currently available on the App Store in the United States. However, distribution in the European Union (Belgium and France) is blocked due to the Digital Services Act (DSA) trader verification, which still shows “In Review” in App Store Connect. Some details: App Review completed: Feb 24 DSA compliance submitted: Feb 25 Status: Still “In Review” after more than two weeks Documents requested by Apple Support have already been uploaded via their secure link App availability shows “Cannot Sell” for Belgium and France The app is live and downloadable in the US Because of this, the launch of the app in the EU is currently blocked even though the app itself has been approved. My questions: Is it normal for the DSA trader verification to take this long? Has anyone experienced a similar delay with EU distribution? Is there anything else that can be done from the developer side to unblock the verification? Any feedback or similar experiences would be greatly appreciated. Thanks!

Hello! I'm reaching out because we're seeing an inconsistency in App Store Connect data after we implemented the iOS Smart App Download Banner on our websites: when we go to App Store Connect → App Analytics → Acquisition → Campaigns, we see: “There isn’t enough data to display campaigns.” despite the fact that we expect to see some download data there. Context: Apps: HomeRun – Get Things Done (App ID: 1506390428) and ProntoPro - Trova Professionisti (App ID: 1274970171) We deployed the iOS Smart App Banner on the corresponding web pages on March 5 (https://homerun.pl/ and https://prontopro.ch/) We have also created corresponding campaigns in App Store Connect and are passing tokens via the banner meta tag: We tested this in real life by downloading both apps at least 5 times using distinct Apple accounts which never downloaded the apps before. Verification You can visit our websites (https://homerun.pl/ and https://prontopro.ch/) and verify the Smart App Banner configuration by viewing the page HTML source and locating the apple-itunes-app meta tag and its affiliate-data value. If helpful, we can provide any other additional resource of info you might need. Thanks a lot in advance for your help!

I am working on an e-commerce app (retail/marketplace) that allows users to place orders for both free and paid products. After receiving a DeclaredAgeRange API response — retrieved via the Family Controls / Screen Time framework — indicating that a user is a minor, I want to understand the recommended approach for handling payment flows. Specifically, is it necessary to block payments for users identified as minors via DeclaredAgeRange, even though our app uses server-side encrypted card processing rather than Apple In-App Purchases (StoreKit)? Any guidance on best practices or App Store policy requirements for this scenario would be greatly appreciated.

When trying to load an ambisonics file using this project: https://github.com/robertncoomber/NativeiOSAmbisonicPlayback/ I get "Unexpected Ambisonics format". Interestingly, loading a 3rd order ambisonics file works fine: let ambisonicLayoutTag = kAudioChannelLayoutTag_HOA_ACN_SN3D | 16 let AmbisonicLayout = AVAudioChannelLayout(layoutTag: ambisonicLayoutTag) let StereoLayout = AVAudioChannelLayout(layoutTag: kAudioChannelLayoutTag_Stereo) So it's purely related to the kAudioChannelLayoutTag_Ambisonic_B_Format

Hello, I am reaching out here because I have two iOS apps that have been stuck in "Waiting for Review" status with no communication from the App Review team. App 1: OKIRIZO (Apple ID: 6757417197) First submitted: January 10, 2026 Current submission: February 25, 2026 Status: Waiting for Review (19+ days on current submission, over 2 months since first submission) Multiple resubmissions due to the prolonged wait App 2: TidaKitchen (Apple ID: 6759185372) Current submission: approximately March 11, 2026 Status: Waiting for Review Both are version 1.0 initial submissions for the iOS App Store. There are no messages, no rejection notices, and no feedback in App Store Connect. I have also submitted expedited review requests but have received no response. I understand that review times can vary, but waiting over two months with zero communication is significantly impacting our business. These apps serve local businesses in Okinawa, Japan, and the delays are causing real operational problems for our clients. I have seen many similar reports from other developers in February-March 2026 on these forums. If anyone from the App Review team could investigate, or if fellow developers have found a resolution, I would greatly appreciate any guidance. Thank you for your time.

Hi Community, The Leverage macOS has with Bootstrap token is immense using the same for Software Updates, Erase Device and new Local Account Creation in System Settings While I refer From IT Deployment Guide Which States the below For a Mac with macOS 10.15.4 or later, when a secure token-enabled user logs in for the first time, macOS generates a bootstrap token and escrows it to a device management service. I even tested out the Statement using Automated Device Enrollment Workflow ( With AutoAdmin Account Only, With Both AutoAdmin Account , Primary Account ) and it Granted BootStrap Token Immediately upon login How ever with User-Initiated Enrollments it differs like below Sometimes upon installation of MDM Profile in macOS Immediately the BootstrapToken is sent to MDM Sometimes the BootStrapToken is not immediately sent, so I need to logout , login with the Secure Token enabled user for macOS to escrow BootStrapToken to MDM Sometimes Even when I followed the pointer as in 2) like logout / login from a SecureToken Enabled user the BootStrapToken is not escrowed to MDM , Which Affects the OSUpdates, Erasing Capabilities to be used precisely with MDM Protocol Can someone Please Help with the Flow for BootStrapToken Generation / issuance to MDM incase for User-Initiated Enrollment

We are implementing in-app provisioning in our fintech app; We are reaching out to ask for your help in understanding what is going wrong so we can fix it. What happens: User taps “Add to Apple Wallet” → we present PKAddPaymentPassViewController → they tap Next → after a few seconds the flow fails with "Set Up Later" alert. Device log: "eligibility request failure", "Received HTTP 500" )'; underlyingError: 'Error Domain=PKPaymentWebServiceErrorDomain Code=0 "Unexpected error." UserInfo={PKErrorHTTPResponseStatusCodeKey=500, NSLocalizedDescription=Unexpected error.}'; userInfo: '{ PKErrorHTTPResponseStatusCodeKey = 500; }'; > Feedback Assistant ID: FB22176928 (In-App Provisioning issue 500 Internal Server Error)

I think I’ve discovered a quantum paradox in the enrollment process. On February 3rd, I paid for my membership. Since then, my account has been in a "Schrödinger's State": It exists (because the payment was successful and my ID was verified weeks ago) It doesn't exist (because it’s still stuck on "Pending" and I can't access any developer tools) It’s been 31 days, and the box is still closed. But I really hope not many people are in this situation, has anyone else faced something similar? How did you resolve it? I’d love to finally start publishing…

Hello, I recently paid for the Apple Developer Program membership, but I am still being prompted to complete payment as if my subscription has not been processed. I have already been charged, and the payment appears to have gone through on my end. However, my account still shows an unpaid or inactive status, and I continue to receive payment prompts. Could you please investigate this issue and confirm that my membership is active? If there is a duplicate charge or a processing error, I would appreciate your assistance in resolving it. Thank you for your help.

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.