It seems it's not possible anymore to view the output of the thinking process of an LLM. In Xcode 27 we were able to enlarge the output of each thinking phase, even though the UX wasn't actually great for doing this. Now, in Xcode 27.2 this is almost completely gone. There's only one line that seems to print the last line of the output. Do I miss something? Observing this content while the LLM is thinking is important, in order to be able to steer the LLM, or help it to find things, stop digressing into irrelevant topics, etc. While this was also not great, since enqueuing a message while the LLM is thinking has been queued – but the thinking phase has never been interrupted. So, enqueuing a message in order to steer the LLM was almost futile anyway. Nonetheless, I would expect newer Xcode versions to improve the user experience. I am unsure why this choice was made and included in a release. In my view, the AI chat and conversation behavior need improvement in several ways, though that is material for a few more posts.

Hi everyone, I downloaded Xcode 27.0 today because I need the Metal Toolchain for Unreal Engine 5.6 on my Mac. Xcode itself is installed and working, but Unreal is having issues because the Metal Toolchain doesn't seem to be installed. When I run: xcrun metal --version I get: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain I tried: sudo xcodebuild -downloadComponent MetalToolchain but it just stays on: Beginning asset download... If I cancel it, I get: xcodebuild: error: Download was cancelled. (Asset download for com.apple.MobileAsset.MetalToolchain ...) I've also run: xcodebuild -runFirstLaunch and installed the latest Command Line Tools for Xcode 27.0 through Software Update. xcrun --find metal does find the executable, but the actual Metal Toolchain appears to be missing. I'm mainly trying to get this working so I can use Unreal Engine 5.6. Has anyone had this issue with Xcode 27, or know the correct way to install the Metal Toolchain when xcodebuild -downloadComponent gets stuck at "Beginning asset download"? Thanks!

Hi, I’m encountering a consistent boot failure on iOS 27.3 simulator runtime with the new DeviceHub architecture in the latest Xcode. Environment Mac: Apple Silicon macOS version: [macOS Golden Gate 27.2] Xcode version: [27.2] Runtime: iOS 27.3 Simulator Runtime Architecture: DeviceHub (new CoreDevice stack, no old CoreSimulatorService fallback) Error Message

In a synthetic reproduction of a DeviceSupport-style backup on macOS 26.7.1 with Xcode 26.6 on Apple silicon, a source object has no com.apple.provenance, while a newly created destination object acquires that private extended attribute. File contents, modes, ACLs, and the source's other extended-attribute names can be verified independently. The backup acceptance contract requires a future restore to reproduce the original governed metadata. Is destination creation expected to add this attribute? For a faithful restore to a fresh APFS destination, should restoration software omit it, remove it after creation, preserve it, or allow macOS to regenerate it? Which supported API or documented postconditions establish restoration fidelity when the source lacked the attribute? Could the attribute affect DeviceSupport symbol usability or access behavior? We are seeking Apple-supported backup and restoration procedures and security postconditions, not an interpretation of private metadata. No real DeviceSupport files, raw private attribute values, production paths, credentials, datasets, or personal information are included.

With Xcode 27.1 (27A9275) and an iOS 27.0.1 (24A446) physical device, the UI-test runner starts, then fails about 60 seconds later with com.apple.dt.XCTest.XCTFuture, code 1000: “Timed out while enabling automation mode.” No business test method starts (0 methods started). What is the officially supported, targeted diagnostic entry point for this XCTest initialization boundary? Specifically: What supported configuration and logging level expose the runner sending an automation-mode RPC, device testmanagerd receiving it, testmanagerd sending a reply, and the runner receiving that reply? Which timestamps and session/request correlation fields associate those events across the runner and testmanagerd? Can collection be limited to one device, one test attempt, these processes, and a short time window? What minimal text fields are necessary? Can unrelated-app data, screenshots, audio/video, runner environment values, credentials, and personal information be excluded? Please specify any required setup and how to disable or remove it afterward. We need a supported entry point and a precise, minimal privacy scope before changing configuration or collecting broader diagnostics. A general CoreDevice or sysdiagnose workflow alone does not establish that these RPC send/receive events will be recorded.

Versions under discussion: Apple Command Line Tools: 26.5.0.0.1777544298 LLDB: 2100.0.17.108 Components: lldb, LLDB.framework, debugserver I am seeking documented capability boundaries for observing an owned test process on macOS, rather than reporting a reproduced defect. Earliest observation point For a process launched under LLDB/debugserver, what is the earliest guaranteed stopped point? Is there a supported workflow that establishes observation before dyld and image initializers execute, or is observation necessarily established later? Please distinguish an exec stop, a stop at main, and images already present at the first stop. Event completeness and loss detection Are image-load/unload notifications a complete, ordered event stream, including shared-cache/preexisting images? Can library-initializer execution be observed with equivalent guarantees? What documented sequence, overflow, or dropped-event indication lets a client detect an incomplete observation, rather than treating a snapshot or lack of events as proof of completeness? Process ownership and reaping In launch versus attach modes, which process actually creates the target and which process consumes its terminal wait status? What documented behavior applies if the LLDB frontend or debugserver exits unexpectedly? In particular, how can a controller distinguish a termination signal being sent from the target actually being reaped, without competing with another wait-status consumer? Pointers to documentation or source/build references matching these components would be appreciated. If any of these guarantees are unsupported, an explicit limitation would also answer the question.

It annoys me that Xcode keeps downloading Simulators automatically, even though I haven't asked for them. Under Settings > Components > Other Installed Platforms I see iOS Simulator iOS 18.0 uptil 18.5. These are eating space in /Library/Developer/CoreSimulator/Caches/dyld/25E253. Is there a way to prevent these automatic downloads?

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.

On Xcode 26 and earlier versions, two-finger touches were possible on Simulator by holding down the option key. On Xcode 27 with Device Hub, this is no longer possible. While the trackpad can be used for pinch and rotate gestures, two-finger taps and two-finger pans are not possible. This is a major regression that renders our app basically unusable in Device Hub. We rely on two-finger tap and pan gestures to navigate our 3D models. Not being able to do this in Device Hub and in Xcode previews would be a huge loss. Is this actually no longer supported or am I missing something?

Does Xcode 27 or TestFlight support installing a watch-only beta on an Apple Watch For Your Kids device? I want to test my watch only standalone app on my kids apple watch as that is the only device I have. Is it possible to use that watch for testing standalone apple watch application. The watch is setup as kids watch on my iphone.

I just downloaded and installed the final released Xcode 27.2, and it queued up, downloaded, and installed not one but two simulator SDKs. Why is that?

I just saw the following in the Xcode 27 release notes: Xcode can now serve asset packs to your app while debugging on devices by setting a Background Asset Packs folder in the Run scheme action’s Options tab. (165230494) And sure enough, the option is there. But what do I need to point this to? I tried everything: the path to the built .aar asset pack the path to the .json manifest file the path to the download-manifest.json (for self-hosted asset packs) the path to the directory that actually contains the assets (as also referenced by the manifest file) the path to the directory that contains the manifest file and the asset directory. Nothing works. I always get the same errors on the console: Checking for updates failed: DecodingError.dataCorrupted: Data was corrupted. Debug description: The given data was not valid JSON.. Underlying error: Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected end of file" UserInfo={NSDebugDescription=Unexpected end of file} The asset pack with the ID “MyID” couldn’t be looked up: DecodingError.dataCorrupted: Data was corrupted. Debug description: The given data was not valid JSON.. Underlying error: Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected end of file" UserInfo={NSDebugDescription=Unexpected end of file} The manifest couldn’t be refreshed: DecodingError.dataCorrupted: Data was corrupted. Debug description: The given data was not valid JSON.. Underlying error: Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected end of file" UserInfo={NSDebugDescription=Unexpected end of file} I'm testing on a physical iPhone. Any advice would be appreciated!

Before Device Hub (27.0), you could drag a photo onto an iOS Simulator window and the photo would be added to that simulated device's Photos library. This does not work in Device Hub (27.0). Bummer if your app has to do with photos.

I am looking for current Apple guidance on installing an independently developed, Watch-only watchOS app on an Apple Watch configured with Apple Watch For Your Kids / Family Setup, without changing its existing pairing, Apple Account or Family Setup configuration. Configuration: Apple Watch SE 3 (GPS + Cellular). watchOS 26.6. Managing iPhone running iOS 26.6.2. Xcode 27.1. Family Setup user is a child under 13. The app operates independently of a companion iPhone app. Its conventional-device version has been installed and tested on another, conventionally paired Watch. The isolated variant builds for watchOS with signing disabled, but has not been signed or installed on this Family Setup Watch. A read-only development-device inventory did not identify the Family Setup Watch. We have not changed its settings or attempted installation on it. I found this January 2022 answer from an Apple Frameworks Engineer stating that Family Setup Watches were not supported for Xcode development: https://developer.apple.com/forums/thread/698831 I also reviewed the later discussion about missing Developer Mode, which contains similar reports but no supported installation procedure: https://developer.apple.com/forums/thread/741161 Does the earlier limitation still apply to the configuration above? If direct Xcode development deployment is now supported, what is the exact workflow for discovering the Watch as a development destination, registering it for development, enabling Developer Mode where applicable, and provisioning/installing a Watch-only app while preserving Family Setup? Please identify required trust prompts, restarts or settings changes. If it is supported but the device is undiscoverable, which non-destructive diagnostics should be collected first? If it remains unsupported, is there another Apple-supported registered-device testing route that preserves Family Setup, or is a reviewed standalone Watch App Store release required? TestFlight is not an eligible route for this child's use under Apple's published age restriction. We are not seeking an age/account workaround, private APIs, or instructions to unpair, erase or convert the Watch to conventional pairing. Please link the applicable documentation or explicitly confirm the current platform limitation. This question concerns development installation only.

I have a personal company app for internal use only. Under Xcode26 if would build and I could distrubte it no problem. I updated to Xcode27. Made some minor changes to some of the Text that is displayed in the app and now I can not get the Build function to work. It is grayed out completly.

Environment Mac mini with Apple M4 macOS 26.7.2 (build 25G332) Xcode 26.6 CoreSimulatorService 1051.55 External USB SSD formatted as APFS, mounted read/write, with ownership enabled Source simulator: iPhone 17 Pro running iOS 26.5, shut down Issue I am attempting to preserve a shutdown simulator using the supported simctl clone operation, with the destination CoreSimulator device set located on an external APFS SSD. Command form: xcrun simctl clone <source-UDID> "<preserved-device-name>" "/Volumes/<external-volume>/<device-set-path>" The destination directory is owned by the logged-in user and has ordinary writable POSIX permissions. The volume is mounted read/write with ownership enabled. No restrictive ACL entries or file flags were found on the destination directories. Observed result simctl reports: NSPOSIXErrorDomain Code=22: Device was allocated but was stuck in creation state. CoreSimulator records the preceding data-clone failure as: NSCocoaErrorDomain Code=513 Underlying NSPOSIXErrorDomain Code=1 Operation not permitted The temporary destination simulator entered the Creating state and CoreSimulator automatically rolled it back. At the same timestamp, unified logging attributes the rejected external-volume write to com.apple.CoreSimulator.CoreSimulatorService, rather than to simctl. The TCC and sandbox sequence shows: A check for kTCCServiceSystemPolicyAllFiles. A check for kTCCServiceSystemPolicyRemovableVolumes. Removable-volume access requiring a TCC prompt. Prompting being denied because the requesting CoreSimulatorService is an Apple platform binary. Launch Services being unable to create an application record for the CoreSimulatorService XPC bundle. No consent prompt was displayed. CoreSimulatorService's Info.plist contains an NSRemovableVolumesUsageDescription string specifically describing access when a simulator device set is configured on external storage. This is a development-tool/service issue; no application project or third-party framework is involved. Expected result CoreSimulatorService should either present or arrange the supported removable-volume consent workflow, or use a documented user-controlled Files & Folders permission that allows an external device set. Questions What is the supported procedure for granting SystemPolicyRemovableVolumes access to com.apple.CoreSimulator.CoreSimulatorService when the Apple platform XPC service cannot display the consent prompt? Should CoreSimulatorService appear in System Settings > Privacy & Security > Files & Folders with a Removable Volumes switch? Is cloning into an external APFS CoreSimulator device set supported with Xcode 26.6 on macOS 26.7.2? Is there a supported way to initiate the operation so consent is attributed to Xcode or another user-facing Apple process? Is the Launch Services application-record failure expected, or is this a known CoreSimulator/TCC issue with an available fix? I have not edited the TCC database, reset privacy decisions, granted broad Full Disk Access, disabled security controls, changed permissions, removed extended attributes, manually copied protected simulator records, or retried using an unsupported filesystem workaround. I can provide focused, redacted CoreSimulator, sandboxd, and tccd excerpts privately if an Apple engineer requests them.

I am seeking a supported public diagnostic or prerequisite for a standalone Siri UI test. Feedback: FB25377231. Developer Technical Support directed this question to the forums. Environment: Mac mini (2024), Apple M4, 32 GB, native arm64 macOS 26.7.2 (25G332) Xcode 26.6 (17F113), iOS Simulator SDK 26.5 iPhone 17 Pro Simulator; the original test's xcresult identifies iOS 26.5 (23F73) Classic Siri, en-GB A small test-host project compiled and ran one selected XCTest case. Its core public API call was: XCUIDevice.shared.siriService.activate( voiceRecognitionText: "What is two plus two?" )The exact recognition text reached the testing activation path, but SpringBoard logged: No network. Not starting the request for SASRequestSourceTestingNo arithmetic answer appeared during the configured 30-second wait. This was observed once; a repeatable frequency is not established. This reproducer has no product app, app-specific Siri intent, or CarPlay integration. In the original Simulator test runner, the first unconstrained NWPathMonitor callback was satisfied, with en0/wiredEthernet, but supportsIPv4, supportsIPv6, and supportsDNS were all false. Default-route SCNetworkReachability samples reported reachable. A separate, later diagnostic used the same simulated device with the installed iOS 26.5 (23F77) runtime. Identical public Foundation/Network helpers on the host and Simulator each issued one URLSession HEAD request to: https://www.apple.com/library/test/success.html Both received HTTP 200. The Simulator helper's initial path callback again reported satisfied with IPv4/IPv6/DNS capability flags false. This proves a response only for that helper/API/URL/time. It does not prove that the flags stayed false, that a fresh DNS lookup occurred, that Siri endpoints were reachable, or that the earlier 23F73 failure had the same cause. A setup confounder may matter: additional iOS platform support, including runtime 23F77, was installed while the original 23F73 Simulator remained booted. The arithmetic test ran afterward but still reported 23F73 in xcresult. The later HTTPS control ran separately on 23F77. There has been no further Siri activation. What supported Simulator/XCUISiriService prerequisite or public diagnostic can distinguish the cause of this specific request-start refusal? Is it expected for this configuration, a known issue, or evidence of an unmet prerequisite? The complete original results and a minimal test-host project are retained. Selected evidence and source are already attached to FB25377231; the same material can be supplied privately to DTS. I am seeking a supported approach rather than private preferences, service overrides, or repeated test requests.

My paired Apple Watch never shows up in Xcode, so the Developer Mode toggle never appears on the watch (Settings > Privacy & Security). The paired iPhone works perfectly, and I build and install to it every day. Setup Mac: macOS Tahoe 26.6, Xcode 27.0 (watchOS 27 SDK and platform installed) iPhone 15 Pro Max, Developer Mode ON, shows as connected in xcrun devicectl list devices over USB Apple Watch on watchOS 26.x, passcode set, unlocked, on wrist Free personal team (also tried a second free Apple ID; both are signed in to Xcode) Symptom xcrun devicectl list devices lists the iPhone and an iPad, never the watch Devices and Simulators shows no watch under the iPhone No ~/Library/Developer/Xcode/watchOS DeviceSupport folder has ever been created Unified log on the Mac shows no CoreDevice / remotepairing activity for the watch at all. It looks like the Mac never hears from it. Network No router. The Mac gets internet from an iPad over USB and re-shares it over Wi-Fi (macOS Internet Sharing). iPhone and watch are joined to that network. I also tried the Mac and phone on the iPhone's Personal Hotspot. VPN is off and the firewall is off. Already tried, no change Unpaired the watch and paired again (restored from backup) iPhone: Settings > Developer > Clear Trusted Computers, re-trusted, xcrun devicectl manage pair Accepted the "Trust this computer" prompt on the watch after a restart iPhone Developer Mode off, restart, on, restart Signed out of and back in to Xcode accounts; accepted the latest agreements Restarted the Mac, iPhone and watch; waited 5+ minutes with the Devices window open each time Bluetooth and Wi-Fi on everywhere; watch and Mac on the same Wi-Fi Is there a way to force Xcode to discover the watch through the iPhone, or a log predicate that shows why the watch is never offered? Any pointers appreciated.

It doesn't show any files, only warning or errors for me. Same behavior with @

Hi everyone, I'm experiencing an issue with the OpenAI integration in Xcode 26.3. When I navigate to Xcode → Settings → Intelligence → OpenAI, Codex is marked as "Unavailable", and I cannot download or enable it. My configuration: macOS: 26.7.2 Xcode: 26.3 Apple Intelligence: Enabled ChatGPT Plus subscription: Active ChatGPT in Xcode: Available and working Claude integration: Available and can be downloaded normally Codex: Unavailable I've attached a screenshot showing the issue. I'm wondering why Codex is unavailable while Claude works without any problems, despite Apple Intelligence being enabled. Has anyone encountered the same issue? Could this be related to regional restrictions, compatibility requirements, or an Xcode bug? Any help or suggestions would be appreciated. Thanks!