Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.

I am testing SFSpeechRecognizer using the en_US locale. When the iPhone Simulator’s system language is set to Japanese, SFSpeechRecognizer.isAvailable returns false for en_US, so speech recognition is unavailable. As far as I have tested, this issue does not occur on iOS Simulator 26.2 or earlier. Is this a Simulator-specific issue, or is it a behavior change that could also occur on physical devices? Has any additional setup become necessary to use speech recognition in Simulator? I then changed the iPhone Simulator’s system language to English. After doing so, SFSpeechRecognizer.isAvailable returned true for en_US. However, starting a recognition task still failed immediately with kLSRErrorDomain Code=300, “Failed to initialize recognizer.” The following error was returned: Error Domain=kLSRErrorDomain Code=300 "Failed to initialize recognizer" UserInfo={ NSLocalizedDescription=Failed to initialize recognizer, NSUnderlyingError={ Error Domain=kLSRErrorDomain Code=300 "Failed to create recognizer from=/Users/<USERNAME>/Library/Developer/CoreSimulator/Devices/<DEVICE-UUID>/data/private/var/MobileAsset/AssetsV2/com_apple_MobileAsset_UAF_Siri_Understanding/purpose_auto/ c079bfa6b8856202dc8cb2135fef3b06229ced6e.asset/AssetData/mini.json" UserInfo={ NSLocalizedDescription=Failed to create recognizer from=/Users/<USERNAME>/Library/Developer/CoreSimulator/Devices/<DEVICE-UUID>/data/private/var/MobileAsset/AssetsV2/com_apple_MobileAsset_UAF_Siri_Understanding/purpose_auto/ c079bfa6b8856202dc8cb2135fef3b06229ced6e.asset/AssetData/mini.json } } } I have not observed either of these issues on iOS Simulator 26.2 or earlier: With the Simulator language set to Japanese, the en_US recognizer does not become unavailable. When SFSpeechRecognizer.isAvailable is true, recognition does not fail with kLSRErrorDomain Code=300. Environment Xcode: 26.6 (17F113) iOS Simulator 26.5 (23F77), iPhone 17 (A3258J/A) iOS Simulator 26.4 (23E244), iPhone 17 (A3258J/A)

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

Since Xcode 27 GA, text entry from a UI test on a physical iOS 27 device delivers only the first 3–4 characters and then stops, while the call still returns success. Taps and scrolls are fine. The same tests pass on Xcode 27 beta 1. Filed as FB24932647. Broken: Xcode 27.0 (27A266a), 27.1 beta (27A9269), 27.2 beta 2 (27B5028f) Works: Xcode 27 beta 1 (27A5194q) Device: iPhone, iOS 27.0 (24A437) Repro. We drive it through WebDriverAgent. The failing step is XCTest's own event synthesis in testmanagerd, which is the same path XCUIElement.typeText goes through. Xcode 27.2 beta 2, run sudo xcodebuild -runFirstLaunch, reboot the device. Type subjectline into a plain UITextField. Read the field's value back. Expected subjectline. Actual sub or subj, in every one of 16 attempts. In a recipient-style field the fragment appears and is then erased, so nothing survives. 0 of 32 attempts completed. Device log, all within one second: testmanagerd Failed to load displays from CADisplay testmanagerd Failed to resolve displays. Defaulting to generic keyboard sender. testmanagerd Recap event action playback initiated UIKitCore hardwareKeyboardAttached = YES UIKitCore Moving from placement OnScreen to OffScreenDown UIKitCore Change to input view set: (empty) testmanagerd Recap event action playback completed testmanagerd can't resolve a display, so it falls back to a generic keyboard sender that registers a virtual HID keyboard. iOS then treats that as a hardware keyboard and dismisses the software keyboard while the text is still being typed. What changed. Comparing testmanagerd in the two DeveloperDiskImages: beta 1 derived the display from the app's identity (Computed display ID … from embeddedApplicationIdentifier … bundleID). GA removed that and added CADisplay enumeration with the generic fallback. That code is unchanged through 27.2 beta 2. This is not 181945323, which is marked fixed in 27.2 beta 2. That one needs Device Hub and clears on its own. Is anyone else seeing this on device? Is there a supported way to type on device under Xcode 27 GA, other than staying on beta 1?

We’re using an Enhanced Security helper extension with AppExtensionProcess and XPCSession to isolate native zero-knowledge proof generation from wallet and signing code. On an iPhone 15 Pro running iOS 26.6.2 (23G90), the helper terminates with: EXC_RESOURCE RESOURCE_TYPE_MEMORY: high watermark memory limit exceeded (limit=35 MB) Terminated due to memory issue Our current prover requires substantially more memory: its public proving key is approximately 402 MiB, and its witness workspace alone is approximately 69 MiB. The same proof engine has completed successfully in a standalone iOS app process. The helper currently processes only synthetic test inputs. We want to preserve the helper’s sandbox and Enhanced Security protections and use a configuration supported for App Store distribution. Is there a supported way to increase the memory limit for this specific helper extension type? Does com.apple.developer.kernel.increased-memory-limit apply to Enhanced Security helper extensions? If so, what provisioning, target configuration, and device/OS requirements apply?

I am using Coding Intelligence, powered by Claude, in the first production release of Xcode 27.0 (in MacOS 26.7). Initially it was working ok. But after less than a day, it now crashes every time it needs to ask for permission for any shell command. And each time I restart things, it burns through a ton of tokens. ☹️ Any suggestions? (I'll file a bug report right now…)

Using Xcode 27.1 RC, the iPhone Duo simulator (Device Hub) only comes with the Settings and Safari apps. Am I missing something? Are there plans to have the usual simulator apps such as Photos, Calendar, Reminders, Maps, etc.? In these early stages it would be really nice to have some real apps to look at for examples of how some things should work/appear on the Duo in different layouts.

I am rather flabbergasted by the “future Xcode project file format” error. It happens in Xcode 26: Indeed the project was maintained so far in a 27, nevertheless, the project format is set to **16**: Can please someone explain the culprit and suggest a fix? Thanks!

I've still an old iPhone X (running iOS 16.7.16) and like to also use this to test/debug my Apps, but it seems that XCode 27.1 does no longer support it. The device simply does not show up in the new Device Hub. I still have some App-specific data on this device, which I would like to use for the tests, but as XCode now ignores this device, I can't even copy the data over to the newer devices. Is it somhoe possible to add the device to the device Hub, or make it available to XCode so I can actually test on this device as well?

Compiling my project using Xcode 27.1 ends with an error: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX27.0.sdk/System/Library/Frameworks/SwiftUI.framework/Modules/SwiftUI.swiftmodule/arm64e-apple-macos.swiftinterface:1:1: error: failed to build module 'SwiftUI'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 6.4 effective-5.10 (swiftlang-6.4.0.31.4 clang-2100.3.31.1)', while this compiler is 'Apple Swift version 6.4 effective-5.10 (swiftlang-6.4.0.34.1 clang-2100.3.34.1)'). Please select a toolchain which matches the SDK. 1 | // swift-interface-format-version: 1.0 | `- error: failed to build module 'SwiftUI'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 6.4 effective-5.10 (swiftlang-6.4.0.31.4 clang-2100.3.31.1)', while this compiler is 'Apple Swift version 6.4 effective-5.10 (swiftlang-6.4.0.34.1 clang-2100.3.34.1)'). Please select a toolchain which matches the SDK. 2 | // swift-compiler-version: Apple Swift version 6.4 effective-5.10 (swiftlang-6.4.0.31.4 clang-2100.3.31.1) 3 | // swift-module-flags: -target arm64e-apple-macos27.0 -enable-objc-interop -target-arch-variant arm64e.x1 -enable-library-evolution -language-mode 5 -O -library-level api -enable-experimental-feature AnyAppleOSAvailability -enable-upcoming-feature InferSendableFromCaptures -enable-experimental-feature DebugDescriptionMacro -enable-bare-slash-regex -user-module-version 8.0.84.1.406 -module-name SwiftUI -package-name SwiftUICompiling it with Xcode 27 ends without error. Do you see any other root cause than the one mentionned: Xcode 27.1 uses swiftlang-6.4.0.34.1 clang-2100.3.34.1 while internal sdk was compiled with swiftlang-6.4.0.31.4 clang-2100.3.31.1 ?

Can I download the iOS 26 simulator runtime via a download link? The machine I need to deploy on may require an offline package installation due to firewall restrictions.

On Xcode 27.0 (27A266a) / macOS 27.2, I ran xcrun mcpbridge from a scripted stdio MCP client and captured traffic system-wide, with a curl control visible in the same captures. Findings: mcpbridge itself opened no network sockets (online or offline, and under a deny-network sandbox). The "Xcode Service" process it connects to made about 2 KB of outbound TLS to an Apple edge address at startup, plus a certificate check via trustd and a request to devimages-cdn.apple.com. When a workspace was opened through XcodeOpenWorkspace, Xcode Service also made two TLS connections to appstoreconnect.apple.com (about 5 KB upstream). This did not occur without a workspace open, and XcodeListWorkspaces itself caused no traffic. mcpbridge sends a CoreAnalytics event to analyticsd (strings: "MCPBridgeTelemetry: Submitted CoreAnalytics event" / "Telemetry off; skipped"), payload <private>. Questions: What is sent to App Store Connect when a workspace is opened this way, and is it the same as opening the project in Xcode directly? What does the MCPBridgeTelemetry event contain, is it sent off-device, and what setting controls it? Is any MCP tool input or output (file contents, paths, build output) sent to Apple?

A Mac reboot fixed it for a few images, but then it went black again.

I have Xcode 27.1. When I open the Developer Documentation window, it only has the 27.0 APIs. While running Xcode 27.1 if I go to Xcode -> Settings -> Components -> Developer Documentation -> Info, the info window shows the Xcode version as 27.0 and the Developer Documentation Version as 10M13950. Xcode -> About Xcode definitely shows version 27.1. It's very difficult trying to work on iPhone Duo support when the developer documentation doesn't show any of the iOS 27.1 APIs. Is there any way to get the proper documentation loaded?

Hallo everyone, We are building our app with Xcode 27 and noticed that UIDesignRequiresCompatibility still appears to be honored on iOS 26 devices. Questions: Could you confirm whether this key is still supported on iOS 26 when built with Xcode 27? If our deployment target includes iOS 26, should we keep the key for backward compatibility, or is Apple's recommendation to remove it entirely? Additionally, are there any risks associated with removing it for iOS 26 users?

I'm trying to use Xcode Coding Assistant connected to local AI server, but the chat fails after 5 minutes with error: The request timed out. Detail: No Data/Bytes for request: http://localhost... AI server gives me info that client disconnected: 2026-10-19 22:24:23 [INFO] [nvidia/nemotron-3.5-super-vl] Prompt processing progress: 88.3% 2026-10-19 22:24:30 [INFO] [LM STUDIO SERVER] Client disconnected. Stopping generation... (If the model is busy processing the prompt, it will finish first.) 2026-10-19 22:24:30 [INFO] [nvidia/nemotron-3.5-super-vl] Finished streaming response 2026-10-19 22:24:31 [DEBUG] 17.12.133.523 W srv stop: cancel task, id_task = 0 2026-10-19 22:24:37 [DEBUG] 17.18.441.198 I slot release: id 0 | task 0 | stop processing: n_tokens = 47985, truncated = 0 It looks like http/tcp default timeout. AI suggests that it should be possible to set Xcode Coding Assistant timeout, but I cannot find it anywhere. How is Xcode Coding Assistant supposed to work if it shuts down on default network protocol timeout? I haven't tried yet on nVidia hardware, which should be faster, but it could still be a problem when working on multiple files in project with inference running on one Blackwell chip. I do not have nVidia rack with 72 chips, it wouldn't fit to my home office. How do I change the network timeout for Coding Assistant? Configuration: MacOS 27.0.1 (26A434) Xcode 27.0

Oldest model of 5.5 with codex is deprecated by chatgpt but I only see 5.5 as the highest available model selectable in the dropdown in intelligence settings in Xcode when selecting codex I have the ChatGPT pro account and login to codex in xcode via email/password and not the API key I have already tried login out, quitting xcode, removing codex agent and reinstalling it, so far nothing works

I'm hitting a toolchain inconsistency between Xcode 26.3's asset compiler (actool) and App Store Connect's upload validator, and I have build logs proving both sides. The builder side (actool in Xcode 26.3): When compiling the asset catalog for our watchOS target, actool reports "unassigned children" for the watchOS longLook icon role - specifically [watch][44x44][longLook][42mm][2x] - and does NOT compile it into Assets.car. The 42mm longLook icon simply cannot be produced by the toolchain. The checker side (App Store Connect): Uploading the resulting archive is REJECTED by the App Store Connect validator with a "Missing Icon" error for a 44x44 at 2x image (Long Look 42mm). So the builder cannot produce the exact icon the checker demands. This is an Apple toolchain inconsistency - either: actool should compile the longLook 42mm role into Assets.car, or the App Store Connect validator should not demand an icon the toolchain cannot emit. Environment: Xcode 26.3 watchOS app target with an App Icon asset catalog containing the longLook role configured for 42mm 2x Question: Is this a known issue, and is there a workaround to produce an upload that passes validation? I can provide build logs for both sides on request.

Hi everyone, I've been struggling with a TestFlight issue for over a month, and I'm hoping someone here has encountered something similar or knows how to resolve it. I'm developing an iOS app called Bondi, and every time I try to submit a new build for external beta testing, App Store Connect returns an HTTP 422 error. I've tried contacting Apple Developer Support, but I haven't received a helpful response, and I'm completely blocked from distributing new builds to my external testers. The error: When submitting a build for Beta App Review, the following API request fails: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "9fc5c303-4edb-4aee-9b39-75c8c8c53e1c" } } } } } The browser console shows: The server responded with a status of 422. API Response Error: TF_BETA_APP_REVIEW_RESPONSE status code: 422 api correlation key: SRKTSBKDZ2F7XPBJH7XFYSBUL4 In previous attempts, I also encountered this error: `ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING im not sure it's connect but I also noticed the following console warning: fetched via init(), using default/cached config values. What I'm trying to understand Has anyone encountered BETA_CONTRACT_MISSING when submitting a TestFlight build? Does TestFlight require any additional agreements, even for completely free applications? Could this indicate an issue with my Apple Developer account rather than the app itself? Is there any workaround to reset or reinitialize the TestFlight beta agreement? Can someone from Apple confirm whether this is a known issue? I've been blocked for over a month, and it's incredibly frustrating that App Store Connect provides no meaningful explanation of what's wrong.

Hi everyone, I’m currently experiencing unusually long review waiting times and wanted to ask if others see the same behavior this week. My situation: • App Store update has been in “Waiting for Review” significantly longer than usual • A newly submitted build also seems stuck • TestFlight processing is slower than I normally see • Expedited review request and contact attempts didn’t change the status so far