I am editing my iOS project in Xcode 16 and want to use the "Swift Compiler - Upcoming Features" section of the build settings to selectively enable the new Swift 6 language features.
I have read the instructions for doing this and have dowloaded an Apple sample project and can see that section under the project and target-level Build Settings in the sample project
However, when I open my Xcode project in XCode 16 that section does not appear.
Is there any way for me to influence how Xcode 16 displays the build settings?
In fact, no "Swift Compiler" sections appear at all under my project Build Settings (All | Combined). There is a "User-Defined" section that has the Swift Version, Compilation Mode and Optimization level.
The project itself is several years old and was on a very old project version. I have upgraded my project document format to "Xcode 16" but it made no difference.
I have compared my project and the sample project in a text editor and both seem to have similar structure. I tried removing unused and outdated settings from my project but that also had no effect.
Is there an alternative to deleting my project file and adding the source files to it? I have a large project with multiple targets so that would be something I'd rather not do.
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
ChatGPT in Xcode 26.1 is super slow for me, anyone else?
The response returns quickly but the preview window takes a few seconds per line. What it used to do in a few seconds on 26.0 now takes tens of minutes.
Anyone else running into this and have suggestions? I'm using the minimal setting on a fast internet connection. M2 Pro MBP, macOS 26.1.
"EnableLiveAssetServerV2-com.apple.MobileAsset.MetalToolchain" = on;
ProductName: macOS
ProductVersion: 26.0.1
BuildVersion: 25A362
The MetalToolchain is installed, however I keep getting error that MetalToolchain cannot be found by the Xcode
"Command CompileMetalFile failed with a nonzero exit code"
error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain
❯ xcodebuild -downloadComponent MetalToolchain
2025-10-31 11:18:29.004 xcodebuild[6605:45524] IDEDownloadableMetalToolchainCoordinator: Failed to remount the Metal Toolchain: The file “com.apple.MobileAsset.MetalToolchain-v17.1.324.0.k9JmEp” couldn’t be opened because you don’t have permission to view it.
Beginning asset download...
2025-10-31 11:18:29.212 xcodebuild[6605:45523] IDEDownloadableMetalToolchainCoordinator: Failed to remount the Metal Toolchain: The file “com.apple.MobileAsset.MetalToolchain-v17.1.324.0.k9JmEp” couldn’t be opened because you don’t have permission to view it.
Downloaded asset to: /System/Library/AssetsV2/com_apple_MobileAsset_MetalToolchain/4ab058bc1c53034b8c0a9baca6fba2d2b78bb965.asset/AssetData/Restore/022-17211-415.dmg
Done downloading: Metal Toolchain 17A324.
Hi,
I'm running Xcode version 26.0.1 (17A400). Every time I restart Xcode, it seems to not recognize my Claude login anymore, and I have to go through the whole authentication flow again. It's quite annoying. Does anyone have a solution for it?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi,
in our Xcode project we have a Tooling package, which defines build tool plugins for generating compile time safe constants for our localization strings as well as assets using swiftgen.
This is working very well in Xcode 16, but fails in Xcode 26 beta 1 and beta 2 as well.
The failure is specifically:
unsupported configuration: the aggregate target 'Localization' has package dependencies, but targets that build for different platforms depend on it.
I've reduced this to a minimal sample project, which you can find here.. To reproduce: Open the Repro workspace, that is attached in Xcode. Try to build TestyPackage. You'll see the error.
I've filed this bug during WWDC week, but no feedback yet and no solution in Xcode 26 beta 2. Here's the feedback number, in case you have this too and want to file a duplicate: FB17934050.
Does anyone else have this issue and perhaps a solution?
Any idea what this message means? I assume it's coming from CloudKit, but the application seems to store and retrieve data properly.
Can we use Icon Composer to drive an app icon for iOS 26 apps today? I get errors uploading a build to TestFlight internal testing about missing App icon dimensions for an iOS 26 app.
I am writing to report multiple issues encountered after updating to Xcode 26 Beta, which have significantly impacted my project's compilation and functionality. My project can run normally in Xcode16.3 version, Below are the specific problems, along with the steps I took to address them and the subsequent errors that arose:
Symbol Not Found Error for _NSUserActivityTypeBrowsingWeb
After updating to Xcode 26 Beta, my project failed to build with the error: "Symbol not found: _NSUserActivityTypeBrowsingWeb." To resolve this, I removed the MobileCoreServices framework from the Build Settings, as it appeared to be related. However, this led to a new error, indicating that this change introduced further complications.
Clang++ Error: No Such File or Directory 'OpenGLES'
Following the resolution of the first issue, I encountered a new error: "iOS clang++: error: no such file or directory: 'OpenGLES'." To address this, I added the OpenGLES.framework to the Build Phases. While this resolved the clang++ error, it triggered additional errors, suggesting that the underlying issue persists or new dependencies are conflicting.
Recurring XIB File Compilation Errors
My project uses XIB files, and every time I attempt to compile and run, Xcode reports errors related to different XIB files. Notably, when I open the reported XIB file, no errors are displayed within the Interface Builder. After saving or inspecting the file, the compilation error temporarily disappears, only for another XIB file to trigger the same issue in the next build. This creates a repetitive cycle. I have confirmed this is not a caching issue, as I clean the build cache (Product > Clean Build Folder) before each run. If I skip cleaning the cache, the OpenGLES-related error (Issue 2) reappears, indicating potential interactions between these problems.
These issues have made development with Xcode 26 Beta extremely challenging, as each attempted fix seems to introduce new errors, and the XIB issue creates a persistent loop. My setup includes:
Xcode Version: 26.0 beta 2 (17A5241o)
macOS Version:15.4.1 (24E263)
Right now, I am trying the tutorial for SwiftUI from the Apple Developer Program inside of Xcode, but I encountered a problem. Inside of the selectable canvas mode in Xcode, I wanted to command-control-click the element (in this case, a text) to bring up the editing popover and select "Show SwiftUI Inspector." For some reason, on the popover menu, the only option was "Embed." I only wanted the menu point Show SwiftUI Inspector, and I also tried the shortcut Ctrl+Option, but nothing worked. Now is there another method to get to this menu? Or can you help me with that?
Noah
Topic:
Developer Tools & Services
SubTopic:
Xcode
To reproduce this bug create a new Xcode Project for IOS choose UIKit. In the app delegate add the following lines.
As you can see in the above image . Line 19 with the initialization of PHPickerViewController has no compilation failure.
Now lets add import WidgetKit
As soon as widgetKit is imported a compiler error is thrown which is PHPickerViewController is not in scope.
This worked with Xcode 16.4
It was possible to have a swift file with both WidgetKit implementations and PhotosUI implementations. This behavior has changed in Xcode 26/26.0.1 .
Does anybody know why this happens , could not find any clues within the different versions of documentations.
P.S
Found a work around which raises further questions
Adding import SwiftUI fixes this problem , I am genuinely curious on how this is happening on a compiler level.
LINKS
To my previously published post :https://developer.apple.com/forums/thread/804059
Hi everyone,
Since updating to Xcode 26, I’ve been running into an issue with the new ChatGPT integration inside Xcode.
Even though I have an active ChatGPT Plus subscription (GPT-4 or GPT-5) and I’m signed in to my OpenAI account, Xcode doesn’t seem to recognize my paid plan. After reaching the free usage limit, I get the following message:
“Over daily limit. ChatGPT in Xcode will be unavailable for up to 24 hours.
For higher limits, sign in with a paid ChatGPT account or upgrade to ChatGPT Plus.”
The issue is that I am already logged in with my ChatGPT Plus account, and everything works fine on the ChatGPT web app — but inside Xcode, it keeps treating me as a free user.
Here’s what I’ve tried so far:
• Signing out and back into ChatGPT from within Xcode
• Restarting Xcode and macOS
• Verifying that I’m logged in to ChatGPT in Safari
• Updating both macOS and Xcode to the latest versions
None of these steps have resolved the issue. It seems like Xcode isn’t syncing properly with OpenAI authentication, and therefore it applies the free-tier limits even for paid accounts.
Has anyone else encountered this problem?
Is there any way to force Xcode to reauthenticate with OpenAI or link it properly to a ChatGPT Plus account?
System setup:
• Mac mini (Apple M2, 16 GB RAM)
• macOS Tahoe 26.0.1
• Xcode Version 26.0.1 (17A400)
Here’s the error message I’m seeing:
Topic:
Developer Tools & Services
SubTopic:
Xcode
Xcode Preview is not working.
Successed to build Preview but error message displays like below:
I think it's maybe related with loader path followed by error details below.
I created xcproj file using tuist 4.19.0.
How can I fix this issue?
Error Details
Is it just because it's still so early or are we not getting the feature in the EU for the time being?
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm pulling my hair out here with this new Xcode 16, it complains that my app's dSYM is empty though it's clearly not, it's about 25MB.
I'm working on a project using an internal static library, everything is built inhouse using swift, we own all the source code. It worked just fine until the other week, when I updated the Xcode, and now I can't debug anything. I keep getting "type for self cannot be reconstructed" when I run "po self.some_property". Why is that?
The Debug information Format is set to DWARF with dSYM File for both the executable and lib projects.
I've been a Unix guy since before I knew myself and I enjoy fixing things myself, down to bare metal, but man, this bug is driving me crazy. Is it even a bug??
It's the first time in more than 15 years since I started coding on Mac and iPhone when a bug has defeated me. I was always able to fix things using just the documentation and google, but the Apple toolchain is getting worse and worse nowadays.
I remember the time when Apple made the complicated things simple, now they make the simple things complicated :(
I just split the static lib from the main project one year ago, because of the ridiculously long build time. Should I merge back all the code in a single project? Something seems wrong to me.
So I created this account to ask the masters. How can I get back my debug info (and sanity)? Using Xcode 15 is not an option because it doesn't run on Sequoia.
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
At the Platform State of the Union, Apple demoed clicking a ✨ button in the Xcode toolbar to use Apple Intelligence in Xcode.
I don't see that button in Xcode Version 26.0 beta (17A5241e). Am I missing it? It's supposed to be in the upper-left corner, right?
Do I need to turn it on or something? I'm on macOS 15.5 Sequoia, on a 16-inch, 2021 MacBook Pro
Hello,
I’m new to macOS after many years on iPhone, and I’m trying to run a simple app on my iPhone directly from Xcode. The app builds fine in the simulator, but deploying to a real device fails with this error:
The tunnel connection failed while the system tried to connect to the device.
Domain: com.apple.dt.CoreDeviceError
Code: 4
Failure Reason: The tunnel connection failed while the system tried to connect to the device.
User Info: {
DVTErrorCreationDateKey = "2025-10-02 16:55:53 +0000";
"com.apple.dt.DVTCoreDevice.operationName" = connect;
}
--
The tunnel connection failed while the system tried to connect to the device.
Domain: com.apple.dt.RemotePairingError
Code: 4
--
I get the same error via command line, e.g. for
xcrun devicectl device info apps --device "..."
My setup:
macOS Version 26.0.1 (Build 25A362)
Xcode 26.0.1 (Build 17A400)
iPhone 13 on iOS 26.0.1
iPhone is paired with the Mac (I can see it in Finder and in Xcode alongside the simulator).
Developer Mode is enabled on the iPhone.
I also see my Apple Watch listed in Xcode.
I might have enabled Multipath networking in the past - but in iOS 26.0.1, the setting is missing in the Developer settings - so there is no way to check if it's enabled or to disable it. I know this was the solution to a similar problem: https://developer.apple.com/forums/thread/737907
What I tried:
Restarted both Mac and iPhone, unpaired them, paired them again.
Disabled and re-nabled development mode
Tried both Wi-Fi and wired connection (Apple-certified cable).
Reset privacy and network settings on the iPhone.
Verified I’m not running any VPN.
Despite this, deployment always fails with the same tunnel connection error.
Has anyone encountered this before or found a solution/workaround?
Thank you very much,
Martin
Topic:
Developer Tools & Services
SubTopic:
Xcode
I am experiencing an issue with Xcode 16.2 (15E204a) where global workspace search does not return results from .xib files.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Is anyone else receiving this warning from Xcode when running on the Simulator?
"Failed retrieving MusicKit tokens: fetching the developer token is not supported in the simulator when running on this version of macOS; please upgrade your Mac to macOS Ventura."
My Mac is already updated to macOS Sequoia, and I'm also running the latest version of Xcode. Feedback: FB17150538
When I try to build my project with Xcode 26.1 beta (17B5025f) it freezes a lot.
The steps are as follows:
Open my project with the aforementioned Xcode
Start a build of one of my schemes
Open a browser or any other app above the Xcode window
Try to present the Xcode window on the foreground
Result: Xcode freezes
I cleared the Derived Data and it still happens