I didn't run benchmarks before update, but it seems at least 5x slower. Of course all the LLM work is on remote servers, so is non-intuitive to me this should be happening. Had updated MacOS and Xcode to 26.1RC at the same time, so can't even say I think it is MacOS or I think it is Xcode. Before the update the progress indicator for each piece of code might seem to get stuck at the very end (and toggling between Navigators and Coding Assistant) in Xcode UI seemed to refresh the UI and confirm coding complete... but now it seems progress races to 50%, then often is stuck at 75%... well earlier than used to get stuck. And it like something is legitimately processing not just a UI glitch. I'm wondering if this is somehow tied to visual rendering of the code in the little white window? CMD-TAB into Xcode seems laggy. Xcode is pinning a CPU. Why, this is all remote LLM work? MacBook Pro 2021 M1 64GB RAM. Went from 26.01 to 26.1RC. Didn't touch any of the betas until RC1.

In my code, I used the newly added class AssetPackManager in Xcode 26. When compiling with Xcode 16, it would report an error saying "Cannot find 'AssetPackManager' in scope". Swift cannot use __IPHONE_OS_VERSION_MAX_ALLOWED. How to solve this problem?

Since Xcode 26 our tests are crashing due to the Main Thread not being able to deallocate WKNavigationResponse. Following an example: import Foundation import WebKit final class WKNavigationResponeMock: WKNavigationResponse { private let urlResponse: URLResponse override var response: URLResponse { urlResponse } init(urlResponse: URLResponse) { self.urlResponse = urlResponse super.init() } convenience init(httpUrlResponse: HTTPURLResponse) { self.init(urlResponse: httpUrlResponse) } convenience init?(url: URL, statusCode: Int) { guard let httpURLResponse = HTTPURLResponse(url: url, statusCode: statusCode, httpVersion: nil, headerFields: nil) else { return nil } self.init(httpUrlResponse: httpURLResponse) } } import WebKit import XCTest final class ExampleTests: XCTestCase { @MainActor func testAllocAndDeallocWKNavigationResponse() { let expectedURL = URL(string: "https://galaxus.ch/")! let expectedStatusCode = 404 let instance = WKNavigationResponeMock() // here it should dealloc/deinit `instance` automatically } Here the call stack: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 CoreFoundation 0x101f3dd54 CFRetain.cold.1 + 16 1 CoreFoundation 0x101e14860 CFRetain + 104 2 WebKit 0x10864dd24 -[WKNavigationResponse dealloc] + 52

In Xcode I've: select Product / Scheme / Edit scheme tap on Archive on the left hand side of the select post actions and + to add a new script Then in there I have added a script I want to run on the archive after its created. I'd like to be able to see the output the script churns out as it goes along but doesn't seem possible? If I just add something like echo "hello" to the start of the script then I don't see "hello" visible anywhere when I build an archive (via Product/Archive). I'm looking in the build navigator. Is there somewhere else to look or is it possible to get the logging into the navigator?

dSYM size became thrice for builds generated via xcode 26 compared to xcode 16. These are all release builds.

Hello Xcode 26.0.1 (17A400) Missing some Metal components When building a program using Metal, it induces an unexpected error : “error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain Command CompileMetalFile failed with a nonzero exit code” Which terminates the build The fix given “xcodebuild -downloadComponent MetalToolchain” using sudo does not work Did someone find a work around or could resolve the issue? Many thanks Jean MacBook Air M4; macOS 26.0.1; Xcode 26.0.1

Our project plans to upgrade Xcode from 16.2 to Xcode 26. We’ve noticed that the information on https://developer.apple.com/support/xcode/ states that the Deployment Targets for Xcode 26 supports iOS 15–26.1. However, the Deployment Targets for our current project is set to iOS 13. Does this mean that we must set the project’s Deployment Targets to iOS 15 or higher if we want to upgrade to Xcode 26? Can we still set the Deployment Targets to iOS 13? If we upgrade to Xcode 26 and set the Deployment Targets to iOS 13, will there be any problems?

Hello, I'm experiencing consistent crashes of XCPreviewAgent when using Xcode Previews on macOS 26.0.1 Tahoe (25A362). Configuration: macOS: 26.0.1 (25A362) - stable release Xcode: 16.0 (23.0.54) - stable release Hardware: MacBook Pro M4 Project: SwiftUI iOS app Issue: Every time I try to use Xcode Previews, XCPreviewAgent crashes with: Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000340e54000 Termination Reason: Namespace SIGNAL, Code 10, Bus error: 10 The crash occurs in shared memory region during dynamic library loading. What I've tried: Cleared all caches: rm -rf ~/Library/Developer/Xcode/DerivedData Deleted Preview data: rm -rf ~/Library/Developer/Xcode/UserData/Previews Reset simulators: xcrun simctl --set previews delete all Switched xcode-select to /Applications/Xcode.app/Contents/Developer Tried both Xcode stable and Xcode beta Created fresh simulators Clean build (Cmd+Shift+K) Rebooted Mac multiple times The app runs fine on simulator (Cmd+R), but Previews consistently crash.

We are experiencing troubles in our organization when we want to debug iOS applications on physical iPhones and iPads. Our iPhones (iPhone 16e, iOS 18.5) are not recognized by Xcode 16.4, but in the Finder they show up fine using the USB cable. We are aware, that the communication is different and there is an ad-hoc network that gets created to exchange the device profile. Together with our IT department responsible for our security infrastructure we narrowed it down to the following reason: As we are blocking all IPv6 traffic for local networking, the iPhone cannot communicate with Xcode to make the first connection and load the device profile. As they are not planning on changing this behavior, I am reaching out to you, if there is a way to force this first handshake between Xcode and iOS device to use IPv4? Or is there any other way to enable debugging for these devices? Any ideas would be very helpful.

開発アプリで通知確認を行うため、UDIDをプロビジョニングプロファイルに追加する必要があります。 iPhoneのUDIDは取得することができたのですが、AppleWatchのUDIDを取得する方法が分かりません。 Xcodeと接続してUDIDを取得しようとしましたが、iPhoneのみ認識がされAppleWatchが認識されていません。 AppleWatchもデベロッパモードをONしなければならないとAppleから返答をもらったが、その方法がわからないのでどなたかご教授お願い致します。

I'm trying to setup a macOS 26 build environment in a VM (using UTM and the virtualization framework Apple provides). I have Xcode 26 installed and have logged into my Apple ID and verified that the team and other configuration looks fine in Xcode settings. When trying to build the macOS app, I see errors saying the VM's device ID has not been registered. I have confirmed that the device ID is registered both in the Provisioning portal AND the downloaded .provisionprofiles (in Library > Developer > Xcode > UserData). This problem appears on multiple targets (e.g. the main app and extensions). If I try to manually provision the app, using the Provisioning portal, I can build the product, but it will not launch because of Gatekeeper issues. Finally, signing to run locally doesn't work either. As the app launches, frameworks refuse to load because Team IDs don't match. With ad hoc provisioning, there are no Team IDs. I've come to the conclusion that this just isn't possible. Which is a shame because I need to support products with a build environment on macOS 15 and cannot move over to macOS 26 yet. I suspect many developers outside of Apple are in a similar position.

I'm getting this error from inside the TestFlight tab in Appstore Connect. For a MacCatalyst app. This has worked for amost 4 years now I'm getting this error. I did update my version of Xcode to 26.0.1. And I migrated all the project settings it asked me to migrate. I ran the Validation in the Archive window of Xcode. No issues found there.

Whenever I hit play on my app to test it on the Mac the register .app part starts taking more than 15 minutes, this is severely impacting my work. There's no indication on what's wrong and how can I fix this.

Hi All, I have recently upgraded my Silicon Mac Laptop from MacOS 15.3 (Sequoia) to MacOS 26 (Tahoe). Since existing Xcode 16.2 is not compatible with MacOS 26, i installed Xcode 26.0.1 but after the successful installaton the application is not working and quits after the erorr dialog "Loading a Plugin Failed." (Screenshot attached). I tried resatring/reinstalling the Xcode 26.0.1 but no luck. To narrow down the issue i installed the same Xcode 26.0.1 in another Silicon Mac laptop with MacOS 26(Tahoe) where no previous Xcode was installed and it went well and working as expected. With my assumption Xcode 26.0.1 breaks when the device is upgraded from sequoia to Tahoe due to some conflicting old Xcode settings/files which may not be compatible with Xcode 26 or Tahoe but i am not sure. I followed some old articles as below from the forum and nothing worked for me so far. https://developer.apple.com/forums/thread/660860 https://developer.apple.com/forums/thread/719810 https://developer.apple.com/forums/thread/759396 Can some one shed a light on this to resolve this issue? Thanks.

We’re facing an issue when trying to install an enterprise-distributed iOS app on devices running iOS 18.5. During installation, we receive this error message: “This iOS app requires a newer version of iOS. You need to update this iPhone to iOS 26.0 to install this app.” However, in Xcode 26.0.1, our app’s minimum deployment target is explicitly set to iOS 17.6. After adding this step and the app result is unable to install the app on ios 18.5 and message getting as per the above quotes. Kindly help me out this issues.

Hello, I'm trying to remove a localization from a String Catalog in a Swift Package. How can I do that? I tried to remove the file and create a new one, but all the languages are back. The only place where I've found a reference to the languages is in Package/.swiftpm/xcode/package.xcworkspace/xcuserdata/user.xcuserdatad/UserInterfaceState.xcuserstate But I don't know how to edit this file to remove a language. Thank you, Axel

Every time I launch Xcode 26.0 (17A324), I see this window: Consequently, each time I launch Xcode, I must manually close the Downloads window, and it will always reappear the next time I launch Xcode. My question: How can I make the Downloads window with this message go away permanently, so I don't have to manually dismiss it? I tried deleting Device Support for Vision Pro (M5) and iPad Pro (M5) from Settings > Components, but unfortunately this is what I see: Thank you for any guidance you can provide.

I downloaded the Xcode Beta 3 on my MacBook Pro M4 Base today and tested out some iOS26 mechanics of my app. And when I came back to my main Xcode to continue developing in iOS18, I couldn't build my app. I went to Product > Destination > Manage run destinations and then tried to create a simulator with iOS18 but it didn't show up, only choice that's showing up was iOS26. I tried deleting iOS18 platform and downloading it again but it didn't solve, I tried deleting Xcode Beta but it didn't solve the problem either. I deleted Runtimes folder, it didn't solve too. I can not create a simulator of iOS18 or below too, the error says "The iOS 18.5 simulator runtime is not available. Try reinstalling Xcode or the simulator runtime." How can I fix this problem?

I found that unofficial apps like ChatGPT and Shadowrocket can use widgets in VisionOS 26. How is this achieved? How can I also enable widgets for apps I develop?

Hello Developers and Apple Engineers, I am encountering a persistent and highly unusual Xcode build failure when trying to use Metal APIs, specifically related to MTLCommandQueueDescriptor. I have exhausted all standard troubleshooting steps, including a complete erase and reinstall of macOS, yet the issue remains. Hardware diagnostics have passed. I am seeking insights or potential solutions. The Problem: When compiling any project (including brand new, empty macOS App projects) that attempts to set the dispatchType property on an MTLCommandQueueDescriptor instance, the build fails with the following errors: Swift // Code causing the error: let queueDescriptor = MTLCommandQueueDescriptor() queueDescriptor.dispatchType = .userInteractive // <-- Error occurs here // Compiler Errors: Value of type 'MTLCommandQueueDescriptor' has no member 'dispatchType' Cannot infer contextual base in reference to member 'userInteractive' Key Evidence - Physical Header File Corruption: The root cause appears to be a physically corrupted/incomplete SDK header file. Using the cat command in Terminal to inspect the contents of the relevant Metal header file confirms that the definition for MTLCommandQueueDescriptor is missing the dispatchType property: Bash cat /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Metal.framework/Versions/A/Headers/MTLCommandQueue.h The output consistently shows MTLCommandQueueDescriptor only having maxCommandBufferCount and logState properties, even after a fresh OS and Xcode installation. Environment: macOS: Version 26.0.1 (Build 25A362) - Clean install via Erase and Reinstall from Recovery. Xcode: Version 26.0.1 (Build 17A400) - Installed fresh from Mac App Store after OS reinstall. Mac Hardware: MacBook Pro (14-inch, M3) - (Please confirm this model info is accurate) Hardware Diagnostics: Passed (Tested at an official Apple Store). Exhaustive Troubleshooting Steps Performed (Issue Persists After All): Standard Xcode Cleaning: Clean Build Folder (Shift+Cmd+K). Manually deleted DerivedData folder (~/Library/Developer/Xcode/DerivedData). Deleted Xcode Caches (~/Library/Caches/com.apple.dt.Xcode, com.apple.dt.xcodebuild). Command Line Tools Path: Correctly set using sudo xcode-select -s /Applications/Xcode.app/Contents/Developer. Verified path using xcode-select -p. Verified version using xcodebuild -version. Multiple Xcode Versions & Install Methods Attempted (Before OS Reinstall): Xcode 26.0.1 (App Store). Xcode 26.0.1 (.xip package from Developer Portal). Xcode 26.1 Beta 3 (.xip package from Developer Portal). Performed thorough cleaning (deleted ~/Library/Developer, /Library/Developer, caches, rebooted) before each .xip installation attempt. In all cases, cat command confirmed the header file remained corrupted on disk after installation. Hardware Check: Took the Mac to an official Apple Store. Hardware diagnostics passed without any issues reported. Complete OS Reinstallation: Booted into Recovery Mode. Used Disk Utility to completely erase the internal SSD (APFS, GUID Partition Map). Reinstalled macOS 26.0.1 from Recovery. Set up the Mac as a new device (did not restore from backup). Post-OS Reinstall: Installed Xcode 26.0.1 fresh from the Mac App Store. Set command line tools path correctly. Created a brand new macOS App project (MetalTest). Pasted the minimal code to reproduce the issue into AppDelegate.swift. Build failed with the exact same errors. Ran the cat command again, confirmed the MTLCommandQueue.h file on the fresh system is STILL missing the dispatchType property. Request for Help: Given that the SDK header file corruption persists even after a complete macOS erase and reinstall, and hardware diagnostics have passed, I am at a loss for the cause or further troubleshooting steps. Has anyone encountered a similar situation where core SDK files remain corrupted despite a clean OS install and passing hardware checks? Are there any deeper system caches or states that might survive an erase/reinstall and interfere with SDK file integrity? Are there any more advanced diagnostic steps recommended? Any insights or suggestions from Apple engineers or the community would be greatly appreciated. Thank you. I have previously contacted Apple Developer Support regarding this issue, case ID: 102731239935.