According tho Claude, The crash is clearly a bug in Xcode's built-in AI chat feature (IDEIntelligenceChat), not an authentication issue or anything on your end. What the crash log shows: The crash is happening in IDEIntelligenceChat — specifically in ChatInputEditorView.updateView and SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. It's a SIGTRAP (assertion/precondition failure) triggered while SwiftUI is trying to lay out the AI chat panel. This is an Apple bug in Xcode 26.2 itself.

After updating to Xcode 26.4 (public release), I’m no longer able to paste from the Mac clipboard into the Simulator. Automatically Sync Pasteboard is on, and I have content on the clipboard, but paste doesn’t work—Cmd+V does nothing, and there’s no Paste option in the context menu. Is anyone else seeing this?

Hi everyone, yesterday I updated my macOS and Xcode to the latest versions and today I have the strangest thing: Canvas is always crashing whenever I click it, in any and all my Projects. The full Simulator works just fine; only the Preview Canvas crashes. All the crash reports say it's because of AXRemoteElement-BackgroundFetch, and ChatGPT says it's not because of my code. These are very simple Projects, just for experimentation. Nothing complex, just native code while I follow examples in a SwiftUI book. Anyone else having this issue? Translated Report (Full Report Below) ------------------------------------- Process: PreviewShell [2179] Path: /Volumes/VOLUME/*/PreviewShell.app/PreviewShell Identifier: com.apple.PreviewShell Version: 16.0 (23.40.29) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [1405] Coalition: com.apple.CoreSimulator.SimDevice.E9525D59-3C07-43F9-ACC9-18CF5DD0DAA1 [1516] Responsible Process: SimulatorTrampoline [1120] User ID: 501 Date/Time: 2026-03-26 15:00:02.6060 +0200 Launch Time: 2026-03-26 14:57:33.8870 +0200 Hardware Model: Mac17,9 OS Version: macOS 26.4 (25E246) Release Type: User Crash Reporter Key: 1DC4EA68-804A-D651-804B-C2E0C13D9B87 Incident Identifier: F3F1A52F-AFF9-4470-A216-7364FCB5B7E6 Time Awake Since Boot: 1100 seconds System Integrity Protection: enabled Triggered by Thread: 4, Dispatch Queue: AXRemoteElement-BackgroundFetch Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000016b6bfff0 Exception Message: Could not determine thread index for stack guard region Exception Codes: 0x0000000000000002, 0x000000016b6bfff0 Termination Reason: Namespace SIGNAL, Code 10, Bus error: 10 Terminating Process: exc handler [2179]

Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary workaround, what would be the impact if Apple later removes support for this flag, especially with newer iOS versions (e.g., iOS 26+)? For users who already have the app installed with this flag enabled For users installing the app for the first time after such changes

Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with "Logic Testing Unavailable." The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Build.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ build-for-testing Run tests without building: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Test.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ test-without-building Note: xcodebuild test (combined build and test) also fails with the same error. Expected result: The hosted unit tests run successfully on the connected physical device, as they do under Xcode 26.2. Actual result: Step 1 (build-for-testing) succeeds. Step 2 (test-without-building) fails immediately (within ~1 second) with: 2026-03-26 11:23:28.683 xcodebuild[51930:731004] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:28.725 xcodebuild[51930:730966] [MT] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:29.239 xcodebuild[51930:730966] Writing error result bundle to /var/folders/jl/knmkq18x4cg_3w087zgpfldm0000gn/T/ResultBundle_2026-26-03_11-23-0029.xcresult xcodebuild: error: Failed to build project TestProject with scheme TestProject-UnitTests.: Cannot test target “redacted” on “redacted”: Logic Testing Unavailable Logic Testing on iOS devices is not supported. You can run logic tests on the Simulator. Why this looks like an Xcode regression: The same project and same physical iOS 16.0.3 device work under Xcode 26.2. Under Xcode 26.4, build-for-testing still succeeds, so signing, provisioning, and bundle construction appear valid. The failure happens only when Xcode plans or launches the on-device test run. Before the failure, Xcode 26.4 logs: DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. A newer physical device running iOS 26.3 works under Xcode 26.4 without this warning. The issue also reproduces with a minimal standalone Xcode project, which makes a project-specific configuration problem unlikely. The Xcode-generated .xctestrun files for the passing Xcode 26.2 case and failing Xcode 26.4 case are structurally equivalent, making an .xctestrun format difference unlikely to be the cause.

After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme <SchemeName> build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.

With the latest Xcode 26.4 my project fails to compile due to a "compiler unable to type-check in reasonable time" error with a library I've been using for years and has not changed. The library is https://github.com/ngageoint/mgrs-ios and is specifically around this line https://github.com/ngageoint/mgrs-ios/blob/master/mgrs-ios/utm/UTM.swift#L96. Since this isn't my library I can't change it, but again we've been using this library for years now without issue - it was only when Xcode updated this morning that our compilation workflow broke. (Compilation machine is an M3 Pro with 18GB of RAM, so I don't think that's the problem here)

I submitted this to Feedback Assistant as FB22331090 and wanted to share a minimal reproducible example here in case others are seeing the same issue. Environment: Xcode 26.4 or Xcode 26.3 Apple Swift version 6.3 (swiftlang-6.3.0.123.5 clang-2100.0.123.102) Effective Swift language version 5.10 Deployment target: iOS 17.0 The sample app builds successfully for normal development use, but archive fails. The crash happens during optimization in EarlyPerfInliner while compiling the synthesized deinit of a nested generic Coordinator class. The coordinator stores a UIHostingController. Minimal reproducer: import SwiftUI struct ReproView<Content: View>: UIViewRepresentable { let content: Content func makeUIView(context: Context) -> UIView { context.coordinator.host.view } func updateUIView(_ uiView: UIView, context: Context) { context.coordinator.host.rootView = content } func makeCoordinator() -> Coordinator { Coordinator(content: content) } final class Coordinator { let host: UIHostingController<Content> init(content: Content) { host = UIHostingController(rootView: content) } } } Used from ContentView like this: ReproView(content: Text("Hello")) Steps: Create a new SwiftUI iOS app. Set deployment target to iOS 17.0. Add the code above. Archive. Expected result: Archive succeeds, or the compiler emits a normal diagnostic. Actual result: The Swift compiler crashes and prints: "Please submit a bug report" "While running pass ... SILFunctionTransform 'EarlyPerfInliner'" The crash occurs while compiling the synthesized deinit for ReproView.Coordinator. Relevant log lines from my archive log: line 209: Please submit a bug report line 215: While running pass ... EarlyPerfInliner line 216: for 'deinit' at ReproView.swift:19:17 One more detail: The same sample archived successfully when the deployment target was higher. Lowering the deployment target to iOS 17.0 made the archive crash reproducible. This may be related to another forum thread about release-only compiler crashes, but the reproducer here is different: this one uses a generic UIViewRepresentable with a nested Coordinator storing UIHostingController.

Was working before, no longer working this week. Trying to sign in to my Claude Pro account via Xcode Intelligence. Goes to browser, I login, and accept authorization in Claude then redirect back to Xcode is reject. Everytime, multiple browsers, and even trying the add "/" that others have noted for other cases.

Hi. Our IT security team have flagged that on many developer machines they see a deprecated version of Python - 3.9.6. I've done some research on this and the general line is, feel free to upgrade the main version of Python on the Mac, but the version of Python which is internally used by Xcode (3.9.6) must be left unchanged. Our IT security team reached out to Apple and have received conflicting information as to if this Ruby 3.9.6 version can be upgraded. One response for example was "I asked my Solutions Engineer and he has come back with the following: We don’t include Python within macOS anymore, we install 3.9.6 with Xcode to support some of the internal tools - but there’s nothing preventing a customer updating that version: https://mac.install.guide/python/update". Does anyone know if it is possible to upgrade to a supported version? Kind regards, Kai.

Hi, On a 1920 points wide monitor, running maximized, Xcode 26.4 can't show more than 10 editor tabs at a time. Under the same conditions, Xcode 26.2 adapts tab widths to file names and fits 12-14 tabs. That's 2-4 more files I can see and access at a glance, without extra interaction. How can I get that level of information density back in the Xcode 26.4 editor tab bar? Screenshots Xcode 26.4 (10 tabs) Xcode 26.2 (12 tabs) Xcode 26.2 (14 tabs)

After updating to Xcode 26.4 the pasteboard sharing feature in the simulators doesn't work.

Hi everyone, I'm working in a strictly offline (intranet) environment and cannot use the standard online installation process to download and install the Claude Agent for Xcode. What I've tried: I manually copied the Agent binary/folder from an online machine to the following path: ~/Library/Developer/Xcode/CodingAssistant/Agents/Versions/26.3/claude The Issue: Even though the files are in the correct directory, Xcode fails to recognize the agent. It doesn't appear in the settings, and the Coding Assistant remains unavailable. Questions: Is there a specific metadata file (e.g., a .plist or .json index) that needs to be updated for Xcode to "see" the manually added agent? Are there any code signing or quarantine issues (like xattr) that need to be addressed when moving the agent between machines? Does anyone know if there are other dependencies or cache folders (besides ~/Library/Developer/Xcode/CodingAssistant/) that need to be synchronized? Environment: macOS: 26.3 (25D122) Xcode: 26.3 (17C519) Any guidance on the manual registration process for these agents would be greatly appreciated. Thanks!

Every time I touch (add a key, remove a key, even add a key, then remove it) the Strings Catalog .xcstrings file, it re-renders the entire file and creates a 18 thousand line dif. When I looked closer, it changes the whitespace before colons! "version": "1.0" "version" : "1.0" it does so for every JSON node. This makes the whole feature useless, because we wont be able to see what we changed upon code review (diff is unprintable in the github interface) and every time we change a single translation, we will be stacking 18k lines diff. Not to mention merge conflicts?

0 0x1001bd52c __assert_rtn + 252 1 0x100132054 void std::__1::__introsort<std::__1::_ClassicAlgPolicy, ld::AliasAddressOrderer&, ld::Atom const**, false>(ld::Atom const**, ld::Atom const**, ld::AliasAddressOrderer&, std::__1::iterator_traits<ld::Atom const**>::difference_type, bool) + 0 2 0x1001319a4 ld::LayoutLinkedImage::assignAtomOffsetsInSection(ld::SectionLayout&, unsigned int, bool) + 680 3 0x100136724 void dispatchForEach<ld::SectionLayout*, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0>(std::__1::span<ld::SectionLayout*, 18446744073709551615ul>, unsigned long, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0)::'lambda'(unsigned long)::operator()(unsigned long) const + 7852 4 0x19dca8aec _dispatch_client_callout2 + 16 5 0x19dca37f8 _dispatch_apply_invoke3 + 336 6 0x19dca8ad4 _dispatch_client_callout + 16 7 0x19dc91a60 _dispatch_once_callout + 32 8 0x19dca2938 _dispatch_apply_invoke + 252 9 0x19dca8ad4 _dispatch_client_callout + 16 10 0x19dcc59dc _dispatch_channel_invoke.cold.5 + 32 11 0x19dca113c _dispatch_root_queue_drain + 736 12 0x19dca1784 _dispatch_worker_thread2 + 180 13 0x19de47e10 _pthread_wqthread + 232 ld snapshot written at /tmp/****app.debug.dylib-2026-03-24-092748.ld-snapshot ld: Assertion failed: (aliasSectionNum == sectionNum && "alias and its target must be located in the same section"), function assignAliasAtomOffsetInSection, file Layout.cpp, line 4805. clang: error: linker command failed with exit code 1 (use -v to see invocation) I want to submit an ld-snapshot attachment, but the "Add File" function in the posting section won't let me add any files. My macOS was upgraded from version 16 to 26.3, and my Xcode was upgraded from version 16.1 to 26.3. Please help me resolve this as soon as possible, thank you.

[Reply to DTS Engineer] Thank you for looking into this. I have identified the root cause of the issue: it is a Bundle ID case-sensitivity mismatch. My parent app was approved as com.hayashikento.FocusPact (Capitalized), but I accidentally requested the Configuration Extension with a lowercase ID (com.hayashikento.focuspact...). This causes a "Prefix Mismatch" error in Xcode, preventing me from archiving the app. To fix this, I have just submitted a new entitlement request with the corrected capitalized ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Since the core functionality was already approved under the lowercase ID, could you please expedite the approval for this capitalized version? This technical correction is the only thing blocking my TestFlight distribution. Thank you for your support!

I just installed Xcode 26.4 RC (17E192) yesterday and found that the documentation window now omits Foundation for me. Searching for "Date" finds the date property from GameKit, Core Data, ... but no Date type. I was previously using 26.4 beta and this was not the case. Is anyone else seeing the same thing?

Help please! I'm new to Xcode and my Mac is a 2021 MacBook Pro. I've downloaded Xcode recently (version 26.2) and wanted to preview and test my first App. But somehow, I just can't download the iOS simulator. People tell me that I can download resources from developer.apple.com, but I only found the iOS_18.2_runtime.dmg. I downloaded and installed the iOS 18.2 version but Xcode still requires to download the iOS 26.2 simulator. I don't know why and how to fix this problem. Please help!

I'm trying to use Xcode 26.3's official MCP Server (xcrun mcpbridge) on an Intel Mac（15.7.4）, but it crashes immediately. Run xcrun mcpbridge in Terminal： dyld[3809]: Symbol not found: _$s10AppSandbox17ASBBinaryIdentityC14teamIdentifierSSSgvg Referenced from: /Applications/Xcode.app/Contents/Developer/usr/bin/mcpbridge Expected in: /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox [1] 3809 abort xcrun mcpbridge Observations The same command works on an Apple Silicon Mac (M1, macOS 26.3).

Hello, I have a critical issue regarding the "Family Controls (Distribution)" entitlement. My app "FocusPact" was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a "Bundle identifier prefix mismatch" error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an already authorized functionality. Team ID: UHG4J7F7NH App Apple ID: 67591326449 Thank you for your assistance. I am a student developer eager to start MVP testing as soon as this is resolved.