Heya! I'm preparing my apps for the iPhone Duo, but having a hard time with the Simulator for it. Basically it's very very slow, crashes often (not speaking about my app but the device hub tool freezes or crashes). Restarting it often helps to kinda "cleanup" when it starts feeling like deep mud when using it, but it would not make it smooth just less deep mud feeling. I am running it on an M1, so that would probably be a good reason for it going this slow. However, any tips to make it run better? Things, settings I can toggle on and off?

For simctl shipped with Xcode 27.0 build 27A266a, is there a supported way to deliver launch stdout/stderr directly to an in-memory consumer without first writing raw output to a regular file, then stop the collector within a bounded time without forwarding a signal to, blocking, terminating, restarting, or changing signal policy in the launched application? Please identify the documented interface and supported OS/runtime scope, or explicitly state that this combination is unsupported. Do stdout/stderr path options officially accept a FIFO or other nonpersistent sink, and where is that sink resolved? What open/create/truncate/blocking behavior and reader-before-writer order are guaranteed? Which process owns the output writer after launch returns? Does simctl exit or collector detach close, transfer, or leave that writer alive? At consumer byte/time limit, EOF, reader closure, collector failure, or backpressure, what happens to App writes and signals, including SIGPIPE/EPIPE? Is there a supported independent detach/drain mechanism that avoids App effects and indefinite background collection? Can the supported interface guarantee no raw-output file or replay spool before the consumer, and which documented limits can the consumer enforce without affecting App lifecycle? Please identify the supported interface, applicable tool/runtime versions, and documented lifecycle guarantees, or clarify which requirements are unsupported. This request is limited to the public tool interface contract and contains no application logs, source code, device identifiers, customer data, or diagnostic attachments.

xcstringstool compile (and by extension CompileXCStrings in Xcode/Bazel builds) hangs indefinitely on .xcstrings files where one or more keys have a localizations entry count that is a significant outlier relative to the rest of the file's keys — even when total file size and total entry count are unremarkable. The tool produces no error, warning, exception, or log output; it simply spins at high CPU with flat memory until killed.

I am working on adding an iOS app to my existing MacOS app. However Transporter shows them both identically. They have the same icon and the same major version number. Please add some clue as to the OS type of each delivered submission so I can tell them apart.

The iOS 17 simulator does not respond at all when I try to interact with it. The simulator is not frozen as I can still control appearance and launch apps via the right sidebar. Things like the home button and clicking on the screen simply don’t work. I am using Xcode 27 beta 6. Feedback ID: FB24674634

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

In an app using SwiftUI's NavigationSplitView with UIKit view controllers hosted via UIViewControllerRepresentable in the detail pane, a UIBarButtonItem (system .search) in the hosted view controller's navigationItem disappears visually when the iPhone Duo simulator view is dragged to the right side while the Duo is open, while its tap target remains active in the same location, however when tapped, nothing happens. Dragging back to the center restores the icon. The same button, and the same NavigationSplitView layout, is completely stable under equivalent live window-resizing on Mac Catalyst -- resizing the Catalyst window never reproduces the issue. This seemingly points to the Duo simulator's window/hit-test recomposition during the fold transition rather than an app-level bug. See screenshots. I

if i try to take a screen shot of the iPhone duo simulator with the screen shot button at the bottom of the device hub, it turns out all black. This only happens in the folded state.

Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing.

Hi everyone, I’m currently running macOS 27.0 beta (26A5388g) on my Mac, along with the latest Xcode 27 beta, and I’ve recently started experiencing a serious issue where multiple macOS system services are repeatedly crashing. Initially, I started getting repeated “intelligencetasksd quit unexpectedly” notifications. At first it happened occasionally, but it has now become extremely frequent. After dismissing one crash notification, another system service often crashes shortly afterward. I’ve also seen services related to Intelligence / intents crashing. The notifications keep appearing one after another to the point where I’m barely able to use the Mac normally — including difficulty typing and interacting with applications. The issue is not limited to Xcode. It appears to affect macOS system services themselves. System information Mac: Mac15,2 (Apple silicon) macOS: macOS 27.0 beta, build 26A5388g Xcode: Xcode 27 beta Issue started: After running the macOS beta for some time; it has progressively become more frequent Main process initially crashing: intelligencetasksd Path shown in crash report: IntelligenceTasksEngine.framework/Support/intelligencetasksd Exception: EXC_BREAKPOINT (SIGTRAP) I have attached a screenshot of the crash report showing the intelligencetasksd crash. Has anyone else experienced this on macOS 27 beta? Is there a known issue with the new Intelligence/Intents services, or is there a recommended way to reset/rebuild the relevant system components? At this point the repeated crashes are making the Mac extremely difficult to use, so I’d really appreciate any troubleshooting steps or information about whether this is a known beta issue. Thanks!

When I try to download the metal toolchain 26.6 (17F109) in Xcode it just stays on preparing to download. Does anyone have an idea on how to fix this? I'm on macOS 26.6.1 (25G76)

I have a problem downloading Xcode components like Metal Toolchain or Developer Documentation. The action stuck with the status "Preparing to download". The symptoms started several weeks ago. I noticed this when my copy of Xcode 27 beta stopped showing the developer documentation. Strangely, when I re-launched Xcode it insists to download the Developer Documentation and keep showing "Preparing to download" while other components like Metal Toolchain, when I quit Xcode, it cancels the component download and that component status reverts to "Get". The symptoms continue thru the released version of Xcode27. Does anyone know the cure?

When I archive and distribute any iOS app from Xcode 27.0 RC on macOS 27.0 Golden Gate, the upload stalls indefinitely at “Preparing to upload [App].ipa”. The archive, signing, provisioning, IPA packaging, and App Store Connect authentication all complete successfully. This is reproducible with multiple unrelated iOS projects on the same machine, so it does not appear to be caused by a specific app, signing configuration, asset, or bundle identifier. Cancelling the upload is the only way to exit the stalled state. I also checked with ChatGPT Codex if it can narrow down the issue. It states: "The failure occurs when Xcode launches the swinfo utility from the ContentDelivery framework to generate the asset description.swinfo crashes with SIGSEGV / exit code 139. The crash report reports:Thread stack size exceeded due to excessive recursion". But I actually never got an error message during the upload itself, it just hangs indefinitely at "preparing to upload..." (Tried it several times up to 36h). This issue is new since I updated to macOS Golden Gate and xCode 27 RC. Xcode Cloud is the only working option right now to upload a Build to App Store Connect. Anyone experiencing the same issue and found a solution? What I already tried: Revoke and renewed my Apple Distribution certificate. Delete xCode, Installed it again (I also installed xCode 27.2 Beta which I knew would not work to upload an app to App Store Connect from a Beta version). Created a brand new project and tried to upload this. Also hang at "preparing to upload..."

Neither in Xcode 27 beta 1 or 2 we have been able to use simulators for the intel x86 architecture. Is there any way to get them?

This is a repost of https://discussions.apple.com/thread/253025487 Hi, How do you pipe selected text in Apple Xcode out to an external program, replacing it with the output from that program? For example, in MacVim, you can type !}command to pipe the rest of the current paragraph to command, replacing the original text with the output of that command, which is hella useful if you’ve written a lot of filters for tasks like automatic text reflowing or automatic source code reformatting. How do you do this in Apple Xcode? I am running Apple Xcode Version 10.1 (10B61) [the highest-numbered, most-recent version of Xcode compatible with Apple macOS Version 10.13.6 “High Sierra”]. ’preciate it, Austin

Hi. Today we upgraded to Xcode 27 and installed the iOS 27 runtime component. Now storyboards cannot be opened. Xcode only displays "Loading iOS 27.0..." Besides, we cannot create simulators either. iOS 27 runtime appears missing even though it is installed. We tried removing and reinstalling the runtime but it didn't work. Right now all development came to a halt. Please help.

I can no longer use Codex within Xcode anymore because it says it's unsupported. gpt-5.5 has been out for several months...please update for support for it. I don't want to have to jump through a bunch of hoops using Terminal just to be able to use Codex in Xcode.

Large companies/applications are good to go for Duo release. Is there a timeframe when Xcode 27.1 will be available so we can build and submit to App Store in time for Duo release? Any guidance around this?

Environment Xcode 27.1 (27A9269) Simulator runtime: iOS 27.1 (24A94401) Device: iPhone Duo simulator (unfolded) macOS 26.7.1 (25G241), Apple silicon Mac Hardware keyboard connected (default Simulator setting) Summary After locking the iPhone Duo simulator with ⌘L and unlocking it, the whole display stays dimmed and appears unresponsive. Both apps in split view are affected. Pressing the ⌘ key once restores the screen immediately. This reproduces with only system apps (Settings + Safari), so it does not appear to be app-specific. Steps to reproduce Boot the iPhone Duo simulator (iOS 27.1) and unfold it. Open Settings and Safari side by side in split view. Press ⌘L to lock the device. Unlock (swipe up on the lock screen). Expected The display returns to normal brightness and both apps respond to input. Actual The entire display, including both split-view apps, stays dimmed. Taps appear to do nothing while it is dimmed. Pressing ⌘ once immediately restores normal brightness. After recovering, Settings had navigated to a different page, which suggests some taps were delivered while the screen was dimmed. Notes It looks like the simulator misses the ⌘ key-up when ⌘L locks the device, so iOS behaves as if ⌘ is still held (the hold-⌘ shortcut overlay dimming the screen). Locking with Device ▸ Lock from the Simulator menu avoids the ⌘ modifier entirely. In one case the dimmed state persisted across relaunching an app and only cleared after rebooting the simulator. We first hit this while testing our own app in split view, where it looked like an app hang. Sampling the app's process showed the main thread idle. Workaround Press ⌘ once after unlocking, or lock with Device ▸ Lock instead of ⌘L. Has anyone else seen this on the iPhone Duo simulator, or is this a known issue?

Hi everyone, I am developing an iOS companion app with an integrated watchOS component (a golf swing tracking tool using CoreMotion). I have run into an issue where the watchOS app gets stuck indefinitely in the "Installing..." state and never finishes installing on the physical Apple Watch. Environment (All on latest public releases): Xcode Version: Latest release (Xcode 18.x) macOS Version: Latest release (macOS Sequoia / latest version) iOS Version: Latest release (iOS 20.x) watchOS Version: Latest release (watchOS 13.x on Apple Watch Ultra 2) Deployment Target: Matched to latest minimum deployments Signing: "Automatically manage signing" enabled with an active Apple Developer Program account Steps to Reproduce: Connect the iPhone to the Mac via a physical cable. Select the iOS target in Xcode and successfully run/install the companion app onto the iPhone. Launch the stock Watch app on the paired iPhone. Scroll down to the "Available Apps" section, locate the development app, and tap "Install". The circular progress indicator starts spinning with the status "Installing...", but it remains in this state indefinitely (waited over 2 hours) without ever completing, timing out, or surfacing an error alert on either the iPhone or the Apple Watch. Troubleshooting Already Verified: Bundle ID Hierarchy: iOS App: com.company.appname Watch App: com.company.appname.watchkitapp Both targets share the exact same Development Team, signing certificate, and provisioning profiles. Developer Mode: Explicitly enabled and rebooted on the Apple Watch (Settings -> Privacy & Security -> Developer Mode). Also verified as enabled on the host iPhone. Connectivity & Cache: Cleared Xcode DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData). Performed hard reboots on both the iPhone and the Apple Watch to terminate any hung background sync daemons (installd / CoreDevice). Ensured both devices and the Mac are on the same Wi-Fi network with Bluetooth turned on. Questions: Under the current CoreDevice architecture, is installing local debug builds via the iPhone's stock Watch app still supported, or does it silently fail because the physical Apple Watch's UDID is not directly provisioned during an iOS-only build? Which subsystem in macOS Console.app (e.g., com.apple.dt.CoreDevice, com.apple.StreamingExtractor, or installd) is best for tracking the exact error/timeout code when the watch installation hangs? What is the currently recommended workflow to deploy and debug a paired watchOS target directly onto physical hardware? Any insights from the team or community would be greatly appreciated!