Overview

I started enrolling in the Apple Developer Program last Sunday. The confirmation email said I should receive a response within two business days, but it's now been five days and I still haven't heard back. Is this normal?

Hi everyone, I'm working on a Live Activity implementation for a ticketing app (written in Swift/SwiftUI with ActivityKit), and I've encountered an unexpected behavior on iOS 26.2.1 that contradicts my understanding of the documentation. What the docs say: The official ActivityKit documentation states: "The system uses the minimal presentation when more than one app has an active Live Activity." This implies the two minimal slots are intended for two different apps. There is no documented scenario where a single app occupies both minimal positions simultaneously. What I observed: On a device running iOS 26.2.1, with two active Live Activities from the same app running at the same time, both minimal views appeared on the Dynamic Island simultaneously — one attached to the island, one as a detached floating pill. Questions: Is this behavior intentional in iOS 26, or is it a regression / unintended side effect? Has the system policy changed in iOS 26 to allow a single app to occupy both minimal slots? If this is expected, is there any updated documentation or release notes that cover this change? Environment: Device: iPhone 14pro iOS: 26.2.1 Xcode: xcode26 Any insights from Apple engineers or developers who've seen this would be greatly appreciated. Thanks!

Hi everyone, Our organization account has been stuck in review hell for almost 3 months now if you count the enrollment phase. Long story short, we got hit with a Guideline 2.3.1(a) rejection recently. We spent days cleaning up the entire codebase, stripped out all old/unnecessary libraries, and ran static analysis to make sure everything is completely standard. There is zero obfuscated code or dynamic execution now. We submitted this clean version (Build 9) 6 business days ago, but it's just sitting there in 'Waiting for Review'. No updates, no emails, nothing. This delay is seriously hurting our business operations and commercial launch. The active case ID for this issue is 102893875646. If any Apple moderator or representative here can ping the App Review team or escalate this internally, it would be a lifesaver. Thanks.

Hi everyone, quick question, as the title suggests: is there a mode that bypasses permission requests for actions that aren't already in "Always Allowed" mode? Something like Claude Code's "dangerously skip permissions" setting. It's quite annoying to see his conversation ask for permission dozens of times; Thanks!

Hello everyone, I'm looking for advice from developers who may have encountered a similar situation. I originally submitted an app called Bien, which provides financial services and handles sensitive user data. During review, Apple rejected the app under Guideline 5.1.1 and advised that the app must be published under a seller/company name that reflects the Bien brand. Following that guidance, we went through the process of creating a new Apple Developer account under the appropriate company identity and submitted the app again using the new account. However, the new submission has now been rejected under Guideline 4.3(a) (Spam) because the binary, metadata, and concept are similar to apps submitted under another developer account. The challenge is that the similarities exist because it is the same app, being resubmitted under the new account that Apple previously indicated should be used. We have: Submitted a formal appeal. Opened a support case with Apple. Provided the previous review communication showing the requirement to publish under the Bien company name. Has anyone experienced a situation where an app was moved to a new developer account following Apple's ownership or branding requirements and subsequently received a 4.3(a) rejection? If so: How was the issue resolved? Was additional documentation required? Did App Review eventually recognize the account transition and approve the app? Any insights would be greatly appreciated. Thank you.

Hi there, my App is showing "Waiting for Review" over 1+ week later. Previous reviews on this app went through within 24 hours, so this is a clear outlier. I've submitted expedited review requests, replied via Resolution Center, contacted App Review via the support form, and called phone support — all with no response or no ability to help on their end. Has anyone gotten unstuck from a similar situation recently or are longer review times common currently? Appreciate any pointers.

Hi there, my app is still showing "Waiting for Review" over 1 week later. Previous reviews on this app went through within 24 hours, so this is a clear outlier. All prior reviewer feedback has been addressed in the current build. I've submitted expedited review requests, replied via Resolution Center, contacted App Review via the support form, and called phone support — all with no response or no ability to help on their end. Has anyone gotten unstuck from a similar situation recently? Appreciate any pointers.

Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.

Dear community, I recently transferred my iOS app to a different developer account as part of an app acquisition. When uploading now on the new team the first build from the new team via Xcode Cloud, I get: ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['OLDTEAMID.ch..'] and the new version of software being submitted has an application-identifier of ['NEWTEAMID.ch..']. This will result in a loss of keychain access. I understand this is expected, since the App ID prefix changed from the old Team ID to the new one. The problem is that this app is a crypto wallet: it stores the user's private key in the keychain using the default access group ($(AppIdentifierPrefix)$(CFBundleIdentifier)), with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and no iCloud synchronization. If existing users update to a build signed by the new team, they permanently lose access to their keys — there is no server-side recovery. <key>keychain-access-groups</key> <array> <string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string> </array> It was extremely stupid to do it like this :( I've read the "App ID Prefix Change and Keychain Access" post, which describes migrating keychain items into an app-group-based access group before the transfer, then transferring the app group along with the app. Unfortunately, my transfer has already completed. My questions: Is transferring the app back to the original team, shipping a migration update that moves keychain items into an app group access group, and then re-transferring the app together with the app group still the recommended (and only) path in this situation? Are there any pitfalls with migrating items protected by SecAccessControl (.userPresence) into an app group access group, given that reading them requires biometric/passcode authentication? Is there any timing constraint or cooldown I should be aware of when transferring an app back and then transferring it again shortly after? Any other less time intensive options? Is it possible to "transfer a team id"? Or rename/handover the old account to the new developer? Thank you for the team and guidance on this.

Don’t spam

Hello, I’m trying to use a third-party MCP server (ICM) in Xcode 27’s new Coding Assistant. The server appears to start correctly and shows up when I run /mcp, but as soon as an agent tries to use it, Xcode appears to rewrite my config and changes "enabled = true" to "enabled = false". My configuration looks like this: [mcp_servers.icm] command = "/opt/homebrew/bin/icm" args = [ "serve", "--no-embeddings", "--db", "/Users/Sam/emdash/worktrees/Castle/emdash/custom-widget-system-5dubi/.icm-xcode/memories.db" ] enabled = true I’ve spent quite a while debugging this and found some interesting behaviour: The MCP server appears when I type /mcp. SQLite databases can be created and written inside the current workspace. SQLite databases can also be created and written in /tmp. SQLite databases outside the workspace (for example in ~/Library/Application Support) fail with readonly/open errors. Ordinary file operations outside the workspace still work fine. What I’m trying to understand is: Why is Xcode disabling the MCP server? What filesystem access should MCP servers have? Are they intentionally restricted to the workspace and /tmp? Is there a supported way to allow an MCP server to access data stored elsewhere on disk? Has anyone else run into this? Thanks!

ubject: Walkie-Talkie App Not Working After Updating to iOS 27 Developer Version Dear Support Team, I am experiencing an issue with the Walkie-Talkie app after updating my device to the iOS 27 Developer Version. Since the update, the app is not functioning properly, and I am unable to connect or communicate with my contacts using Walkie-Talkie. I have already tried several troubleshooting steps, including restarting the device, checking my network connection, and verifying that both FaceTime and Walkie-Talkie are enabled. However, the issue still persists. Could you please help identify the cause of this problem and advise on any available solutions or known issues related to the iOS 27 Developer Version? Device Model: [IPHONE 17] iOS Version: iOS 27 Developer Version Issue Started: Immediately after updating to iOS 27 Developer Version Thank you for your assistance. I look forward to your response.

Hello, In early May, Apple Support asked me to provide identity verification documents for my developer account (payments up to date since 2016). I submitted the requested documents. Since then, I no longer have access to certificates, identifiers, and profiles on my account, which prevents me from submitting or updating my apps. I have contacted support 6 times (same reference number: 102888223471) without receiving any response. My account is in good standing (active payments since 2016), and this situation is completely blocking my development activity. Has anyone experienced the same issue or can help escalate this? Thank you in advance.

我的账号注册提交身份ID很多天了,一直没有激活, 界面一直提示最多需要2-4天, 可是已经过去了很多天了仍然一直是这样;

I’ve developed a service that migrates saved locations from other services to Apple Maps using Apple Maps Guides. Are you planning to develop this service in the direction of native migration or increasing its limits? We’ve noticed a high demand for this request, but we’re currently hitting Server API limits.

Hi Everyone, Our app update has been in "Waiting for Review" status for over a week now, which is well beyond the usual review window. It has not yet moved to "In Review." Status: Waiting for Review (unchanged for 7+ days) Contains a critical production bug fix Our live users are currently affected by an issue, so getting this update through is fairly urgent. We have already submitted an expedited review request, but there has been no movement so far. Is anyone else experiencing unusually long "Waiting for Review" times recently? Any guidance on whether this is a known backlog, or anything we can do to help move this along, would be greatly appreciated.

The Menu command to create a new project based on a Package.swift file is gone. How am I supposed to do this now?

I previously attempted to apply for the hotspot-provider entitlement but was rejected. I no longer require this entitlement. I need to remove the hotspot-provider permission although the Network Extensions capability is checked. However, the generated provisioning profile still includes the hotspot-provider permission, which causes error 409 when I upload the IPA file. I only need the Network Extensions entitlement. Could you please advise how to remove hotspot-provider from the provisioning profile?

报错日志：Error Domain=CBErrorDomain Code=15 详细内容如下 1213: 2026-06-10T12:22:33.608+08:00 new_carkey: BLEDevicesFinder didFailToConnect: <CBPeripheral: 0x708e3ad7a0, identifier = 79CFD7C7-C273-E5D6-E5F6-EA9B7BFC3500, name = NIO Key 0791 , mtu = 0, state = disconnected>, Optional(Error Domain=CBErrorDomain Code=15 ""Failed to encrypt the connection, the connection has timed out unexpectedly."" User... <skipped 110 characters> ...

Description of the Issue: We are experiencing intermittent, severe latency spikes during cellular data transmission (specifically with MQTT Publish) on iPhone 17 devices. Through internal testing and cross-referencing with similar user reports online, we suspect this is caused by an aggressive power-saving or sleep mechanism in the cellular modem/iOS network stack when traffic is sporadic or low-frequency. Steps to Reproduce / Observations: Establish an MQTT connection over a cellular network (5G/LTE) on an iPhone 17. Publish messages at irregular or low-frequency intervals (e.g., sporadic IoT data transmission). Result: Severe latency spikes occur intermittently during transmission. Diagnostic Findings & Documented Workarounds: Workaround 1 (Constant Traffic): If we connect a secondary device (e.g., a PC) to the iPhone 17's Personal Hotspot and run a continuous background ping (with a 10ms interval), the MQTT latency spikes disappear completely. This high-frequency traffic prevents the device/modem from dropping into power-save mode. Workaround 2 (VPN Tunnel): Utilizing a VPN profile (such as Cloudflare's 1.1.1.1 app) significantly mitigates the issue. We suspect this is due to either the VPN's background keep-alive packets maintaining the active state of the modem, or iOS applying a less aggressive power-saving policy to active VPN interfaces. System Environment: Device: iPhone 17 series OS: iOS 19 (or specify your current version) Network: Cellular (5G/LTE) Questions Regarding Temporary Workarounds & Mitigations: To unblock our current development and ensure a reliable user experience before an official OS-level fix is deployed, we would highly appreciate Apple's technical guidance on the following questions: Recommended Keep-Alive Mechanism: Since higher frequency traffic effectively prevents the modem from entering power-save mode, does iOS have a recommended, power-efficient way for an application to maintain an active cellular network state (e.g., recommended TCP/MQTT keep-alive intervals or NWPathEvaluator configurations) without being suspended or penalized by the system? Network Optimization APIs: Are there specific Network Framework APIs (Network.framework) or socket configuration flags (such as Multipath TCP, or Quality of Service (QoS) flags like Background vs Default) that can signal to the iOS kernel to apply a less aggressive power-saving policy on the active cellular interface? Background Execution Policy: For IoT applications that need to publish MQTT data seamlessly while running in the background, what is the best practice to prevent the cellular link from dropping into deep sleep mode? We would appreciate it if the Apple Network/CoreOS engineering team could look into this cellular power management behavior. Thank you for your support.