undle/Application/D1E61F20-B0C9-4B21-8152-E4ABFA0979F2/YTVIP.app': Unspecified User Info: { DVTErrorCreationDateKey = "2026-03-04 03:05:58 +0000"; DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = "Cannot launch '/private/var/containers/Bundle/Application/D1E61F20-B0C9-4B21-8152-E4ABFA0979F2/YTVIP.app': Unspecified"; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_identifier" = d13ba5c93db94daa55ae177b1822998b675939a8; "device_model" = "iPhone7,2"; "device_osBuild" = "12.5.3 (16H41)"; "device_osBuild_monotonic" = 1607004100; "device_os_variant" = 1; "device_platform" = "com.apple.platform.iphoneos"; "device_platform_family" = 2; "device_reality" = 1; "device_thinningType" = "iPhone7,2"; "device_transport" = 1; "launchSession_schemeCommand" = Run; "launchSession_schemeCommand_enum" = 1; "launchSession_targetArch" = arm64; "launchSession_targetArch_enum" = 6; "operation_duration_ms" = 12938; "operation_errorCode" = 3; "operation_errorDomain" = IDEDebugSessionErrorDomain; "operation_errorWorker" = DBGLLDBLauncher; "operation_error_reportable" = 1; "operation_name" = IDEiPhoneRunOperationWorkerGroup; "param_consoleMode" = 1; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 5; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_MTE_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_mtc_enable" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 3; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 1; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 0; "param_launcher_substyle" = 0; "param_lldbVersion_component_idx_1" = 0; "param_lldbVersion_monotonic" = 170302360103; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos26.2"; "sdk_osVersion" = "26.2"; "sdk_platformID" = 2; "sdk_variant" = iphoneos; "sdk_version_monotonic" = 2302005700; } System Information macOS Version 26.3 (Build 25D125) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-04T11:05:58+08:00

Here's the text of FB22001359 I've just submitted: Xcode 26 changed the behavior of the Inspectors pane (which hopefully is a bug and not an intended behavior). Now, if I close (or open) the Inspectors pane in a window tab, it closes (or opens) the Inspectors pane in ALL tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years. By way of example: In a window tab that contains a .xib, I always want the Inspectors pane to be open. While in the window tabs that contain code files, I want the Inspectors pane to be closed. (Sometimes I do open it in certain window tabs, when needed). Before Xcode 26, the Inspectors pane was open or closed in each individual tab as the user desired. Now, if I close the Inspectors pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to open the Inspectors pane AGAIN. But then when I go back to a code window tab, I have to CLOSE the Inspectors pane there (because it became open globally). And have to do this endlessly every day. WHY??? Please restore the normal, pre-26 behavior of the Inspectors pane. That is, the Inspectors pane should remain open or closed as PER INDIVIDUAL WINDOW TAB, not globally. Thank you for your attention to this important issue!

Here's the text of FB22008758 I've just submitted: Xcode 26 changed the behavior of the Navigators pane (which hopefully is a bug and not an intended behavior). in Xcode 26, if I close (or open) the Navigators pane in a window tab, it closes (or opens) the Navigators pane in ALL window tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years (I've been using Xcode since 2006). By way of example: In a window tab that contains a .xib, I prefer the Navigators pane to be closed. While in all other window tabs (that contain code files and other items), I want the Navigators pane to be always displayed. Before Xcode 26, the Navigators pane was open or closed in each individual window tab as the user desired. But in Xcode 26, if I close the Navigators pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to close the Navigators pane AGAIN. But then when I go back to a code window tab, I have to OPEN the Navigators pane there (because it became closed globally). And have to do this endlessly every day. WHY??? Please restore the normal, pre-26 behavior of the Navigators pane. That is, the Navigators pane should remain open or closed as PER INDIVIDUAL WINDOW TAB, not globally. Thank you for your attention to this important issue!

Xcode 16 and 26 changes in painful way how the Tab key works during autocomplete. Previously, pressing Tab would extend the typed text up to the word match. For example, we have two classes: NSViewController and NSViewCoordinator BEFORE, typing: "NSV" + Tab used to complete to NSViewCo Now, in Xcode 26, pressing Tab just use the first suggestion. Stupidly. Especially when you want DispatchQueue and it gaves you DispatchSemaphore… That is very inconvenient because very often I want just see all possible cases with some prefix...without need of typing all prefix manually. How to restore the previous behavior? How to do autocomplete word-by-word?

Hi, I’m facing a consistent simulator boot issue that appears to start after iOS 18.2 simulator runtimes and persists in 18.6, 26.1, and 26.2. Observed behavior iOS 18.2 simulator works fine iOS 18.6 simulator does NOT boot iOS 26.1 / 26.2 simulators do NOT boot Tried everything reinstall/clear cache and all and event formatted the system Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding macOS: Sequoia Xcode: 26.1, 26.2 Machine: Apple Silicon Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = "2025-12-26 02:19:27 +0000"; IDERunOperationFailingWorker = "_IDEInstalliP.honeSimulatorWorker", Session = "com apple CoreSimulator.SimDevice CCDECA56-4A59-491B-A830-0F3928FCD957"; } Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding Domain: com.apple.SimLaunchHostService.RequestError Code: 4 Event Metadata: com.apple. dt. DERunOperationWorkerFinished : { "device_identifier" = "CCDECAE6-4A59-491B-A830-0E3928FCD957"; "device_model" = "iPhone18, 1"; "device_osBuild" = "26.1 (23B86)"; "device_osBuild_monotonic" = 2301008600; "device_os_variant" = 1; "device_platform" = "com apple.platform.iohonesimulator"; "device_platform_family" = 2; "device_reality" = 2; "device_thinningType" = "iPhone18,1"; "device_transport" = 4; "launchSession_schemeCommand" = Run; "launchSession_schemeCommand_enum" = 1; "launchSession_targetArch" = arm64; "launchSession_targetArch_enum" = 6; "operation_duration_ms" = 1183; "operation_errorCode" = 4; "operation_errorDomain" = NSPOSIXErrorDomain; "operation_errorWorker" = "_IDEInstalliPhoneSimulatorWorker"; "operation_error_reportable" = 1; "operation_name" = IDERunOperationWorkerGroup; "param_consoleMode" = 1; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com apple platform Please help on this as it got stuck. Thanks

Steps to reproduce: Open Xcode 26.3 → Settings → Intelligence → Claude sign-in Click the sign-in button — spinner begins, never completes An email the arrives with a magic link. The magic link opened a browser page which displayed a 6-digit verification code with instructions reading "enter this verification code where you first tried to sign in" — i.e. back in Xcode. However, Xcode was showing only an endless spinner with no code entry field anywhere in the UI. This is the core bug. I did since manage to complete authentication sign-in through a second browser verification field that eventually appeared after about 10 minutes and did get signed in, but the Claude Intelligence agent still returns "Your request could not be completed" even after successful sign-in and a full Xcode restart. Prior to this bug starting at 10 am on February 19 I had been using the intelligence agent successfully for about a week. Anthropic did have some sort of event on their system around February 18/19 so maybe this has been a result of that. I have notified Anthropic support and Apple Feedback Assistant. Does anybody have a workaround until either anthropic or Apple get back to me?

Hi, I recently updated my Mac to macOS Sequoia 15.7.2, and then updated my Xcode packages right afterward. However, when I try to open Xcode, I receive the message: “You can’t open the application because it is being updated.” I contacted Apple Developer Support (software) by phone and went through their troubleshooting steps, but the issue persists. They confirmed that everything appears fine on their end. In System Settings, both macOS and Xcode show as fully up to date. However, when I manually check in the App Store, it says Xcode needs to be updated. When I press Update, I get the following error: “Xcode could not be installed. Please try again later.” I’m fairly new to Xcode, but it seems there may be an incomplete update or verification loop preventing the installation from finishing properly. Could you please advise on how to resolve this so I can open Xcode again?

Hello Apple Developer Community, I'm seeing a persistent crash in my iOS app reported via Firebase Crashlytics. The issue only started appearing on devices running iOS 26.3.0 and above (the crash does not occur on lower iOS versions, and it's unrelated to my app's version number). Key points: My app does NOT use any Text-to-Speech (TTS) features whatsoever. No AVSpeechSynthesizer, no Speech framework, no related APIs called from our code. My app is primarily written in Objective-C (with some Swift components possibly via dependencies). The crash stack is entirely within Apple's private TextToSpeech framework, specifically in ausdk::BufferAllocator::instance(). I suspect it might be indirectly triggered by a third-party ad SDK (e.g., Google Mobile Ads, AppLovin, etc.) that could be loading or interacting with accessibility features in the background — but this is just a hypothesis, as I have no direct evidence yet. Here is one representative crash log: Crashed: com.apple.root.user-initiated-qos.cooperative 0 TextToSpeech 0x6bb00 ausdk::BufferAllocator::instance() + 99800 1 TextToSpeech 0xf8c60 ausdk::BufferAllocator::instance() + 677688 2 TextToSpeech 0xf8c60 ausdk::BufferAllocator::instance() + 677688 3 TextToSpeech 0x1a0b9c ausdk::BufferAllocator::instance() + 1365620 4 libswift_Concurrency.dylib 0x628b4 swift::runJobInEstablishedExecutorContext(swift::Job*) + 288 5 libswift_Concurrency.dylib 0x63d28 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) + 156 6 libdispatch.dylib 0x13f48 _dispatch_root_queue_drain + 364 7 libdispatch.dylib 0x146fc _dispatch_worker_thread2 + 180 8 libsystem_pthread.dylib 0x137c _pthread_wqthread + 232 9 libsystem_pthread.dylib 0x8c0 start_wqthread + 8 The crash occurs on a background cooperative queue (Swift Concurrency). Questions: Has anyone else seen crashes inside ausdk::BufferAllocator::instance() in TextToSpeech on iOS 26.3.0+ even without using TTS in their app? Could a third-party ad SDK be causing the TextToSpeech framework to load unexpectedly (e.g., via accessibility preloading)? Is this a known bug in iOS 26's Spoken Content / Speak Selection features? Any workarounds or fixes from Apple? Any insights, similar reports (especially from Objective-C based apps), or advice would be greatly appreciated! Thanks!

Hello, I've been searching online for ways to remedy this issue for the past 3 days and this is my last resort. The Issue Build on device fails to connect to the device. The prompt will permanently be stuck loading in that screen. Finder is able to connect to the device, just that Xcode is unable to. Xcode does prompt for passcode on the device, and I have entered it accordingly. I note that i AM on VPN, but even disabling VPN and turning off Wifi does not fix the issue. This was working until several days ago. Not sure what the issue is. Fixes Attempted Tried with a different cable, and USB ports Tried with different devices (multiple devices both iPad and iPhone has the same issue) Turn Off and On developer mode on devices. Clear Trusted Computers on devices. Updating both devices to the latest iOS version. Quitting Xcode Clearing derived cache Restarting Macbook Updating to the latest iOS version on Macbook Reinstalling Xcode toggling signing certificates I was trying other fixes like "pkill usbmuxd", but since I am on corporate hardware, i will be required to escalate it if i require sudo permissions. Is anyone able to provide a concrete solution or explanation why this happens?

I have been getting the following error intermittently (once it happens, then its consistent) when I try to build my app Showing Recent Errors Only Unable to resolve build file: BuildFile<b11862f281fd8c8287d499b4f0922a9c61c95323d2196ba877ed344a02baffbb> (The workspace has a reference to a missing target with GUID '0c7e19da3805e0a412c717704d4549fc25560b498add930cbef9623bd9afb53a') There have been no changes to my project (git status is clean). I have tried cleaning DerivedData as well, but it did not help. How am I supposed to figure out from the GUID what is it that xcode is trying to find?

As stated in the title, my device is M4 macmini, running macOS 26, with Xcode version 26.1. The error message is ": retrying debugserver without secure proxy due to error: Error Domain=com.apple.dtdevicekit Code=811 UserInfo={NSUnderlyingError=0xc42b07930 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653150 UserInfo={MobileDeviceErrorCode=, com.apple.dtdevicekit.stacktrace=, DVTRadarComponentKey=261622, NSLocalizedDescription=}}, NSLocalizedRecoverySuggestion=Please check your connection to your device., DVTRadarComponentKey=261622, NSLocalizedDescription=}, the official documentation does state that debugging is supported for devices running at least iOS 15. However, my 2019 MacBook Pro, with macOS 15.7.2 and Xcode 26.1 installed, can debug iOS 12 devices normally. The product manager has asked me to identify the issue, but I am at a loss. If anyone can provide a solution or confirm that support for iOS 12 is no longer available, we would be very grateful. Additionally, iOS 13 devices can all be debugged normally

Hi there, I am trying to use the agentic coding with the new Xcode update, however the "Intelligence" tab is not coming up on the left hand side of my Xcode settings. I've ensured I have macOS greater than 26, I've got Apple Intelligence and Siri enabled. I've shut down and restarted Xcode and my computer. Still, the option is not available. Can anyone help?

Hi, In Xcode 26.2, editor tabs adapt their width to the number of pinned tabs: In Xcode 26.3, editor tabs have a minimal width, after which the row of tabs becomes horizontally scrollable: Notice how less tabs are visible at a time on Xcode 26.3 (second image). Yet, there is enough horizontal space to accommodate more, as shown on Xcode 26.2 (first image). This is a UX regression. How can I revert back to 26.2 tab sizing behavior? Thank you.

I have two apps; one is a subset of functionality of the other. The smaller app has about 170 Swift files. The larger app has these files plus about 120 more. So I would expect the larger app to take around twice as long to build. Instead, the smaller app takes less than a minute to build while the larger app takes over 13 minutes to build; to be exact, it takes 15.3 times longer. While reviewing the build report, I noticed that the smaller app compiles the Swift files in batches, with each batch taking around 10 seconds, but with up to 17 batches running at once. In contrast, the larger app compiles all 290 Swift files in one giant batch, so apparently there is no multithreading of the Swift compilation (see screen shots below). The difference in the number of batches the smaller app compiles at once roughly corresponds to the difference in overall build time. Is there a build setting I can change to make the larger app compile Swift files in multiple smaller batches as the smaller app is doing? I checked SWIFT_COMPILATION_MODE and it's the same in both apps (Incremental for debugging and Whole Module for release) but I don't know what other settings I should check.

I decided to try out XCode 26.2s new AI abilities but I only get a "Your request couldn't be completed". When clicking the details button I get see this error: InferenceError::unspecifiedUnderlyingError::Error(message: "Unknown parameter: 'tool_call_outputs'.", type: "invalid_request_error", code: Optional("unknown_parameter"), privacyPassRedemptionResponse: nil, userFacingLocalizedErrorMessage: nil) How do I fix that?

Have a peculiar problem I'm not able to solve. Working on an app with a mapview in the max zoomed out globe level. For some reason this morning Xcode froze/crashed when I was working and I had to force quit to get it back up. Then a new issue of graphical artifacts on the space section of the Mapview showed up. This Tuesday has now been spent in full on trying to solve this to no avail. I created a new project for iOS/iPadOS and added a similar map implementation. It works fine. I used Claude to help me after a few reinstalls of Xcode with this. I asked claude to summarize - this is what has been done: Claude generative AI summary starts here---------- Here's a complete summary of everything attempted: The Problem SwiftUI tvOS app with MapKit globe view showing severe rendering artifacts — corrupted pixels surrounding the globe. Started after Xcode crashed while the tvOS simulator was actively running. iOS simulator, macOS Maps app, and all native apps work perfectly. Only tvOS simulator MapKit is affected. Hardware Confirmed Fine Geekbench 6 Metal GPU score: 124,666 (normal for M1 Max) Apple Diagnostics (Apple Silicon method): No issues found macOS Maps globe renders perfectly Everything That Was Attempted Simulator resets: Erased all simulator content and settings Created brand new simulator devices Deleted derived data Killed CoreSimulator service Runtime reinstalls: Removed and reinstalled tvOS platform runtime multiple times Tested on Xcode 26.3 and 26.4 beta — same issue on both Installed fresh tvOS runtime after full Xcode reinstall Cache clearing: ~/Library/Caches/com.apple.CoreSimulator ~/Library/Saved Application State/com.apple.iphonesimulator.savedState All Metal shader caches in /private/var/folders/ including: com.apple.CoreSimulator.SimRenderingServices.SimMetalHost com.apple.CoreSimulator.SimRenderingServices.SimRenderServer com.apple.CoreSimulator.CoreSimulatorService com.apple.iphonesimulator com.apple.dt.Xcode com.apple.dt.xcodebuild com.apple.CoreSimulator.simctl ~/Library/Developer/Xcode/XcodeToMetalToolchainIndexMapping.plist ~/Library/Developer/Xcode/SDKToSimulatorIndexMapping.plist ~/Library/Developer/Xcode/DerivedData Full Xcode reinstall: Deleted Xcode completely Removed ~/Library/Developer Removed all Xcode-related caches and preferences Fresh install from Mac App Store APFS simulator volume cleanup (required disabling SIP): Discovered 138GB of orphaned APFS simulator volumes in /Library/Developer/CoreSimulator/Volumes/ that were protected by SIP and couldn't be deleted normally These volumes were left in a corrupted/limbo state from the original Xcode crash Temporarily disabled SIP via Recovery Mode Successfully deleted all orphaned volumes Re-enabled SIP Reinstalled fresh tvOS runtime Metal Toolchain: Found three leftover Metal Toolchains (17A324, 17A5241c, 17A5295f) in Xcode settings Cleared toolchain index mapping file Reinstalled fresh Metal Toolchain with new tvOS runtime Current State Fresh Xcode installation Fresh tvOS runtime All simulator volumes cleared SIP re-enabled Issue still persists What Has NOT Been Checked /Library/Developer/CoreSimulator/Cryptex /Library/Developer/CoreSimulator/Images /Library/Developer/CoreSimulator/Profiles Conclusion This is almost certainly a bug triggered by the hard Xcode crash corrupting something at a level that has survived complete reinstallation of Xcode and all simulator components. The corruption is somewhere in a system-level component that normal developer tools cannot reach. Requires Apple Developer Technical Support or escalation via Feedback Assistant with the full timeline and screenshots. For Apple's reference: Machine: MacBook Pro M1 Max Xcode: 26.3 / 26.4 beta (both affected) Started: After hard Xcode crash while tvOS simulator was actively rendering MapKit globe Affected: tvOS simulator MapKit globe only Not affected: iOS simulator, macOS Maps, all native apps ----------(Claude generative AI summary ends here) ----------- Anyone seen this before? Absolutely wild. Can't think of more things to try. Been eyeing a new Macbook for a while. Strange coincidence that the new M5 Macbook Pros dropped today :D But in sum it does not seem like a GPU issue since the same rendering works on the iOS sim. Thanks!

I was having an issue with the new xcode and was forced to to go back to to Xcode 26.0.1. ( I need iOS simulators for mobile testing and as Developer I know is using this version with no problems). I've always install xcode from the app store with no issue so installing from Apple Dev was something new for me so So I did the following downloaded Xcode 26.0.1 Extracted it from Xzip added the extracted Xcode version to the applications folder click the Xcode icon Expected result I was expecting to see text i could install Xcode version Actual Result Xcode opened Asked me to create a project When project was created I saw Question. What did I do wrong? How do I fix it?

Hi, I submitted my Swift Student Challenge 2026 app and I'm worried about a build error I got when testing. I have both PlateClassifier_2.mlmodel and PlateClassifier_2.mlmodelc in my Sources folder. Only the .mlmodelc is listed in my Package.swift resources. When building I got: PlateClassifier_2.mlmodel: No predominant language detected. Set COREML_CODEGEN_LANGUAGE to preferred language. Build failed — 1 error Will judges hit this same error? Does having an unlisted .mlmodel alongside the .mlmodelc cause a hard build failure on other machines too, or is this specific to my setup (Xcode 26.2 beta, building to physical device)? Will this get me instantly disqualified? Any help appreciated.

I am using official MCP SDK. According to official guide, Servers MUST provide structured results that conform to this schema. https://modelcontextprotocol.io/specification/draft/server/tools#output-schema I could see output schema defined, but result have no structured content. Current output schema: { name: "XcodeListWindows", title: "List Windows", description: "Lists the current Xcode windows and their workspace information", inputSchema: { type: "object", properties: { }, required: [ ], }, outputSchema: { type: "object", properties: { message: { description: "Description of all open Xcode windows", type: "string", }, }, required: [ "message", ], }, } Current response: { "result": { "content": [ { type: "text", text: "{\"message\":\"* tabIdentifier: windowtab1, workspacePath: \\xxx\\n* tabIdentifier: windowtab2, workspacePath: \\xxx\\n\"}", }, ] } } Expected: { "result": { "content": [ { type: "text", text: "{\"message\":\"* tabIdentifier: windowtab1, workspacePath: \\xxx\\n* tabIdentifier: windowtab2, workspacePath: \\xxx\\n\"}", }, ], "structuredContent": { "message": "* tabIdentifier: windowtab1, workspacePath: \\xxx\\n* tabIdentifier: windowtab2, workspacePath: \\xxx\\n", } } }

Looking for any guidance on how to duplicate the Display Settings under "Display & Brightness" more specifically the Display Zoom.