Overview

Greetings! We are experiencing an issue with Apple iPad 9th generation devices. A stationary iPad may lose connection with a 5 GHz Wi-Fi network. We ran an investigation and found that these iPads are getting stuck on access points when losing connectivity. Here is what we tested: We took 3 devices: iPad 9th generation running iPadOS 17.4.1 iPad 9th generation running iPadOS 26.5.2 iPad 11th generation running iPadOS 26.5.2 We walked around our space with Wireless Diagnostics enabled on the iPads. After some time, we compared the gathered logs. The iPad 9th generation, working on different iPadOS, when connected to a 5 GHz network, gets stuck on one AP. The 2.4 GHz network, on the other hand, works as intended regardless of the authentication method. The iPad 11th generation does not have this issue. Please confirm if this is a known problem. We would be glad to know if there are any fixes available. Attached you will find obfuscated wireless diagnostic logs. We can provide more detailed logs if needed. iPad_wireless_logs.txt

Environment: iPadOS 27 Beta (Developer Beta) iPad with Bluetooth Classic (iAP2/ExternalAccessory) + BLE active session App uses UIKit, WKWebView, scene-based lifecycle Problem: When the user invokes the new Siri AI by long-pressing the power button while our app is in the foreground with an active Bluetooth Classic session, we observe: No scene lifecycle callbacks fire — no sceneWillResignActive, no sceneDidEnterBackground, nothing. We confirmed by logging every UISceneDelegate method. Main thread / data processing threads are starved for ~2 seconds, causing a backlog of incoming Bluetooth data. Our real-time data processing latency jumps from ~105ms to over 2,300ms within 2 seconds of Siri activation. CADisplayLink / requestAnimationFrame callbacks show a ~935ms gap coinciding with the Siri overlay appearance, then irregular intervals afterward. The Bluetooth Classic transport (ExternalAccessory/iAP2) remains physically connected throughout — the issue is purely host-side processing starvation. What we've ruled out: BLE link degradation: firmware-side diagnostics confirm 100% data delivery, 0 lost packets during the incident Memory pressure from our app: our process memory stays flat; system-available memory drops ~14 units externally Questions: Is the absence of sceneWillResignActive when Siri AI activates on iPadOS 27 intended behavior, or a beta bug? The new UIApplication.systemPrefersReducedResourceUsage property (iPadOS 27 beta) — is this intended to signal system overlays like Siri consuming resources? Does the corresponding systemPrefersReducedResourceUsageDidChangeNotification fire when Siri activates? Are there recommended patterns for apps with real-time Bluetooth data processing to maintain thread priority during system overlays? We currently use default QoS for our data processing dispatch queues. The processing starvation causes the waveform display to degrade (appears as a connectivity issue to the clinician) even though the wireless link is healthy. We need either: A notification that a system overlay is active, so we can adjust our UI accordingly Guidance on maintaining processing priority during Siri AI activation Any community insight on workarounds would be highly appreciated. Thanks.

Hello everyone, I submitted my app to App Review five days ago, and its status is still showing “Waiting for Review.” There have been no messages in the Resolution Center and no requests for additional information. The same app was approved on the Google Play Store and has already been live there for a week. I understand that Apple’s review process is different and that review times can vary, but five days without entering the review stage seems longer than usual. Is anyone else currently experiencing similar delays? Should I simply continue waiting, or would you recommend contacting Apple Developer Support at this point? Thank you for any advice or feedback.

I see online theres list of urls app can use to deeplink to Apple apps: https://github.com/bhagyas/app-urls#references-and-additional-resources are these acceptable by Apple? Apps just want to redirect the user so they can take some appropriate action.

我的产品中有一个匹配聊天的功能，但审核被退回显示目前随机或匿名聊天不允许上架，但我测试其它同类APP是有此类功能的，这查怎么回事？

Hello. I made a developer account payment and completed identity verification on January 17, 2026. However, the developer account still shows as inactive. Furthermore, I've submitted requests for assistance, but haven't received a response to any of them. I need urgent help.

App Zekra stuck in “Waiting for Review” for 7 days — two Apple Support requests unanswered Hello, My iOS app Zekra, version 1.1, has been stuck in “Waiting for Review” for approximately one week. Timeline: July 31: Prepare for Submission Saturday, August 8 at 9:58 AM: Submitted for Review Current status: Waiting for Review Version: iOS 1.1 Submission ID: 2ea117b5-3360-41b2-9f73-de01f7627f80 The submission page says: “Your submission has been submitted to App Review.” However, it has not moved to “In Review”, and I have not received any message from App Review or any request for additional information. I have also contacted Apple Developer Support twice regarding the delay, but I have not received a response yet. This is my first App Store submission, so I would like to confirm that there is nothing wrong with my submission or account and that it is simply waiting in the App Review queue. Could an Apple staff member please check whether my submission is progressing normally or whether there is an issue preventing it from entering review? Thank you.

Hello. I've created an Apple developer account but haven't received any feedback. My account is restricted even though I haven't done anything related to my questions. I submitted support requests with numbers 102925492955, 102925472666, and 102924677966 but still haven't received a response. I need urgent help.

We are trying to confirm how SKAdNetwork ad network identifiers relate to an Apple Developer Program membership. Our understanding (from observation) is that the ad network identifier equals the membership's Team ID in lowercase (<TeamID>.skadnetwork), which would imply one membership (one Team ID) maps to exactly one identifier. We could not find documentation that explicitly confirms or bounds this. We checked existing threads first; none answers this specific point: thread/663032 (case-sensitivity), thread/104211 (where to register), thread/652555 (DSP registration) Our questions: Can more than one ad network identifier be registered under a single Apple Developer Program membership (one Team ID)? If it is limited to one, is that limit documented anywhere? Some organizations appear to hold multiple ad network identifiers. Is enrolling separate memberships under separate legal entities the intended way to obtain additional identifiers, or are there other supported configurations? Any clarification from Apple's engineering team would be appreciated. Thank you.

Hi everyone, We're running Xcode/Swift CI builds inside macOS VMs (Tart / Apple Virtualization Framework) on a 32-core Apple Silicon host. While investigating VM build performance, we noticed a consistent pattern: assigning 24 vCPUs to the VM produces faster overall build times than assigning 26-30 vCPUs, despite the host still showing idle CPU capacity. With higher vCPU allocations, the build starts by utilizing the CPUs well, but later stages show a noticeable drop in CPU utilization and overall build throughput. In contrast, the 24-vCPU configuration maintains more stable CPU usage and completes the workload faster. This was observed repeatedly with the same Xcode/Swift workload. The result seems counterintuitive because the VM is not exhausting the available host CPU resources. Our testing identified 24 vCPUs as the current sweet spot, even though the host provides 32 physical cores. Has anyone observed similar behavior? Some questions I have: Do Xcode builds stop scaling efficiently beyond a certain vCPU count? Are there known scheduler or virtualization effects when assigning nearly all host cores to a macOS VM? Is there a commonly recommended practice to leave a number of host cores unassigned, even when the host appears mostly idle?

We develop an endpoint security agent that customer IT deploys and manages via MDM on supervised, ADE-enrolled Macs. The agent requires Accessibility permissions to perform core security functions. Historically, IT provisioned this via the PPPC payload which granted Accessibility as a managed control without end-user interaction. In macOS 27 this path for Accessibility has been removed. The documented replacement — the Privacy key in com.apple.configuration.app.settings — is consent-based: on a supervised device it presents the user a consolidated prompt with "Allow" preselected, which the user may decline. We are seeking guidance on the supported approach for macOS 27 GA: On a supervised macOS 27 device, is there a supported mechanism for an MDM-managed, code-signature-verified application to be provisioned with Accessibility as a managed security control, without depending on individual end-user consent? (i.e. an equivalent to what PPPC provided for enterprise-managed endpoints.) If the consent-based com.apple.configuration.app.settings Privacy declaration is the only path, what is Apple's recommended approach for enterprise-mandated security agents that must have Accessibility to function — including handling the case where a user declines or dismisses the prompt? We have also filed this as an enhancement request via Feedback Assistant (FB23531820). Environment for context: macOS 27 supervised via Automated Device Enrollment, managed by Jamf Pro.

I recently submitted a new app for App Review, and it has been in “Waiting for Review” for longer than expected. I understand that review times can vary depending on Apple’s current workload, but I wanted to ask if other developers are currently experiencing similar delays. The submission is still showing “Waiting for Review”, and there are no messages or issues shown in App Store Connect. Is there currently a longer-than-usual App Review wait time? And is there anything I should do while waiting, or is it best to simply wait for the review to begin? Would appreciate any insight from developers who have recently gone through the same situation. Thank you!

I'm hoping someone from Apple or another developer has some advice. I have an app update that has been stuck in "Waiting for Review" for 12 days. This is not a new app, it's a small update whose primary purpose is to fix a critical bug that's affecting my users. Here's what I've already tried: Submitted two expedite review requests through the official form (I rarely use this process, so it's not something I've abused). Emailed App Review support twice to explain the situation. So far, I've received no response to either the expedite requests or the emails. At this point, users are continuing to experience a bug that has already been fixed, but I have no way to get the update to them. It's hurting the user experience, causing me to lose users, and is directly impacting my revenue. Has anyone experienced something similar recently? Is there anything else I can do besides waiting? I'd really appreciate any guidance, and if anyone from Apple is reading this, I'd be grateful if someone could look into this situation.

Hi, I’m trying to submit my iOS app Minha Pecuária to App Store Connect, but Apple consistently rejects the build with: Validation failed (409) Missing or invalid signature. The bundle ‘br.com.minhapecuaria.ios’ is not signed using an Apple submission certificate. Error 90034. I have already verified that: The app is signed with an Apple Distribution certificate. The App Store provisioning profile is linked to the correct Distribution certificate and Bundle ID. Automatic signing is enabled in Xcode. The exported IPA was independently checked and shows Apple Distribution as the signing authority. The same error occurs through both Xcode Organizer and Transporter. I also reproduced the problem with a clean/new project. Could anyone from Apple or anyone who has experienced error 90034 confirm what could cause Apple’s server to reject a binary that is correctly signed with Apple Distribution? Thanks!

I've been trying for months to get Gemini 3.5 Flash to work with Xcode 27 Beta (1-3) agentic coding but have failed. Xcode currently uses Gemini CLI v0.42.0 from last year, so it can't call Gemini 3.5 Flash even though all that needs to change is a few characters in the API call. Gemini users are currently forced to choose between 3.1 Pro and 3.1 Flash Preview--both weren't the best choices two months ago, but with the release of 3.6 Flash which is better at coding that 3.1 Pro and miles cheaper, these choices are now unsuitable for any serious workload. I live in Hong Kong, where OpenAI and Anthropic services aren't offered, so Google is the only (native) AI provider for Xcode agentic coding. The cost issue from funneling all the work into 3.1 Pro is terrible especially with some agent bugs that have yet to be ironed out. Given Apple's close partnership with Google on AI, I'm genuinely surprised that after 4 Betas we're still using a Gemini CLI from 2025 that forces users to choose between two very unappealing models. Xcode is basically forcing Google users to switch to OpenAI/Anthropic. Questions: I'd like to know if this will be fixed soon and whether Google users should expect slower updates (i.e. be forced to use older models). Does anyone know of any workarounds?

This page: https://developer.apple.com/documentation/devicemanagement/installing-managing-updating-and-removing-apps#Pin-the-version-of-an-app States the following: To find the EVID of an App Store app, use one of these procedures: If the device management service manages the app using declarative management, look for the external-version-id key in the StatusAppManagedList status item that the device reports to the service. If the device management service manages the app using MDM commands, look for the ExternalVersionIdentifier key in the Installed Application List command response that the device returns to the service. Use the Apps and books metadata for organizations API to look up the externalVersionId key in the Apps.Attributes for the app. Ask the app developer to provide the value. The first 2 require access to an MDM and the third in order to use the Appsand books metadata you need to turn your account into an MDM vendor developer account. So the final option is to "ask the app developer". I am the app developer and have no idea how to get this value. As a normal iOS developer is there no other way than to either contract an MDM or turn your account into an MDM vendor?

Hello, We have an enterprise application that provides a security agent plugin with custom UI based on SFAuthorizationPluginView. We’ve been testing it on macOS 27 Developers Betas 1 through 4 and we noticed that if we set screenUnlockMode to 2, then after a screen is locked for the second time during one session, it can no longer be unlocked. Here are the concrete steps to reproduce: Open Terminal. Run sudo defaults write /Library/Preferences/com.apple.loginwindow.plist screenUnlockMode -int 2 Lock the screen. Observe the “You must enter the password to unlock the screen” dialog window. Enter the correct password and press OK. Lock the screen again. Expected result: The dialog “You must enter the password to unlock the screen” is displayed again. Entering the correct password unlocks the screen. Actual result: The screen is black with no visible UI. Rebooting the system seems to be the only way to leave this state. Displaying custom UI at the unlock screen is a part of our core functionality and it has been working fine with screenUnlockMode = 2 since at least macOS 14. I have filed a feedback FB23918474; if it is a known issue, please merge it with mine so that I can receive updates on the matter. In the meantime, do you have any suggestions on what can be done? Thanks.

I am working on a Network Extension (Transparent Proxy) which is used by a DLP to prevent data leaks over the network. For each incoming NEAppProxyTCPFlow, the extension instantiates a custom wrapper object that creates an outbound nw_connection_t to the target host and port using Network framework. When a client application connects to unreachable or blocked ports (e.g., 5222), our extension proxies this connection. As the destination is unreachable, the newly created connection transitions into nw_connection_state_waiting in Network Extension. Since macOS keeps nw_connection_t in the nw_connection_state_waiting state indefinitely, such connections cause system resource leaks. Over time, this leads to: exhaustion of system file descriptors and sockets. system-wide network unavailability until the extension process is killed. Could you provide best-practice recommendations for handling nw_connection_state_waiting in a Network Extension to prevent such resource leaks?

Some UDIDs are getting added immediately but some takes up to 72 hours and status is "iPhone Processing". Is there a way to get this processing expedited and why some devices gets added immediately.

Hi guys, I've exported the images with transparency for a Vision OS icon but I still keep getting a weird shadow on the top of the icon when I focus on it. Do you guys had this issue before?