Where did the simulator "Slow animations" mode go? I can't find it in the Xcode 27 beta 2 "Device Hub". This feature is incredibly useful. I'm assuming it's a glitch that it's missing, or I'm just not looking in the right place.

After upgrading from Xcode 26.5 to Xcode 26.6, I noticed that the built-in Agents section has changed. My environment Xcode 26.6 (Build 17F113) macOS 26.5.2 (Build 25F84) 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. The Chat section still works normally. Comparison On the same Mac: Xcode 26.5 shows: Claude Agent Codex Get buttons Xcode 26.6 only shows MCP ("Allow external agents to use Xcode tools") and "Add an Agent...", with no built-in Agents. Things I have already tried Deleted all Xcode preferences Deleted ~/Library/Developer Deleted ~/Library/Application Support/Xcode Reinstalled Xcode 26.6 Signed out/in of Apple ID Verified Intelligence is enabled No change. Additional information The following directory is never created: ~/Library/Developer/Xcode/CodingAssistant Searching Xcode preferences also shows no Agent-related configuration. Question Is this an intentional change in Xcode 26.6, or is this a bug? If it's expected, how can I restore the built-in Agent catalog (Claude Agent / Codex)? Thanks!

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.

Never have this problem running in the first version of Xcode 27 until download the latest Xcode 27. At least "Fable" should be added in the dropdown to give a sense that it could be selected and be more careful (in dropdown only have "Sonnet", "Opus", "Sonnet+Opus" and more) I also submit Feedback request FB23973503 with screen capture & more Xcode Claude AI Investigation details

Nothing changed on my end, Pro subscription still active, but Xcode 26.5 (17F42) simply does not want to log into Codex anymore. It opens the OAuth flow and after finishing and closing the window, it still says "Not Signed In". Codex login works everywhere else, including the Codex app. What to do?

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

We need guidance regarding the Python runtime bundled with Apple Command Line Tools. Environment: macOS Tahoe 26.5.2 (25F84) Xcode 26.6 (17F113) Device type: Mac Command Line Tools Python path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/ Version confirmed locally with: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/bin/python3 --version Output: Python 3.9.6 Our vulnerability-management platform, Qualys, reports this Apple Command Line Tools Python runtime as vulnerable under QID 387170, referencing CVE-2022-4303 and CVE-2023-0286. The detection points to: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/Resources/Python.app My understanding is that this runtime is bundled and managed by Apple as part of Command Line Tools, and that manually replacing or modifying this framework is not a supported remediation path. Installing a separate standalone Python version also does not remediate the finding at this Apple-managed path. Could Apple or the community confirm the supported approach for this scenario? Specifically: Is Python 3.9.6 intentionally bundled with the current Command Line Tools release for this macOS/Xcode version? Has Apple applied security fixes or backports to this bundled Python runtime that are not reflected in the upstream Python version number? Is updating Command Line Tools/Xcode the only supported remediation method for this component? Is manually replacing or modifying the bundled Python framework unsupported? Is there any known mitigation or official guidance for vulnerability-management exceptions while waiting for an Apple-provided update? I have also filed this through Feedback Assistant: FB23893693. Any official Apple guidance or reference to existing documentation would be very helpful, as we need to provide an auditable response to our internal security and audit teams.

Summary On Xcode 26.6 (17F113) / Swift 6.2, a Debug build (-Onone) crashes at runtime when comparing UIScene.ActivationState inside a closure passed to Array.first(where:). The exact same code runs fine when built with optimizations (-O / Release). This looks like an -Onone code-generation (miscompile) bug rather than a logic error in the app. Environment Xcode: 26.6 (17F113) Toolchain: Swift 6.2 (Apple default toolchain) Optimization: SWIFT_OPTIMIZATION_LEVEL = -Onone (Debug scheme) Deployment target: [ iOS xx.x ] Run destination: [ Device / Simulator — model, OS version ] Configuration: also reproduces in a fresh checkout after Clean Build Folder + DerivedData wipe Steps to Reproduce Add the following to any app and call it early in the launch path (e.g. from an async context / Task during startup): import UIKit enum ScreenUtil { static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } // Crashes here in Debug (-Onone) on Xcode 26.6 (17F113) return scenes.first { $0.activationState == .foregroundActive } ?? scenes.first } } 2. Build and run with the Debug scheme (-Onone). 3. The app crashes as soon as keyScene is evaluated. Expected keyScene returns the foreground-active UIWindowScene (or the first scene), identically to the optimized build. Actual Immediate crash when the closure evaluates $0.activationState == .foregroundActive. UIScene.ActivationState is an Objective-C-imported (NSInteger-backed) enum, and the failure appears tied to how its value is handled under -Onone. The crash surfaces inside Swift concurrency resume plumbing because keyScene is reached from an async context at launch. Representative frame: (1) await resume partial function for partial apply forwarder for reabstraction thunk helper ... @isolated(any) @callee_guaranteed @async () -> (@out τ_0_0) ... -> ldr x0, [x22, #0x8] ; faults here br x0 ; preceding: bl swift_task_dealloc Reproducibility - Debug (-Onone): crashes 100% - Release (-O): works correctly Workaround Rewriting the closure comparison as an explicit loop avoids the crash: static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } for scene in scenes where scene.activationState == .foregroundActive { return scene } return scenes.first } Notes A sysdiagnose / crash log and a minimal sample project are attached via Feedback Assistant (FB[ number ]). Happy to provide additional details.

I'm on a Mac. I have Xcode installed but it's not running, nor is the Simulator. And yet Mac pops up an alert asking, ""Allow ServiceExtensio to find devices on local networks?" Creepy! No you can't scan my network. What gives? And why not tell me your real name?

Emoji handling (usually a sign of underlying Unicode bugs) is broken in Xcode 27, all betas: The issue doesn't exist in previous Xcode source editors. FB23969935

When will this be available? (Opencode + LMStudio + Qwen 3.6 27B) FB23978071

Or maybe I suck? Is there really no way with the new Xcode to take a simple screenshot from the device you're testing?You have to connect this Device Hub? An entirely separate app. And not only that, then you have to pair it, which maintains a live connection to the phone? Fine. Okay then. But now I can no longer test the microphone functions of my app because that shared session is interfering with it. Oh, well, I'll just disconnect the session then, right? Nope. The button to disconnect the session doesn't work. Device Hub thinks it's disconnected, but my phone still shows the blue sharing session icon in the upper left hand corner. The only way to stop that is to unpair the phone completely. So then every time I want to take a screenshot, I've got to do this pairing crap? I think I'll be running a second copy of Xcode 26 for quite a while just to use the screenshot button.

Super noob here 😅 is there a way to work with the “Xcode” development app on IOS. Any advice or input is welcome.

When connecting my iphone (14pro with iOS 17.2.1) with a paired apple watch (series 9 with OS 10.3), it is not showing up on the devices/simulators list in xcode 15.1. Beyond unpairing/repairing the watch, restarting either iphone or watch, connecting/disconnecting the iphone from the computer or deleting xcode and re-installing xcode, any other suggestions? Under the WatchApp field it shows "no eligible device connected", however, under the console the Apple Watch does appear. I have tried just about everything and can't get the watch to appear in Xcode. I am running all this on a MacBook Pro with Sonoma. Thanks for any assistance!

As of May 8th, 2026, after I upgraded to "codex-cli 0.129.0" via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.

Environment: macOS: Tahoe 26.4 Xcode: 26.5 ChatGPT account successfully authenticated Codex CLI installed and working Codex App installed and working Steps to reproduce: Install Xcode Codex/OpenAI component version where GPT-5.4 is the highest available model. Sign in with ChatGPT account. Confirm Codex works in Xcode. Update the OpenAI/Codex component in Xcode. Attempt to sign in again. Expected result: Xcode completes authentication and shows signed-in status. Actual result: Browser successfully completes authentication and displays "Signed in to Codex." Xcode remains in a sign-in loop or shows "Not Signed In." Authentication never completes. Additional observations: Codex CLI authentication succeeds. Codex App authentication succeeds. ChatGPT web/app access succeeds. Anthropic/Claude component updates continue to work normally in Xcode. Issue appears specific to the updated OpenAI/Codex Xcode component. Older component (GPT-5.4 maximum model available) authenticates successfully.

Has anybody gotten Device Hub to work with Apple TV yet? I've successfully paired a device, and can view its screen in Device Hub. But when I try to Build and Run an app, it gets stuck on "Installing Built products". Filed FB23964509 on this one.

I have a personal iOS project that I also compile for macOS with Catalyst. When built with Xcode 26.x, everything is linked correctly. When built with Xcode 27 betas, the following runtime error occurs: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleCallout Referenced from: <046ED276-F81A-31B4-82FF-6DC82E9041BC> /Applications/Photo Library.app/Contents/MacOS/Photo Library Expected in: <298B64F6-9BC0-3BFB-BE72-EBDC2BE0FF19> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit Any assistance? Thanks

Hi, I'm experiencing an issue with the Crashes tab in Xcode Organizer. Here are the steps to reproduce: Open Xcode Go to Window → Organizer Select my app Click the Crashes tab Select All Versions → More Versions The popup keeps showing a loading failure and never displays the data Xcode Version 26.4 (17E192)

In Xcode 27 Beta 4 (27A5228h), building a project that has a SwiftPM binary target (xcframework) linked directly from both an app target AND a framework target that is embedded in that app fails with "Multiple commands produce" errors. The same project and pbxproj builds successfully in Xcode 27 Beta 3 (27A5218g), so this is a regression introduced in Beta 4. Steps to Reproduce Create a new iOS App project. Add a Framework target (e.g. "SampleCommon") and embed it into the app. Add a SwiftPM dependency for a package that vends a binary xcframework product. Confirmed with airbnb/lottie-spm 4.6.1 (https://github.com/airbnb/lottie-spm). In "Frameworks, Libraries, and Embedded Content" of the app target, add the SwiftPM product (Lottie) with "Embed & Sign". In "Frameworks and Libraries" of the framework target, add the same SwiftPM product (Lottie). Build the app scheme for iOS Simulator. Expected result Build succeeds. The xcframework is embedded exactly once into the .app bundle. This is the behavior in Xcode 27 Beta 3 and Xcode 26. Actual result Build fails with: error: Unexpected duplicate tasks error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework/Lottie' error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework' Two Copy tasks are emitted for the same output path in the app target: Copy from Build/Products/Debug-iphonesimulator/PackageFrameworks/Lottie.framework Copy from SourcePackages/artifacts/lottie-spm/Lottie/Lottie.xcframework/ios-arm64_x86_64-simulator/Lottie.framework Additionally, an auto-generated target named "Lottiedynamic-product" emits duplicate MkDir / ProcessInfoPlistFile tasks for PackageFrameworks/Lottie.framework, which suggests the packaging path for binary xcframework products has been duplicated in Beta 4. Regression Xcode 27 Beta 3 (27A5218g): builds successfully Xcode 27 Beta 4 (27A5228h): fails with the above errors Xcode 26.x: builds successfully Minimal reproduction The issue reproduces on a 2-target Xcode project (app + framework) with airbnb/lottie-spm added and linked from both targetstory captures the smallest triggering diff: pattern1: app links Lottie only -> BUILD SUCCEEDED pattern2: framework links Lottie only -> BUILD SUCCEEDED pattern3: both app and framework link Lottie -> BUILD FAILED (only on Beta 4) Only the framework target's packageProductDependencies and Frameworks build phase entries differ between the succeeding and failing states. Workaround Link the SwiftPM binary product from only one target (either the app or the framework, not both). If only the framework tarl gets the framework transitively at runtime. Impact Any project that uses a SwiftPM binary xcframework and organizes code across multiple linked targets (a very common pattern for larger apps) is blocked from adopting Xcode 27 Beta 4. Environment Xcode 27.0 Beta 4 (27A5228h) macOS 26.5.2 Package: airbnb/lottie-spm 4.6.1 Destination: iOS Simulator (iPhone 17, latest)