Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.

Just installed the new Xcode 26.4 RC build (17E192) after happily using 26.3 for a few months. I'm noticing some immediate regressions in the Intelligence features: Frequent losing of OAuth token (Claude Agent). This had previously been fixed and now is back. Agent "Thinking" is constrained to thought bubble windows, which are (a) too small to read, (b) not scrollable when thinking goes beyond a few paragraphs. Yes they are tappable when thinking is finished, but this doesn't help. Due to (2), in deep thinking, it's impossible to follow progress beyond the visible window, so impossible to know if the agent is going off the rails. I'm noticing just more general slowness to complete tasks. Not just complete them -- it seems like it takes longer to START tasks, which is really weird. It sits there thinking for longer. Same project, same model as before. Every time you tap "New Chat" it presents both Claude and Codex choices, even if you're only signed into one. This turned a simple single tap into now a required two taps. Overall this feels like a frustrating setback after a very positive user experience in 26.3.

I've got a Project with a bunch of frameworks, each of which has a static library version of itself (for compiling command-line tools that also use the code). Compiling the frameworks goes fine. Compiling one of the static libraries (A Mime-parsing framework) is giving me the rather odd message that a bunch of symbols are ambiguous, but the ambiguity resolves to the same symbol in the error-message... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:57:18: error: reference to 'E3_SMIME_ENVELOPED_DATA' is ambiguous 57 | case E3_SMIME_ENVELOPED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ ... and again ... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:62:18: error: reference to 'E3_SMIME_SIGNED_DATA' is ambiguous 62 | case E3_SMIME_SIGNED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:18:2: note: candidate found by name lookup is 'E3_SMIME_SIGNED_DATA' 18 | E3_SMIME_SIGNED_DATA, // Signed data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:18:2: note: candidate found by name lookup is 'E3_SMIME_SIGNED_DATA' 18 | E3_SMIME_SIGNED_DATA, // Signed data | ^ ... and again, etc ... . No file inside the module (neither .m or .h) includes the module-header, the definition of the offending symbols looks like: // // E3AppPkcs7Part.h // E3Mime // #import <E3Mime/E3CryptoContext.h> #import <E3Mime/E3MimePart.h> #import <E3Mime/E3MimeMultipartEncrypted.h> NS_ASSUME_NONNULL_BEGIN typedef enum { E3_SMIME_COMPRESSED_DATA, // Compressed data E3_SMIME_ENVELOPED_DATA, // Enveloped data E3_SMIME_SIGNED_DATA, // Signed data E3_SMIME_CERTS_ONLY, // Only certificate data E3_SMIME_UNKNOWN, // Que ? } E3SMimeType; ... And when I click on the error adornment in the editor pane, the errors disappear. It still won't build the project, though. I just get the same errors the next time I press CMD-B. Can't upload a short screen-capture of that, so I put it the movie at http://0x0000ff.co.uk/mov/phantom-errors.mov.

I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) Text("Hello, world!") } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?

When working in parallel on 2 projects (i.e. a server and a client app project). The Claude Code agents in those projects should be able to communicate with each other to improve the flow of information (i.e. changes in models, DTOs). The developer should supervise the communication and can block, if necessary.

This just started happening today out of nowhere. Instead of only the project I’m working on appearing in Source Control, every project inside my Xcode projects folder is now showing up in the Source Control navigator. This is happening in both the Changes and Repositories tabs.

I would like to have the option to keep my xcode project open regardless of closing all tabs using cmd + w.

Hi, I am working on app at the moment that uses Icon Composer for all of its icons and variations. I want to add an iMessage App to my project however I get validation errors from App Store Connect even if I add an imessage app to my asset catalog and include all app icon assets. Is there any way to do this at the moment natively with Icon Composer? If not how do I manually overwrite the icon JUST for iMessage and not for my entire iOS app?

Can I download the iOS 26 simulator runtime via a download link? The machine I need to deploy on may require an offline package installation due to firewall restrictions.

Can I download the iOS 26 simulator runtime via a download link? The machine I need to deploy on may require an offline package installation due to firewall restrictions.

Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: "warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info." Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the "Generate dSYM" phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue persists regardless of these standard configuration fixes. Expected Result: Xcode should generate a populated dSYM file containing the debug symbols from the executable. Actual Result: An empty dSYM file is generated, making it impossible to symbolicate crash reports.

hello and thank you for reading . I am having an issue with getting my phone -13 pro max - into developer mode I have tried all the basic ways and have tried some with help from Ai. But still haven’t gotten my phone into dev mode? Any tricks the for sure work or what should I do ? There is another option I have t tried but don’t have my laptop or access to a computer currently. would very much app help with this thank you in advance .

I’m working on an iOS workspace with: a static library project: M800SDK a test app project: TestAppObj I was able to build M800SDK for iOS Simulator on Apple Silicon as a simulator static library, and I also verified the architectures in the produced .a file. However, when I link the app target against that simulator build and try to build TestAppObj for iOS Simulator, I get the following linker errors: Undefined symbols for architecture arm64: _OBJC_CLASS_$_TokenMngr clang++: error: linker command failed with exit code 1 Additional context: The library links and works correctly when building the app for a physical iPhone. And the public header TokenMngr.h is found correctly by the app target. The app target is compiled as Objective-C++ where needed. The library is linked in the app target under “Link Binary With Libraries”. Could you help me understand: Is it possible to run on iOS Simulator ? the recommended way to package and consume this library for iOS Simulator on Apple Silicon? Also I am aware i can also build the library for : Any iOS Simulator Device (arm64, x86_64) And specify that on Build Phases in Link : Link Binary With Libraries adding the .a Before i do that i ensure the .a is arm64, x86_64 using the command : lipo -info libM800SDK.a end it returns : Architectures in the fat file: libM800SDK.a are: x86_64 arm64 However, even after confirming those architectures and linking the library to the app target, the app still does not link correctly for iOS Simulator. In some cases, Xcode reports errors suggesting that the build is targeting iOS Simulator, but that one of the linked binaries was built for iPhoneOS instead. This is where I am confused: I understand that lipo -info only shows the CPU architectures present in the library, but not whether a given arm64 slice was built for iPhoneOS or for iOS Simulator

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?

Popular automated testing systems like FireBase [1] and WeTest [2] expect the uploaded test to include the Debug-iphoneos directory generated by Xcode. However, in all of our builds on Xcode 26.3, this folder is created but remains empty. There are some other folders with the same name in subdirectories, but these only contain intermediate build files. Now we're looking for configuration or settings in Xcode to restore the original behavior, where the top-level Debug-iphoneos directory gets populated with a complete image of the test target, include the binary and resource files. Any suggestions would be much appreciated! [1] https://firebase.google.com/docs/test-lab/ios/run-xctest [2] https://www.wetest.net/documents/detail/automation/d8yaA7yz

When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new SwiftUI App project using Xcode 26.3. Leave all project settings at default (Swift version 5). Set the iOS Deployment Target to iOS 16, 17, or 18. Use the following minimal code: import SwiftUI internal import Combine @MainActor class CommonViewModel<Item>: ObservableObject { @Published var listArray = [Item]() } class ContentViewModel: CommonViewModel<String> { func reloadData() { self.listArray = ["1"] } } struct ContentView: View { @StateObject private var viewModel = ContentViewModel() var body: some View { Color.clear .onAppear { viewModel.reloadData() } } } Build and run the app using the Release configuration.

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.

Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Control authentication or host fingerprint UI flow that never resolves. SSH connectivity itself is functioning correctly: ssh -T git@bitbucket.org and ssh -T git@github.com both authenticate successfully. git ls-remote, git fetch, git pull, and git push all work correctly from Terminal. No Source Control accounts are configured in Xcode Preferences. Authentication relies entirely on SSH keys. Steps to Reproduce Configure an SSH key for Git access (e.g., Bitbucket or GitHub) and confirm it works via Terminal. Clone or open an existing Git repository that uses SSH (git@host:repo.git). Open the project/workspace in Xcode. In Xcode, attempt a Source Control operation such as: Source Control → Pull Source Control → Push Observe that Xcode displays a spinning progress indicator and does not complete the operation. Logs available on this Feedback Assist ID: FB22146913

I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with "Failed to authenticate. API Error: 401 - Invalid bearer token" on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported upstream as a 401 authentication error — which is why the error has nothing to do with the actual credentials. APPLE'S RESPONSE Feedback report FB22141224 was closed as 'Works as currently designed' with the explanation that Claude Agent requires the Neural Engine found on Apple Silicon. However, Claude Agent calls Anthropic's remote API over the network and performs no on-device AI processing — the Neural Engine is not involved. The fact that Claude Code works fine on this same Intel Mac with the same credentials demonstrates this clearly. WORKAROUND Using an Anthropic API key instead of OAuth resolves the issue but requires additional paid billing outside of an existing Claude.ai subscription. Has anyone else experienced this on either Intel or Apple Silicon? I'd be particularly interested to hear if Apple Silicon users are also affected, as the Developer Forums suggest this may not be limited to Intel Macs (thread/816369). Any input from Apple DTS engineers would be greatly appreciated.

I’m constantly gettng 47 errors in my code and I’ve tried everything I can think of and can’t find the root problem, please can someone help