Is anyone else using one of the "Dark" editor themes (such as "Default (Dark)" or "Classic (Dark)" in Xcode? And is anyone doing this with Xcode 26 on macOS 26? Here's the result while using the "Default (Dark)" theme while my Mac is in "light" mode: Note that the black background of the editor goes all the way to the far left edge of the Xcode window. The large gray area in the project tree is the black background bleeding through the sidebar. This is really distracting. Is there a way to fix this (besides not using a dark theme - I've been using dark themes for over 30 years)? This appears to be a poor design decision in macOS 26 to have split views show the background of the secondary column behind the primary column. iPadOS 26 has the same issue (see https://developer.apple.com/forums/thread/800073).

The Metal linker in the latest Xcode 27 Beta 5 is failing to link against the Core Image framework unless the current MACOSX_DEPLOYMENT_TARGET is set to macOS 27 Golden Gate Beta. MTLLINKER_FLAGS = -framework CoreImage It looks like the CoreImage framework that shipped in the Beta 5 SDK fails to include versions of CoreImage.metallib to support prior versions of macOS. If your current deployment target is, for example, macOS 13.5, the build log will show a warning: air-lld: warning: ignoring file '/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage.metallib', file AIR version (2.9) is bigger than the one of the target being linked (2.5) ...and produce this error: air-lld: error: symbol(s) not found for target 'air64_v25-apple-macosx13.5.0' metal: error: air-lld command failed with exit code 1 (use -v to see invocation) The above warning + error happen for any MACOSX_DEPLOYMENT_TARGET up to and including macOS 26. Only when setting it to macOS 27 does the linker succeed. Linking against the Core Image framework is required to package your own CIKernels that use Metal’s [[stitchable]] attribute, in lieu of the previous method based on: MTL_COMPILER_FLAGS = -fcikernel and MTLLINKER_FLAGS = -fcikernel. Has anyone else run into this very same issue? (Filed as FB24345950) Any workarounds you’d be willing to share? Would pulling an older version of the CoreImage framework from a previous SDK, and linking explicitly against it work too? Thanks! Gabe

I've filed a FB already through standard channels (FB ID: FB19032008) but I'll post it here in case it may get some attention from others experiencing similar issues. On macOS 26 Beta 5 and Xcode 26 Beta 5 (and earlier revisions afaik) Icon Composer specifies a minimum window size that greatly exceeds the bounds of the 1280x800/832pt video modes available on 13in MacBooks, and which also is too large for the default 1440x900 video mode on non-notched 13in MacBook Air/Pro models as this causes a default-size 64pt dock to occlude the window. I've attached screenshots depicting this behaviour in the two above described cases. Best solution seems like reducing min window size to something that will fit reasonably in a 1280x800pt viewport including the dock and menu bar (e.g. 1000x600 or something).

Does Xcode support the equivalent of 'git add -p' from Terminal? I noticed that if I use 'git add -p', Xcode will show me the lines that I have staged. But, I don't see a way to select the lines from within Xcode. GUI support for that git feature would be nice. Regards, Patrick

Can I use Windows 10 to develop IOS apps?

I've created a basic Multiplatform Project in Xcode, by going to File > New > Project. I've also included the default widget extension target. When I run the widget on Mac, and I control-click and choose "Edit Widget" the widget just kinda turns gray and floats over other windows, but does not let me configure anything. We leave the option to use configure with app intents turned on when adding the widget extension target. When I run the same project on an iPhone simulator, I can configure the widget without any issue. If someone else has a few minutes, can they see if this repeats for them? We are running this test because we are seeing the same experience in a real widget we are trying to develop but we can't get it to go into configuration mode on Mac.

Installing a development build on a physical iPhone fails with: 0xE8008018 - The identity used to sign the executable is no longer valid. On the same Mac, same iPhone, same codebase and same Xcode, switching to a free personal Apple ID team installs and runs with no error. Only builds signed with our paid organisation team fail. Nothing else changes between the two runs. We have already regenerated certificates and provisioning profiles, deleted the profiles folder, cleared DerivedData, removed old identities from the keychain, trusted the profile on device, and tried both automatic and manual signing. None of it changes the result. We have also gone through the existing threads on this error and none of the suggested fixes apply. The build validates locally but the device rejects the identity. Since the signing team is the only variable between success and failure, what should we be looking at? A support case is open with Developer Support but we have not had a technical response yet.

26.6 is officially out https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_6-release-notes but I can't fetch the newest simulator for Xcode this command also doesn't work xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.6 -> iOS 26.6 is not available for download can anyone download iOS 26.6 simulator? thx!

I'm unable to use the Claude Agent in Xcode 26 (stable release) running on macOS 27 beta 5. Steps to reproduce: Open Xcode 26 Settings > Intelligence Select Claude Agent Expected: The Account section loads and allows me to sign in / manage my Claude account. Actual: The Account row shows a loading spinner indefinitely and never resolves, so I can't sign in or use the Claude Agent at all. Environment: Xcode 26 (stable), macOS 27 beta 5. Is this a known incompatibility with macOS 27 beta 5? Is there a workaround (e.g. clearing a cache or re-adding the account) to get the Claude Agent account section to load?

Environment: MacBook Air M4 macOS 27 Golden Gate Beta Xcode 27 Beta iPhone running iOS 27 Beta Apple Watch Series 10 paired to the iPhone Steps to Reproduce: Install macOS 27 Beta and Xcode 27 Beta. Pair an Apple Watch with an iPhone running iOS 27 Beta. Enable Developer Mode on the iPhone. Connect the iPhone to the Mac and launch Xcode. Open Window → Devices and Simulators. Attempt to locate the paired Apple Watch or enable Developer Mode on the watch. Expected Result: The paired Apple Watch appears in Xcode for development purposes. A Developer Mode option is available on the Apple Watch. Xcode is able to recognize and communicate with the watch through the paired iPhone. Actual Result: The Apple Watch does not appear in Xcode. No Developer Mode option is visible on the watch. The iPhone is successfully paired and running iOS 27 Beta, but the watch remains unavailable for development workflows. Additional Notes: The iPhone and Apple Watch are already paired and functioning normally. Developer Mode is enabled on the iPhone. Restarting devices and reconnecting the iPhone did not resolve the issue. Unsure whether this is a limitation of the current beta builds or a regression in Xcode/watchOS development tooling.

Hello! I was recently trying out XCTHitchMetric with my MTKView and it doesn't seem to record anything. But if I use the Animation Hitches instrument then I do see the hitches get recorded when a frame is presented on screen later than expected. I'm curious if there is a reason for this or maybe I am missing something?

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

I constantly manually allow Codex to read Xcode 27 skills, but I don't want to allow it to read from any arbitrary directory, so I didn't enable always allow AgentRead. Question is in the title

MacBook Air (Apple silicon), macOS 26.6.2 (25G83). I have a persistent CoreSimulator/MobileAsset issue. I do not have an Xcode project, Simulator devices, or an active need for iOS Simulator runtimes. Using Apple’s signed CoreSimulator simctl binary, I removed iOS 18.4 (22E238) and iOS 18.5 (22F77) through the documented: simctl runtime delete workflow, after simctl reported each runtime as Ready, Verified, and Deletable. Immediately after deletion, the runtime registration and mounted runtime image disappeared. However, after a normal Mac restart or later CoreSimulator service activity, both runtimes reappear under new image UUIDs and are automatically mounted read-only again. The underlying Apple MobileAsset parents remain present and report NeverCollected: iOS 18.4 / build 22E238: about 8.9 GiB iOS 18.5 / build 22F77: about 8.9 GiB The related CoreSimulator dyld cache also rebuilds to about 7.1 GiB. I have not manually deleted protected Apple assets, killed Apple services, or modified mounts. The only removal attempted was Apple’s own simctl runtime delete command. Expected result: After a successful documented runtime deletion, the runtime should remain unregistered and unmounted, and the Apple-managed backing storage/cache should become reclaimable through a supported process. Observed result: The same runtime builds return after restart/service activity, with new UUIDs and automatic mounts, while their retained MobileAssets remain. Could Apple please advise why CoreSimulator/MobileAsset reconciliation is re-registering deleted runtimes, whether NeverCollected prevents supported cleanup, and what supported procedure can permanently remove or reconcile these unused runtimes? Useful read-only checks: SIMCTL_PATH=/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/Resources/bin/simctl "$SIMCTL_PATH" list runtimes "$SIMCTL_PATH" runtime list -v du -skx /Library/Developer/CoreSimulator/Caches/dyld

Hi everyone, I’m currently running macOS 27.0 beta (26A5388g) on my Mac, along with the latest Xcode 27 beta, and I’ve recently started experiencing a serious issue where multiple macOS system services are repeatedly crashing. Initially, I started getting repeated “intelligencetasksd quit unexpectedly” notifications. At first it happened occasionally, but it has now become extremely frequent. After dismissing one crash notification, another system service often crashes shortly afterward. I’ve also seen services related to Intelligence / intents crashing. The notifications keep appearing one after another to the point where I’m barely able to use the Mac normally — including difficulty typing and interacting with applications. The issue is not limited to Xcode. It appears to affect macOS system services themselves. System information Mac: Mac15,2 (Apple silicon) macOS: macOS 27.0 beta, build 26A5388g Xcode: Xcode 27 beta Issue started: After running the macOS beta for some time; it has progressively become more frequent Main process initially crashing: intelligencetasksd Path shown in crash report: IntelligenceTasksEngine.framework/Support/intelligencetasksd Exception: EXC_BREAKPOINT (SIGTRAP) I have attached a screenshot of the crash report showing the intelligencetasksd crash. Has anyone else experienced this on macOS 27 beta? Is there a known issue with the new Intelligence/Intents services, or is there a recommended way to reset/rebuild the relevant system components? At this point the repeated crashes are making the Mac extremely difficult to use, so I’d really appreciate any troubleshooting steps or information about whether this is a known beta issue. Thanks!

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

Hi, I have been using Claude with Xcode 26.1.1 and it was working fine till a couple of days ago, when it started giving me an error message on every query: "Message from Anthropic: This request would exceed your account's rate limit. Please try again later." I am on the Pro model, and I can use the Claude.ai website just fine. The usage limits on the website show I've used only 11% of the weekly limit, and 4% of the 'current session'. So I'm wondering if this is an Xcode bug / issue, and if there is a workaround. I have restarted Xcode, restarted the Mac, logged out of Anthropic and logged back in, tried Xcode 26.2 beta as well, but no luck.

There was an issue when we processed your order. Verify that your information is correct and try again. If you need further assistance contact us. Duplicate order

Hi, I’m new to Xcode and I’m wanting to publish a sticker app using the template. I have added all the stickers and icons and even tested in simulation, I also have registered the identity and app id but when I try to archive it I encounter two errors: _Communication with Apple failed Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/ and No profiles for ' ' were found Xcode couldn't find any iOS App Development provisioning profiles matching ' ‘_ my understanding is that I don’t really need to do anything else nor need a physical device. the bundle is identical in the app id.

26.6.2 (25G83) with Xcode Version 26.6 (17F113) can't find AI components What's up