Hi, I'm experiencing a strange issue with iCloud Drive and Xcode on a Mac mini (Apple Silicon). Environment Mac mini (Apple Silicon) macOS Tahoe 26.5.2 Xcode 26.5 Symptoms Files in iCloud Drive Desktop stay at "Waiting to Update" for several days. Cloud icons never disappear. Moving projects from iCloud Drive Desktop to ~/Developer takes hours or never finishes. Existing Xcode projects stored in iCloud Drive open as a white "Loading..." screen forever. New Xcode projects work normally. Projects already moved to ~/Developer (for example one project) open and build normally. What I have already tried Restart Mac Updated to the latest macOS Cleared Xcode caches (DerivedData, Archives, old simulators) 132 GB free disk space killall fileproviderd killall bird brctl download brctl diagnose fileproviderctl check -P Logs After restarting fileproviderd, I continuously get messages like: Possible slow statement on SELECT ... scheduler not stable: jobs are running fetch-metadata ... is busy fileproviderd constantly uses around 70% CPU. Also, fileproviderctl check -P never completes. It stops at: "About to launch FPCK checks for 1 domains" and stays there for more than 10 minutes. Questions Has anyone experienced this with macOS Tahoe? Is this likely a CloudDocs/FileProvider database issue? Is there any safe way to repair the FileProvider database without risking iCloud data? Is there any way to identify or clear the stuck synchronization queue? Any advice would be greatly appreciated.

Getting this error trying to submit a build for External Beta App Review: "There was an error processing your request. Please try again later." Build shows "Ready to Submit," internal testing works fine, error happens even before selecting a build. Retried several times over a few days, no change. Checked export compliance, still confirming Test Information is fully filled out. Anyone hit this exact error, especially at the build-selection step?

I am getting this error when trying to run my tests: Library not loaded: @rpath/XCTestCore.framework/XCTestCore Referenced from: <498690CD-C914-3EE9-8EC1-C3BA4EF513CA> /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/lib/libXCTestSwiftSupport.dylib Reason: tried: '/Users/<>/Library/Developer/Xcode/DerivedData/Sonnet-bqruszxvmhdevmbxdbnagkvhywae/Build/Products/Test Project-iphonesimulator/XCTestCore.framework/XCTestCore' (no such file) It is only appearing on the DeviceHub. When I run the tests in my xcode 26, with the old Simulator, they run just fine.

Context is Swift UI iOS app with Xcode 26.6 In my project's Localizable.xcstrings, I have terms flagged as "don't translate". However, when I export the terms with the "Export localizations" menu command, these entry are still listed in the exported XLIFF files (with shouldTranslate:false) Any way to bypass these entries to get accurate clean XLIFF exports ? Thx&rgds, François

Hello! I'm using the new Xcode 26.3 RC and it's new MCP server: However, I am repeatedly prompted to give access to Codex (both the new macOS app and the CLI). And I'm seeing duplicates in the Xcode dropdown: It's pretty blocking in my workflow as I have to keep Allowing over and over again.

Xcode 27 Beta 3 / watchOS 27 Beta 3 - Apple Watch won’t show PIN when pairing in Device Hub (Solved) I ran into an issue where my Apple Watch could no longer pair with Xcode after I manually removed it from Device Hub. Environment Xcode 27 Beta 3 macOS Tahoe Beta iOS 27 Beta 3 watchOS 27 Beta 3 Symptoms iPhone appears in Device Hub and is Connected. Apple Watch does not appear in Device Hub. On Apple Watch: Settings → Privacy & Security → Developer Mode → Devices My Mac appears in the list. Tapping the Mac: Enter watch passcode. Tap Pair. Expected: Xcode should display a 6-digit PIN. Actual: Xcode remains on “Waiting to Pair” forever. No PIN is shown. Additional observations Running: xcrun devicectl list devices Only shows the iPhone. The Apple Watch never appears. Also, while reproducing the issue, coredeviced receives no pairing request at all. So it doesn’t look like the pairing challenge is failing—the pairing request never reaches the Mac. Things I tried (none worked) Restarted Mac, iPhone and Apple Watch. Removed pairing from Device Hub. Removed the Mac from Apple Watch Developer Mode → Devices. Turned Developer Mode off/on. Erased and re-paired the Apple Watch with the iPhone. Re-enabled wireless development. None of these solved the issue. Solution What finally worked was surprisingly simple: Completely power off the iPhone. Keep the Apple Watch and Mac powered on. Pair the Apple Watch from Device Hub again. Immediately after the iPhone was powered off, Xcode displayed the pairing PIN and the pairing completed successfully. After the watch was paired, I powered the iPhone back on and everything continued to work normally. My guess It seems the iPhone (the companion device) may be holding a stale developer pairing state after the watch is manually unpaired from Device Hub. With the iPhone powered off, the watch appears to communicate directly with the Mac, allowing the pairing challenge to be created successfully. Hopefully this helps anyone else who gets stuck at “Waiting to Pair” with no PIN appearing.

Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing.

After upgrading from Xcode 26.5 to Xcode 26.6, I noticed that the built-in Agents section has changed. My environment Xcode 26.6 (Build 17F113) macOS 26.5.2 (Build 25F84) Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing. The Chat section still works normally. Comparison On the same Mac: Xcode 26.5 shows: Claude Agent Codex Get buttons Xcode 26.6 only shows MCP ("Allow external agents to use Xcode tools") and "Add an Agent...", with no built-in Agents. Things I have already tried Deleted all Xcode preferences Deleted ~/Library/Developer Deleted ~/Library/Application Support/Xcode Reinstalled Xcode 26.6 Signed out/in of Apple ID Verified Intelligence is enabled No change. Additional information The following directory is never created: ~/Library/Developer/Xcode/CodingAssistant Searching Xcode preferences also shows no Agent-related configuration. Question Is this an intentional change in Xcode 26.6, or is this a bug? If it's expected, how can I restore the built-in Agent catalog (Claude Agent / Codex)? Thanks!

The following code crashes as soon as the app launches. struct ContentView: View { var body: some View { List { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } I would expect the code not to crash. Note that using a ScrollView works perfectly fine: struct ContentView: View { var body: some View { ScrollView { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } The documentation clearly stipulates that it should work with a list: A scrollable view like ScrollView or List Using Xcode 26.5 (17F42) and simply created a new macOS project using SwiftUI. Feedback FB23655564

It doesn't seem to be able to launch. It says "This version of Xcode is not compatible with this version of macOS." So, does that mean that users who have updated to macOS 27 cannot submit apps to the App Store? Do I have to wait until Xcode 27 starts accepting submissions? Environment: macOS 27.0 / Xcode 26.6 RC

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

Anyone else seeing a lot more "Class X is implemented in both ..." warnings on Xcode 27 than on Xcode 26? Same source, same flags, the count goes from a handful to a couple thousand, and some now correlate with real crashes (cast failures, missing protocol conformances) instead of the usual harmless first-wins behavior. Is this a known change in Swift 6.4 / Xcode 27? Is there a new flag I should be passing? Any suggestions welcome.

With Xcode Version 26.5 (17F42) apps can no longer be launched on a real Vision Pro once migrated to visionOS 27 Beta 2. At launch there is an EXC_BAD_ACCESS runtime error in an initialiser. If you launch apps on a real iPhone/Ipad with OS 27 Beta 2 the program will stop before the end of its start, but there is no precise line with the error. Xcode just stop in assembly code in the debugger, in the init phase of Swift where it searches for which objects to instantiate at launch. After investigating, the error comes from a debug setting from Xcode to show the stack trace. To avoid the error when run from Xcode Version 26.5 (17F42) In Xcode, open Product > Scheme > Edit Scheme. Select the Run action in the sidebar, then open the Options tab. Find Queue Debugging and uncheck Enable backtrace recording. If Queue debugging is enabled, then the program crashes when launched It is useful to be able to run apps from the production Xcode to devices with 27 OSes in beta to be able to test that everything will work fine for new versions of apps released before OSes 27 release. Thank you A previous post was made but the cause was badly identified. New Feedback including a sample code FB23384318

My Mac Catalyst app (distributed via TestFlight) crashes instantly at launch — before main() — on macOS 26.5.1 (25F80) when archived with Xcode 27 beta 3. The same code archived with Xcode 26.5 (GA) launches fine. Crash excerpt: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleBody Referenced from: <...> /Applications/Paku.app/Contents/MacOS/Paku Expected in: <...> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (terminated at launch; ignore backtrace) What appears to be happening The symbol comes from completely ordinary UIKit code — e.g. UIFont.preferredFont(forTextStyle: .body). When linking with the Xcode 27 beta 3 SDK, the two-level namespace bind for _UIFontTextStyleBody in my binary points at AppKit, i.e. the beta SDK's AppKit.tbd declares (re-exports) the UIKit text-style constants for Catalyst. But the shipping OS doesn't provide that: on macOS 26.5.1, _UIFontTextStyleBody is absent from both the installed AppKit binary (checked with dyld_info -exports /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit) and the Xcode 26.5 GA SDK's AppKit.tbd. So any binary linked against the beta SDK hard-binds the symbol to AppKit and then fatally fails to bind on current GA macOS — a 100%-reproducible launch crash for every user not on the macOS 27 beta. Steps to reproduce Mac Catalyst target that uses any UIFont.TextStyle constant (e.g. .preferredFont(forTextStyle: .body)). Archive with Xcode 27 beta 3 and distribute via TestFlight. Launch on macOS 26.5.1 → immediate dyld abort with the report above. Questions Is this a known issue with the macOS 27 beta SDK's AppKit re-export list? It looks like these UIKit constants are being moved/re-exported through AppKit in the 27 cycle, but without availability/weak-linking info that would let binaries back-deploy to macOS 26. Is the intended behavior that Catalyst apps built with the 27 beta SDK simply can't run on macOS 26? If so, should App Store Connect / TestFlight have rejected or flagged the upload?

It is not possible to log into my Claude account in Xcode 27 beta 1 for the coding intelligence chat. When I click "Sign In," the browser opens, I authorize, the browser closes, and that's it. Nothing happens. Xcode does not recognize the login. I'm on MacOS 26.4.1 (25E253) and using Xcode 27.0 beta (27A5194q)

When trying to log into the Codex Plugin from Xcode, on the auth.openai.com site I can not progress. No option will progress from that page. Not: Continue with eMail Continue with Microsoft Continue with Apple Continue with Google Continue with phone number Is this a Safari (27.0, 22625.1.22.11.4) issue, or an OpenAI issue?

I am testing an existing iOS app with Xcode 27 beta 3. The build succeeds, but I am seeing a new linker warning from Swift Package product targets. ld: warning: address=0xF496F points before section(28) start and the target atom is ambiguous Environment: Xcode 27.0 beta 3 Build version: 27A5218g Platform: iOS Simulator Configuration: Debug Project type: iOS app with Swift Package dependencies, also embedding a watchOS app Build command: DEVELOPER_DIR=/Applications/Xcode-beta.app/Contents/Developer \ xcodebuild -project MyWeight/MyWeight.xcodeproj \ -scheme MyWeight \ -configuration Debug \ -destination "generic/platform=iOS Simulator" \ build The build succeeds: ** BUILD SUCCEEDED ** Warnings: MyWeight/MyWeightKit/Package.swift: MyWeightKit-watchOS-product: ld: warning: address=0xF493F points before section(28) start and the target atom is ambiguous MyWeight/MyWeightKit/Package.swift: MyWeightKit-iOS-product: ld: warning: address=0xF496F points before section(28) start and the target atom is ambiguous Both warnings appear during the link step for Swift Package product framework targets. Is this a known issue in Xcode 27 beta 3? Does it indicate a real issue in the produced simulator binary, or is it likely a linker/debug-info diagnostic?

Xcode tells me Previewing in executable targets now requires a new build layout for unoptimized builds. Either set ENABLE_DEBUG_DYLIB to YES for this target, or break out your preview code into a separate framework with its own scheme. How do enable that in Package.swift. swiftSettings don't work (.define and unsafeFlags with -D ...). Creating a library product that the executable then depends on doesn't help either. I have two targets, one is an executable target. The #Preview macro is in the non-executable target.

Problem statement: The Claude Agent component for currently installed by Xcode 26.6 or 27.0 Beta 3 is 2.1.175 which doesn't appear to support the Claude Apps Gateway (see code.claude.com/docs/en/claude-apps-gateway) Versions from 2.1.198 are required. Net effect is that when your organisation switches to the app gateway Xcode's Claude integration no longer works due to the lack of support in the installed component. Questions: Given the component is a signed binary is there any other way to use the locally installed Claude cli (current version 2.1.202)? When is an update expected? Is there any consideration for the rapid evolution of these agents to prevent blocking issues like this?

I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.