Currently it's Sonnet 4.5. I know that 4.6 is out.

Will I be able to download and run Xcode 26.3 on a new MacBook Air with an M5 chip? If yes, what memory size is recommended? 16, 24 or 32 GB ?

I have three rogue iOS simulators, how to correctly delete them and reclaim the disk space? These img files are costing me 18gb of storage.

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

I've recently updated to Xcode 26.3 and I can't download any iOS Simulator Runtime from 26.2 to 18.0, every download gives me: Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2026-03-03 16:14:50 +0000"; } -- Download failed. Domain: DVTDownloadableErrorDomain Code: 41 -- System Information macOS Version 26.4 (Build 25E5218f) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-03T17:14:50+01:00 I tried cleaning every cache, and logging in and out of my account. I saw some reddit posts where they suggested to check out VPNs, host files and other stuff but everything was okay, also I can reach apple cdns etc. I also tried using Xcode beta 26.4 and going back to 26.2 but still the same problem. Anyone has a solution?

My project uses about 10 local packages. When Xcode determins its dependencies graph it includes project Foo (a package) and project Foo_Foo (???). This is a no op for normal builds, but causes the Foo package to be linked twice for test builds which then fail due to duplicate symbols. Nowhere in my repository is Foo_Foo defined or reference. Nowhere in the .xcodeproj/ folder is there mention of Foo_Foo. What am I doing wrong?

I have a group of XCUItest suites that were designed to run in parallel on simulators. They run fine in xcode 16.2, but when I try to run them in Xcode 26 they run fine the first time, but on the second time I get an error that the simulator cannot be found: "No matching device (62621AD4-C8D6-4A1B-B511-79236113FD94) ". This UDID seems to be from one of the clones that were spawned on the previous test run. No matching device (62621AD4-C8D6-4A1B-B511-79236113FD94) in set at /Users/myUser/Library/Developer/XCTestDevices Domain: com.apple.CoreSimulator.SimError Code: 404 User Info: { DVTErrorCreationDateKey = "2026-02-26 22:52:53 +0000"; IDERunOperationFailingWorker = "_IDEInstalliPhoneSimulatorWorker"; } If I clean all simulators and try to run again without closing Xcode, it keeps trying to access the clone that no longer exists. If I close an reopen xcode after removing all simulators ~/Library/Developer/XCTestDevices, xcode keeps trying the wrong device and I get the following error: Failed to clone device named 'iPhone 17 Pro'. (Underlying Error: The operation couldn’t be completed. Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.) This is what I get from CoreSimulator log: Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Device 3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818 encountered in creation state at launch. The device will be re-created. Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Failed to clone the device data path from /Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data to /Users/MyUser/Library/Developer/XCTestDevices/3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818/data, error = Error Domain=NSCocoaErrorDomain Code=260 "The file “data” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSURL=file:///Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSUnderlyingError=0x600000d04120 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Failed to re-create device that was encountered in the creation state (Clone 1 of iPhone 17 Pro (3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818, iOS 26.2, Creating)): Error Domain=NSCocoaErrorDomain Code=260 "The file “data” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSURL=file:///Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSUnderlyingError=0x600000d04120 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : New device is stuck in creation state, deleting: Clone 1 of iPhone 17 Pro (3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818, iOS 26.2, Creating) Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.} Feb 26 17:24:34 Mac-GD6GX5XH com.apple.dt.Xcode[2744] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.}

Dear Xcode Team, Please consider adding an option to position the Coding Assistant on the right side of the editor. Currently, when the assistant panel is open, it makes it difficult to access the Project Navigator at the same time. Having the ability to move the Coding Assistant to the right side would allow developers to keep the Project Navigator visible while interacting with the assistant, improving workflow and efficiency. Thank you

Development environment: MacBook pro Apple M1 macOS Tahoe 26.2 (25C56) Xcode 26.x iPhone 6 Plus / iOS 12.4.4 Exception description: After I upgraded to Xcode 26, my iPhone 6 Plus had a system version of 12.4.4. I was unable to perform real-device debugging, whether for existing projects or new ones. The error message from Xcode was as follows: Could not launch “xxx” Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: Cannot launch '/private/var/containers/Bundle/Application/A44062C1-32F5-4346-B13C-FC3F39EAF7A1/xxx.app': Unspecified Even though I have already added device support for the iOS 12.4 Has Xcode 26 stopped supporting the debugging of any devices running iOS 12 system?

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?

This is the full logging: libsystem_kernel.dylib`__pthread_kill: 0x2502f71c8 <+0>: mov x16, #0x148 ; =328 0x2502f71cc <+4>: svc #0x80 -> 0x2502f71d0 <+8>: b.lo 0x2502f71f0 ; <+40> 0x2502f71d4 <+12>: pacibsp 0x2502f71d8 <+16>: stp x29, x30, [sp, #-0x10]! 0x2502f71dc <+20>: mov x29, sp 0x2502f71e0 <+24>: bl 0x2502f2900 ; cerror_nocancel 0x2502f71e4 <+28>: mov sp, x29 0x2502f71e8 <+32>: ldp x29, x30, [sp], #0x10 0x2502f71ec <+36>: retab 0x2502f71f0 <+40>: ret

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?