Overview

My app presents a popover mail controller, which works fine on iPhone and on iPadOS <26.4. However in iPadOS =>26.4, there is no exit or cancel button in the top left corner as usual. The popover can only be closed by tapping the top centre of the view where the 'swipe down bar' is; it cannot be closed by actually swiping down. This is obviously not intuitive for a user. Since the mail controller is not customizable, I'm asking whether this is a bug, a new (unintuitive) design, or if implementations of a mail controller need updating on the new OS.

I need a bit more support. Per Apple’s guidance, our dext’s hosting app checks to see if the dext is installed, and if it is not installed, it will register the dext. I am going to refer to this as “auto registration.” I have also added a menu option to register the dext, which I am going to call “manual registration.” The manual registration works. The user is prompted to “Allow” the dext to be loaded, and things proceed normally. The auto-registration does not work. It produces an error response that is not helpful: Request did fail with Error 1 (The operation couldn’t be completed. (OSSystemExtensionErrorDomain error 1.)) Registration failed, unknown error. They execute the exact same code path – the auto registration calls the menu option’s function that executes from user selection. When comparing the sysextd logs, they differ starting at “Advancing from validating to validating_by_category.” The manual registration has a trace that reads: got reply from com.apple.system_extension.driver_extension... The auto registration does not get this reply. Attached are the two logs. This is Sonoma 14.7.6, the earliest OS we must support. Any suggestions on what is happening or how to fix it so that auto registration can work? Validate_by_category failure trace Validate_by_category success trace

Hi App Review Team, Our app was rejected under Guideline 1.1. After implementing all requested changes, the app was approved. The next version was approved without any rejection. The following version — with no new functionality added — was rejected again under the same Guideline 1.1. Our follow-up correspondence with the App Review Team did not produce results, and our requests for specific clarification went unanswered. We submitted an appeal to the App Review Board on May 15, 2026. As of today, no response or decision has been received. Contacted Developer Support as well on May 28 via Contact Us → App Review → App Review Status (case ID 102901983790), also no response yet. Could the App Review Team please look into the status of our appeal and confirm it is in the queue? Any guidance on next steps would be greatly appreciated.

Hi everyone, I’m stuck in Apple Support hell and hoping someone here has a workaround. I have a paid Developer account, but I cannot deploy to a physical device due to what looks like a persistent backend database glitch on Apple's side. The Issue: When I check "Automatically manage signing" in Xcode, Apple's servers generate a Provisioning Profile that is hardcoded with an old, orphaned Free Personal Team ID (T7...). This completely overrides my actual Paid Team ID (DP...), causing a permanent Bundle ID mismatch error. What I’ve already done (Zero local issues): Completely wiped my Mac’s Keychain (deleted all dev keys, certificates, and local provisioning profiles). Revoked all certificates in the Apple Developer Portal. Tried generating fresh certificates manually via CSR. Sent Apple Support a full-screen video proving the backend is injecting the wrong ID on a 100% sterile system. The Situation: I am 3 months into my paid subscription and haven't been able to use it. Apple Tier 2/3 engineering has the video evidence but has stopped responding to my status update requests. Has anyone successfully forced Apple's backend to "forget" an old personal team ID, or found any undocumented workaround that doesn't involve creating a brand new Apple ID and paying the $99 fee again? Thanks in advance.

Hello, I am requesting urgent assistance with my app review. I have been through multiple rejection cycles, addressed every issue raised, and resubmitted, but I have not received any response on my most recent submission despite having an active expedited review request. Here are my details: App Name: BitzaHugs Original Submission Date: 05/24/2026 Expedited Review Requested: 05/30/2026 Current Status: Waiting for Review Support Case #: 102903001544 I have fully resolved all previously cited rejection reasons and resubmitted accordingly. My intended launch date has now passed by two days and every additional day of delay has direct business impact. I am not seeing any flags or errors in App Store Connect on my end. I would greatly appreciate any escalation or update on the status of this review. Thank you for your time, Amanda Benavidez

Hello App Review Team, My app was first submitted (version 1.0.0) on May 6. Since then, I have submitted multiple bug-fix updates, but none of them have ever entered the actual review process – they have remained stuck in "Waiting for Review". My latest version is ready and currently waiting for your team to begin the review so it can be released on the App Store. App information: App ID: 6764726742 First submission date: May 6 Latest version waiting: 1.1.1 I would like to ask: Is there any account, agreement, or metadata issue preventing my app from entering the review queue? When can I expect the review to actually start? Our users and business have been waiting for the iOS version for a long time. Any clear guidance from your team would be greatly appreciated. Thank you for your time and help.

I'm trying to diagnose some issues with my AutoFill credential provider not loading on macOS. As far as I can tell I have all the entitlements and provisioning profiles correct, and ASSettingsHelper.requestToTurnOnCredentialProviderExtension() returns true with the Credential Provider showing up enabled in System Settings. However all other attempts to call into AuthenticationServices fail, and ASCredentialIdentityStore.shared.getState() always returns false for state.isEnabled Looking at the logs I don't see anything that stands out but I am not sure I've got the correct filter on the logs. I see discovery taking place 2026-05-29 08:43:09.389967-0700 0xd7d00 Default 0x83c0b1 26490 0 CredentialProviderExtensionHelper: (PlugInKit) [com.apple.PlugInKit:discovery] [d 88616305-672E-4143-81A6-832522BCD790] <PKHost:0x7e6c24900> Beginning discovery for flags: 0, point: com.apple.authentication-services-credential-provider-ui 2026-05-29 08:43:09.390070-0700 0xd7d00 Info 0x83c0b1 26490 0 CredentialProviderExtensionHelper: (PlugInKit) [com.apple.PlugInKit:discovery] [d 88616305-672E-4143-81A6-832522BCD790] <PKHost:0x7e6c24900> Query: { "LS:ExtensionPlatforms" = ( 1, 6, 2 ); NSExtensionPointName = "com.apple.authentication-services-credential-provider-ui"; NSUserElection = 1; } 2026-05-29 08:43:09.392893-0700 0xd79ee Debug 0x83c0b1 487 0 pkd: (PlugInKit) [com.apple.PlugInKit:sandbox] issued file extension for [/Applications/test.app/Contents/PlugIns/testIDCredentialProvider.appex] 2026-05-29 08:43:09.392936-0700 0xd79ee Debug 0x83c0b1 487 0 pkd: (PlugInKit) [com.apple.PlugInKit:ls] [u C85BFC1E-25E1-4917-A1D8-0123013482EE] [com.myapp.test.App.testid-credential-provider(7.35)] info [CFBundleIdentifier] => [com.myapp.test.App.testid-credential-provider] 2026-05-29 08:43:09.392947-0700 0xd79ee Debug 0x83c0b1 487 0 pkd: (PlugInKit) [com.apple.PlugInKit:sandbox] issued mach extension for [com.myapp.test.App.testid-credential-provider] And I see it being discovered correctly: 2026-05-29 08:43:09.394535-0700 0xd7d00 Default 0x83c0b2 26490 0 CredentialProviderExtensionHelper: (ExtensionFoundation) [com.apple.extensionkit:NSExtension] discovered extensions: attributes { "LS:ExtensionPlatforms" = ( 1, 6, 2 ); NSExtensionPointName = "com.apple.authentication-services-credential-provider-ui"; NSUserElection = 1; }, extensionSet {( <EXConcreteExtension: 0x7e71b41c0> {id = com.myapp.test.App.testid-credential-provider} )} I don't see any errors related to security or provisioning that I can tell. Any tricks I can use to see why I can't use my Credential Provider?

Hello, I am requesting urgent assistance with my app review. I have been through multiple rejection cycles, addressed every issue raised, and resubmitted, but I have not received any response on my most recent submission despite having an active expedited review request. Here are my details: App Name: BitzaHugs Platform: iOS Original Submission Date: 05/24/2026 Expedited Review Requested: 05/30/2026 Current Status: Waiting for Review Support Case #: 102903001544 I have fully resolved all previously cited rejection reasons and resubmitted accordingly. My intended launch date has now passed by two days and every additional day of delay has direct business impact. I am not seeing any flags or errors in App Store Connect on my end. I would greatly appreciate any escalation or update on the status of this review. Thank you for your time, Amanda Benavidez

Hello everyone, I am testing how Siri interacts with web pages on iOS devices. When a user utilizes Siri voice commands to search for or open a specific website, Siri usually processes the request and opens the result inside the Safari browser. As a web developer, I want to know if there are any specific HTML meta tags, Schema markup, or SEO best practices that we should implement. This is to ensure Siri can accurately recognize the website's name, brand, and content. What are the simplest ways to make a static web page friendly for Siri voice search? Thanks in advance!

My app OneNest (App Store ID: 6762323106) has had in-app purchase localizations in "Waiting for Review" status for nearly 2 weeks. My subscriptions were approved but the localization for both the subscription and lifetime purchase IAPs remains pending. This is actively blocking customers from completing purchases in my live app. I have an open support ticket but have not received a response in 2 weeks. Has anyone experienced this? Is there a way to escalate IAP localization review specifically? Any guidance would be appreciated.

I am experiencing a significantly long review period for my macOS app. I submitted my app for review on May 25th at 8:58 PM, and it has been stuck in the 'In Review' status since then. It has now been over a week without any updates or feedback. I have noticed a recurring pattern of macOS app reviews taking much longer than usual lately. Is there a known backlog or a change in the review process for the macOS platform? It would be helpful to know if others are facing similar delays to understand if this is a broader trend at the moment. Thanks in advance.

Hello, I've been experiencing an unusually long wait for my app review. My current situation: Status: Stuck in "Waiting for Review" — significantly past the 24–48 hour window with no progress. Developer Support (Email): I've submitted a Developer Support case (Case ID: 102905099480), no response received as of yet. Developer Support (Phone):When attempting to contact Apple Support, the option to request a phone call does not appear to be available for this type of issue. Has anyone else encountered this issue? And what should I do? Thank you.

I am interested to be informed what is relation between storage capacity and Xcode usage; because my storage level goes up when I develop apps on Xcode.

We're seeing limitations in host -> macOS VM changes syncing. Were using Anka, but we've also tried others. We're actually doing the exact implementation that others (the ones we found that are open source) do. Here is a breakdown of what's supported: Operation Direction Supported Notes Create new file/folder Host → Guest ✅ Yes New paths appear in the guest Create new file/folder Guest → Host ✅ Yes New paths appear on the host Read existing contents Host → Guest ✅ Yes Contents present at mount time are visible Modify file in place Guest → Host ✅ Yes Guest edits are written through to the host Modify file in place Host → Guest ❌ No Guest keeps stale contents for already-accessed files (macOS virtiofs caching) Delete file/folder Guest → Host ✅ Yes Removal is reflected on the host Delete file/folder Host → Guest ❌ No Guest still sees the path after the host deletes it (cached) Replace via temp + rename() (atomic) Host → Guest ✅ Yes New inode/dentry; recommended way to update files from the host We're requesting a way to disable caching and/or allow the unsupported actions in the table to be supported. https://feedbackassistant.apple.com/feedback/22905515

Hello, I recently enrolled in the Apple Developer Program. The payment was successfully processed, and I received the receipt/invoice from Apple. Around the same time, I also received an email asking me to upload identity verification documents. However, when I followed the upload link and signed in with my Apple ID, I was shown the following message: "You do not have permission to upload files for this account." Because of this, I was unable to upload the requested documents. Shortly afterward, I received an email stating that my enrollment had been withdrawn. I have already contacted Apple Developer Support, but so far I have only received the receipt/invoice emails and have not received any response regarding this issue. Has anyone experienced something similar before? If so, how was it resolved? Thank you.

Hello, I’m experiencing an issue with my Apple Developer Program organization enrollment and would appreciate help from Apple staff or anyone who has seen this behavior before. Summary of the issue: My organization enrollment appears to be approved, but the account is also showing a pending state, and I am unable to complete the final membership purchase step. When I sign in to the Apple Developer website and click “Purchase Membership”, I am required to re-enter all billing and organization details every time. After submitting the form, no payment is processed, and I am returned to the same “Purchase your membership” screen. The purchase never completes. This has been happening consistently for approximately two months. What I observe: Enrollment appears approved, but account is also stuck in a pending state No membership payment is ever successfully charged Each attempt to purchase resets the entire form No error message is shown Issue occurs on the Apple Developer website Problem persists across multiple attempts and sessions What it seems like: It appears my account is stuck in an inconsistent state where: The enrollment approval has been completed But the membership purchase is still treated as pending or not initiated And the purchase flow is not properly linking to the approved enrollment This results in an endless loop where I cannot activate the membership. Request: Could someone from Apple or the community please advise: Whether this is a known issue with enrollment/purchase state sync If there is a way to reset or clear a stuck pending membership state How this can be escalated to Apple Developer Program Operations / Enrollment team Whether manual intervention is required to complete activation This issue is currently blocking our application release timeline, so any guidance or escalation would be greatly appreciated. Case number (if relevant): 20000115519348 - 102885716444

Hi, I encounter a dead-lock with Apple AUGraphicEQ. I have attached backtrace: thread #44, name = 'com.apple.audio.toolbox.AUScheduledParameterRefresher' frame #0: 0x0000000182059bb0 libsystem_kernel.dylib`semaphore_wait_trap + 8 frame #1: 0x000000018e9e7e00 caulk`caulk::semaphore::timed_wait(double) + 224 frame #2: 0x000000018e9e7cac caulk`caulk::concurrent::details::worker_thread::run() + 32 frame #3: 0x000000018e9e794c caulk`void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*>>>(void*) + 96 frame #4: 0x000000018209dc58 libsystem_pthread.dylib`_pthread_start + 136 regards, Joël

Subject: Enrollment Status Inquiry - Web Order D004860417 Hello everyone, I submitted my Apple Developer Program enrollment, paid the fee, and provided the requested identity documents on May 23, 2026. As of June 1, my account status remains "Pending". Could you please review my application status and advise if any additional information or documentation is required to complete the verification? Web Order Number: D004860417 Invoice Number: MC73562815 Thank you, Aleksandr Sapozhnikov

Hello, I’m having an issue completing my Apple Developer Program organization enrollment and would appreciate help or escalation from Apple staff or anyone who has seen this before. Summary of the issue: My organization enrollment has been approved, but I am unable to complete the membership purchase. When I sign in to the Apple Developer website and click “Purchase Membership”, I am required to re-enter all billing and organization details each time. After submitting, the process does not complete, no payment is charged, and I am returned to the same “Purchase your membership” screen. This has been happening consistently for approximately two months. What I’ve observed: Enrollment status shows as approved No payment is ever successfully processed Each purchase attempt restarts the full form Issue occurs on the Apple Developer website Multiple attempts over time with the same result What it seems like: It appears my account is stuck in an incomplete or broken membership purchase state, where the approved enrollment is not correctly linked to a purchasable membership. Request: Could someone from Apple or the community advise on: Whether this is a known issue If there is a way to reset or clear a stuck membership purchase state How to escalate this to Apple Developer Program Operations / Enrollment team This issue is currently blocking our app release timeline, so any guidance would be greatly appreciated.

wifip2pd leaks file descriptors during repeated Wi-Fi Aware NDP cycles → EMFILE → Wi-Fi Aware permanently broken Summary Under repeated Wi-Fi Aware (NAN) datapath connect/teardown cycles, wifip2pd leaks file descriptors until it hits the per-process limit (EMFILE, "Too many open files"). After that, wifip2pd can no longer create the socket needed to configure the nan0 interface, so updating the nan0 IPv6 link-local address fails with Apple80211Error Bad file descriptor. From the app's side, the NDP datapath is established but the NetworkConnection never gets a local IPv6 address and stays stuck in .preparing. The condition does not self-heal and is not cleared by restarting the app — only a reboot (or wifip2pd restart) recovers Wi-Fi Aware. Configuration iPhone 16 Pro Max, iOS 26.5 Network framework (new Swift NetworkConnection / NetworkBrowser Wi-Fi Aware API) System component: wifip2pd Where the problem is The leak and the failure are entirely inside wifip2pd (the per-process descriptor table fills up). The chain is: fd leak in wifip2pd → EMFILE ("Too many open files", errno 24) → socket() fails → cannot set nan0 IPv6 link-local address (Apple80211 ioctl on invalid fd → EBADF) → app NWConnection NWPath = satisfied but localEndpoint = nil → NetworkConnection stuck in .preparing, times out Abnormal console logs (the evidence) The smoking-gun lines from the unified log / Console (process wifip2pd): wifip2pd <Error> Failed to create socket: Too many open files wifip2pd <Error> Failed to update nan0 IPv6 address to [fe80::30c1:22ff:fe97:fefb] (from [fe80::e8a0:9bff:fe25:4d5c]) because <Apple80211Error Bad file descriptor> wifip2pd <Error> nw_path_shared_necp_fd necp_open failed [24: Too many open files] # errno 24 = EMFILE wifip2pd(Network) <Error> File descriptor is bad, could not create socket Counts over one ~11.5-minute failing capture: wifip2pd "Too many open files": 45 occurrences (a healthy capture has 0). nan0 IPv6 address update: 2 success / 13 fail (the 2 successes are before exhaustion; everything after fails with "Bad file descriptor"). Healthy device, for contrast — the IPv6 update succeeds on every NAN MAC rotation, and the app connection then works: wifip2pd Successfully updated nan0 IPv6 address to [fe80::f4c4:14ff:fe28:784a] # → app NWPath: status=satisfied, local=fe80::f4c4:14ff:fe28:784a%nan0 → NetworkConnection .ready Two facts that localize the bug: The leak is in wifip2pd, not the app. wifip2pd is one persistent daemon (constant pid) whose fd count only grows; the client app was restarted multiple times during the test and that did not release the descriptors. All "Too many open files" lines are emitted by wifip2pd. The NDP datapath itself still succeeds — only socket/interface-address configuration fails: kernel nan0: handleDataPathEstablished: NAN-DP Data path ESTABLISHED ... encrypt 1, EstDPs 1 wifip2pd #### Data Confirmed With Peer: ... port: 9004 Application-layer symptom (developer-facing) The same client code works before exhaustion and fails after: Before: NetworkConnection<UDP> reaches .ready; NWPath.localEndpoint = fe80::…%nan0. After: NetworkConnection<UDP> stays .preparing; every onPathUpdate reports status=satisfied, interfaces=["nan0"], local=nil; it times out and retries forever. The decisive developer-visible signal is NWPath.status == .satisfied together with localEndpoint == nil on nan0. Correlating timestamps confirms the contradiction: the console shows Data Confirmed With Peer ... port 9004 ~9–10 s before the app's NetworkConnection gives up, while the matching nan0 IPv6 update fails with "Bad file descriptor". The datapath is up at L2, but the connection is unusable because no local address was ever assigned. Steps to Reproduce Pair an iPhone with a Wi-Fi Aware peer that publishes a datapath service (_media-sync._udp, paired device, NCS-SK-CCM-128). Repeatedly establish and tear down the NDP datapath. In our case the peer device repeatedly powers off/on; each cycle forces a fresh browse + re-pair + NDP establish (the peer's NAN MAC is randomized each boot). Loop this; wifip2pd is never restarted, so the leak accumulates (failure appeared by ~the 9th iteration). Expected vs Actual Expected: wifip2pd releases the descriptors of each completed/torn-down browse/subscribe/datapath session; fd count stays bounded; nan0 IPv6 updates keep succeeding; NetworkConnection reaches .ready. Actual: wifip2pd fd count grows until EMFILE; nan0 IPv6 update then fails permanently; NetworkConnection is stuck .preparing for the rest of the wifip2pd process lifetime. Impact Any app using Wi-Fi Aware NDP datapaths under frequent connect/teardown eventually loses all Wi-Fi Aware connectivity. The failure is sticky for the wifip2pd lifetime and is invisible to / unrecoverable by the client app. Workaround Reboot the device (resets wifip2pd). The client can only slow the leak (fewer reconnects, prompt release of NetworkConnection), not prevent it, since the descriptors leak inside wifip2pd. To confirm / fix A sysdiagnose captured during the reproduction should show wifip2pd's open-fd count growing monotonically per connect/teardown cycle (which descriptor type leaks per browse/subscribe/datapath). Repro signature to grep in the logs: wifip2pd emitting Failed to create socket: Too many open files, necp_open failed [24: Too many open files], and Failed to update nan0 IPv6 address ... Apple80211Error Bad file descriptor.