Hi everyone, I’m running out of space on my Mac and I need to use an external SSD to free up room, especially because Xcode is taking a lot of storage. I want to know if it’s safe to move some Xcode files—projects, derived data, or system-related files—to an external SSD. Which files can I move safely, and which should stay on the internal drive? I want to avoid breaking anything or causing issues with Xcode or macOS. Also, is it the same situation if I use an external HDD instead of an SSD? Are there additional risks or performance issues to consider?

I'm struggling to build a driver for iPadOS in a particular project configuration. If I put the driver code and dext target into the same Xcode project which contains the iPad app, all is well. This is the way the Xcode driver template does it. However, I'd like to build and debug the dext on macOS, while eventually deploying on iPadOS. So I put the dext into a different project, which has a macOS target, a minimal iPadOS target and a DriverKit target. I made a workspace which contains both projects. I dragged the macOS project into the iPadOS project so that I can refer to the products of the macOS project (specifically, its driver target) as a dependency of the iPadOS target. Note that the main iPad app target depends on the driver target. So the workspace organization looks like this: Workspace iPad project main iPad app target (depends on driver) test project reference test project test macOS/iPad app target DriverKit dext target When I build the iPadOS target, it builds the dependent driver target in the macOS project, but it fails to link because Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a is not found. If I just build the driver target directly in Xcode, there is no such complaint. I looked closely at the build logs, and I see for the failed link, there are these two linker flags set which are not set in the successful case -debug_variant -fprofile-instr-generate I can't seem to control the generation of this flag. I tried turning off the Profile switch in the Scheme editor for the driver, but is makes no difference. When I directly build the driver target, no -fprofile-instr-generate is set and it compiles and links. When i build the driver as a dependency of another target, -fprofile-instr-generate is passed to the linker, which fails. The obvious workaround is to put the driver source code into a separate driver target in the iPadOS project, but I'd rather have just one DriverKit driver for both platforms, with a few settings (such as bundle ID) controlled by a configuration file. Has anyone else encountered this problem, and know of a workaround?

On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4, and is likely introduced in XCode 26. Related threads: https://developer.apple.com/forums/thread/809989 https://developer.apple.com/forums/thread/793307 Work-around Do not store XCUIApplication in the XCTestCase instance, maintain it scoped to the test methods.

I have Xcode 26.1.1 (installed on a Mac Mini with Sequoia 15.7.2), which was installed from the Universal .xip file available from the Apple Developer site. This file is 2.7Gb. When Xcode is run, there is a menu item at Settings -> Components, and the top section "Platform Support" includes an option to "Get" the iOS SDK, which is an additional 10.3Gb download.[1][2] I would like to either use command-line tools to obtain this iOS SDK component, or find where the downloaded package or its contents are installed on this Mac. This Apple Documentation some examples of using command-line tools to download components for Xcode. However, there is no specific documentation on how to separately download the iOS SDK. It seems that if possible, it could be done with "xcodebuild -downloadComponent", however I have tried a number of likely component names (ios, ios_sdk, ios26.1, ios_sdk26.1, iphoneos, iphoneos_sdk, iphoneos_sdk26.1), and none are valid. Does anyone know either where the SDK download can be found, or how to download it using command-line tools? Background: I require this as I am managing a fleet of Mac Minis located in a data centre (used for iOS/Android builds), and Internet access is restricted - any action requiring Internet access needs the Mac to be removed from the machine room racks and taken to a build room, then connected to a mobile hotspot or similar. This access is slow, and the above 10.3Gb download can take over an hour. If I can download the SDK separately, I can distribute it to all of the Macs over the internal network overnight, in advance of visiting the DC for upgrade tasks. [1] Various web sites say that the iOS SDK is "bundled with" Xcode. However, if that's the case a) how is a 10.3Gb download somehow included in a 2.7Gb file? And b) why do I still need to "Get" this component after installing Xcode from the 2.7Gb file? [2] Note that I am not looking for the iOS Simulator, I have already downloaded the iOS 26.1 version of this. I am specifically looking for the iOS SDK as listed under "Platform Support" in the Xcode menu described above.

Prior to iOS 26.0 we were able to download specific simulator runtimes from the command line by using a command like xcodebuild -downloadPlatform iOS -buildVersion 18.0 This is described in the documentation here. This no longer works for 26.x. If I run the following command: "xcodebuild -downloadPlatform iOS -buildVersion 26.0" it fails with the following error: "Finding content... iOS 26.0 is not available for download." If I omit the -buildVersion flag it will download the latest version, currently 26.2, but if I try and specify 26.2 as the buildVersion I still get "iOS 26.2 is not available for download". This behavior has been confirmed on Xcode 26.2. Perhaps related, it appears these runtimes are also no longer being made available for download on https://developer.apple.com/download/all

显示为——构建描述签名错误: 签名证书无效。签名证书；不可用于代码签名。它可能已被吊销或过期。、 目前是在Apple Developer 重新创建证书、生成描述文件了（显示的是有效）；但是下来出来放进打包里就显示证书失效是什么原因？

Recently I noticed that although my drive showed ~800Gb of usage, the folders within totally to around ~600Gb (and yes I was including hidden 'dot' files/folders. After some inspection I found that there are a whole set of Disk Media Images, that appear to be related to XCode simulators. Here's an extract from the command line diskutil list command: /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk5 Physical Store disk4s1 1: APFS Volume iOS 26.2 Simulator 17.1 GB disk5s1 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.2 GB disk6 1: Apple_APFS Container disk7 14.2 GB disk6s1 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.2 GB disk7 Physical Store disk6s1 1: APFS Volume XROS 26.2 Simulator 13.8 GB disk7s1 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.2 GB disk8 1: Apple_APFS Container disk9 17.2 GB disk8s1 /dev/disk9 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.2 GB disk9 Physical Store disk8s1 1: APFS Volume iOS 26.0 Simulator 16.7 GB disk9s1 /dev/disk10 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +8.5 GB disk10 1: Apple_APFS Container disk11 8.5 GB disk10s1 /dev/disk11 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +8.5 GB disk11 Physical Store disk10s1 1: APFS Volume XROS 2.5 Simulator B... 8.2 GB disk11s1 /dev/disk12 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +18.0 GB disk12 1: Apple_APFS Container disk13 18.0 GB disk12s1 /dev/disk13 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +18.0 GB disk13 Physical Store disk12s1 1: APFS Volume XROS 2.5 Simulator 17.5 GB disk13s1 /dev/disk14 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk14 1: Apple_APFS Container disk15 17.6 GB disk14s1 /dev/disk15 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk15 Physical Store disk14s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk15s1 /dev/disk16 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.1 GB disk16 1: Apple_APFS Container disk17 14.1 GB disk16s1 /dev/disk17 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.1 GB disk17 Physical Store disk16s1 1: APFS Volume XROS 26.1 Simulator 13.7 GB disk17s1 /dev/disk18 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk18 1: Apple_APFS Container disk19 17.6 GB disk18s1 /dev/disk19 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk19 Physical Store disk18s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk19s1 /dev/disk20 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +9.1 GB disk20 1: Apple_APFS Container disk21 9.1 GB disk20s1 /dev/disk21 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +9.1 GB disk21 Physical Store disk20s1 1: APFS Volume iOS 18.5 Simulator B... 8.8 GB disk21s1 /dev/disk22 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +20.7 GB disk22 1: Apple_APFS Container disk23 20.7 GB disk22s1 /dev/disk23 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +20.7 GB disk23 Physical Store disk22s1 1: APFS Volume iOS 18.5 Simulator 20.2 GB disk23s1 I am unable to unmount them, either from the command line or Disk Utility. How do I go about this?

This is a grave issue I am facing while testing my apps on my personal device. This is the error I seem to be getting: "The application could not be launched because the Developer App Certificate is not trusted." And on the phone side, this is the message: Unable to Verify App. An internet connection is required to verify the trust of the developer "Apple Development... Before I receive any recommendations, such as deleting Xcode or restarting my device, I would like to clarify that I have already taken all necessary precautions. The application I was testing appeared to function correctly in the morning a few hours prior to the update. However, after upgrading to the latest beta builds, iOS 26.4 beta and the latest macOS beta, this issue has become a recurring problem. I would greatly appreciate your assistance in resolving this matter, as it is of utmost importance to me.

I've seen a couple posts on reddit today but wanted to call out here because I think it may be a more widespread issue - I keep getting an error trying to open my iOS app saying "Unable to verify app - An internet connection is required to verify trust of the developer...". I have never gotten this issue before and did not change anything in my build settings from my last successful build of the app to now. The directions it gives me are to go to Settings > General > VPN and Device Management and trust my developer certificate from there, but that doesn't work either. The first time I tried this, the developer certificate wasn't there at all, then I looked at Reddit and saw people recommending to download the developer certificate to solve the issue, but doing this did not fix the error either. Just looking to see if anyone else has encountered this or what the fix might be.

I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical "Why" This error message reveals that the issue lies in the CoreDevice (and formerly usbmuxd) infrastructure, specifically in the secure transport layer. The "Tunnel" Failure: Xcode attempts to establish a secure, encrypted tunnel (DTXConnection) to the Apple Watch to push the debugger and the app binary. Unlike the iPhone, which can sustain a high-bandwidth connection easily, the Watch aggressively manages its radios (Bluetooth vs. WiFi vs. AWDL) to save battery. The "Handshake" Timeout: If the Watch is on Bluetooth (Low Energy) when Xcode initiates the tunnel, the bandwidth is insufficient. The system tries to escalate the connection to WiFi (or Apple Wireless Direct Link). If this negotiation takes even a few milliseconds too long—due to 2.4GHz interference, router mDNS configuration, or the Watch CPU being throttled—the handshake times out. The "Previous Preparation Error": This is the insidious part. Once the handshake fails once, Xcode’s device service caches that failure state for the device UUID. It marks the device as "unreachable" to prevent the IDE from hanging indefinitely on subsequent tries. Why you see it constantly: You aren't actually triggering a new connection attempt; you are hitting the cached "failed" state immediately. Unfortunately, the solutions it gives me are: The "Wired Proxy" Method (Most Reliable) This is the gold standard for watchOS debugging. Do not rely on "Connect via Network" for the Watch directly if you can avoid it. Disable WiFi on your Mac (temporarily) or ensure the Mac and iPhone are on the exact same SSID. Plug your iPhone into the Mac via USB. Ensure the Watch is paired to that iPhone. Result: Xcode will tunnel the instructions through the USB connection to the Phone, and the Phone acts as a high-bandwidth proxy to the Watch. This eliminates the "Mac-to-Watch" WiFi negotiation failure point. Do you hit this regularly? What do you do to make for a smooth development and deployment process? Or is it really this fragile? Thanks for any help! Bryan

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

When building our project for Mac Catalyst with Xcode 26.2, we get this warning almost a hundred times, once for every object file: directory not found for option '-L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' Somehow, every Link <FileName>.o build step got the following parameter, regardless if the target contained Metal files or not: -L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst The toolchain is mounted at this point, but the directory usr/lib/swift/maccatalyst doesn't exist. When building the project for iOS, the option doesn't exist and the warning is not shown. We already check the build settings, but we couldn't find a reason why the linker is trying to link against the toolchain here. Even for targets that do contain Metal files, we get the following linker warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' not found Is this a known issue? Is there a way to get rid of these warnings?

While WhatToTest..txt was being used in xcode cloud. I wish this feature should just being adopted to functioned from XCode archive and upload to set initial release note from the build pipeline directly from xcode in machine

In Xcode 26.3 and 26.4, when I use Xcode's built-in git functionality to do a "pull" or "fetch", Xcode presents a dialog saying it's performing the operation, but it never completes. The dialog remains on screen with a spinner. My remote repos are stored on a Mac mini on my local network and I access them via SSH. The git command line works fine, as does the tool Git Tower. I've filed this as FB22091014. Has anyone else seen this, and if so, found a solution?

Does Xcode 26 still support creating pull requests and/or viewing comments from GitHub pull requests associated with the current branch? This used to be possible, but I cannot get it to work with the current version of Xcode (26.0.1). The "Create Pull Request" menu item takes me to github.com directly, instead of presenting a nice UI menu; hence I'm wondering.

In my tabview i set a safeAreaBar topPanel, under i have contentview. That ignore safeArea.top so feed go under. What is the best Way to have a the first post in content appear under (under the bottom) if the safeareabar. I use list with foreach. Do we measure the height or is it some smart tips?

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

Hi everyone, I want to avoid the iOS 26 Liquid Glass effect in my app’s UI. While researching, I found the following possible solution: Steps: Go to Info.plist Add the key: UIDesignRequiresCompatibility Type: Boolean Value: YES I have a few questions about this approach: According to the Apple Developer website, this seems to be a temporary solution. How long will this continue to work, and what would be the recommended long-term solution? Which iOS versions does this support (both older and upcoming versions)? If this method is not recommended, is there another way to disable or avoid the glass effect across the entire app without making major UI changes? Any guidance or suggestions would be greatly appreciated. Thank you!

Hello everyone, I’m facing an issue with my app submission being stuck in “Waiting for Review.” I initially submitted my app on 21 February and waited until 27 February, but the review process did not start and there were no updates. On 27 February, I contacted Apple Support regarding this issue, but I did not receive any response. Since there was still no progress, on 4 March I removed the app from review and resubmitted it again, but it is still showing “Waiting for Review.” This delay is affecting my operations, so I would really appreciate any guidance or help if someone has experienced a similar situation. App ID: 6741708449 Thank you.

Can't able to run the Create ML for training and I upgraded to MacOS 26.3 beta and I have tried older and newer