Has anyone notices persistent UI lockups when attempting to perform even the most basic tasks with Claude Code? I'm at a total loss here. I've noticed that the lockups tend to happen more often when the Claude Agent is asking me a question. I've tried removing stale data, disconnecting / reconnected the agent, force quit and restart. Nothing solves this.

Hi, I’m trying to test an independent watchOS app on an Apple Watch Series 6 Cellular that is set up for a child using Apple Watch For Your Kids (Family Setup). My current environment: Apple Watch Series 6 Cellular watchOS 26.6 The Watch is set up for a child using Apple Watch For Your Kids / Family Setup Xcode 26.6 Parent iPhone running iOS 27.0 Developer Mode is enabled on the parent iPhone The Family Setup Watch does not appear as a development device in Xcode/CoreDevice There is no Developer Mode option visible on the Family Setup Watch For comparison, I also have another Apple Watch used for normal development, and that Watch can be detected by the development environment. The issue appears specific to the child’s Family Setup Watch. I would like to understand the Apple-supported development and testing workflow for this configuration. Specifically: Is an Apple Watch set up using Apple Watch For Your Kids / Family Setup expected to be available as a direct Xcode development device? If direct Xcode deployment is not supported, can an independent watchOS app be installed and tested on a Family Setup Watch through TestFlight? If TestFlight is supported, what is the correct workflow for installing the beta on the child’s Family Setup Watch / child Apple Account? Is there another Apple-supported testing or distribution method developers should use for this scenario? I’m specifically asking about an independent watchOS app that can operate without the parent iPhone nearby, rather than a Watch app that depends on an iPhone companion app. I’d also appreciate clarification on the distinction between direct Xcode development deployment and TestFlight/App Store distribution for Apple Watch For Your Kids. Thank you.

Hello, I am playing around with MailKit in Xcode... just created a new App with MailExtension target. When I run it, it's asking if I want to test it with Mail, however, I cannot see the extension in the Mail Settings for enabling it... I a totally newbie here.... what am I missing?

Hi, I’m testing the new NowPlaying framework on iOS 27 using Xcode 27 and an iPhone 17 Simulator, and I’m seeing some behavior that I’m trying to determine is a Simulator issue or something incorrect in my implementation. I have a local AVPlayer playing an MP3 and a MediaSession conforming to MediaSessionRepresentable. The session publishes MusicContent with static artwork, AnimatedArtwork using the .tall aspect ratio, a MediaPlaybackSnapshot, and commands for play, pause, previous, next, and seek. The strange behavior is: I start playback and call requestToBecomeApplicationPrimary(). It succeeds and isApplicationPrimary becomes true, but isSystemPrimary remains false. I lock the Simulator for the first time. There is no Now Playing UI or metadata. I unlock it and return to the app. After recreating/re-registering the MediaSession and calling requestToBecomeApplicationPrimary() again, isSystemPrimary sometimes becomes true. When I lock the Simulator a second time, the Now Playing UI finally appears and the animated 3:4 artwork works correctly. However, the Lock Screen card still does not show the expected play/pause/previous/next buttons. It only shows the title, artist, progress bar, and volume control, despite those commands being included in commands. When the second session succeeds, the framework also starts requesting the artwork as expected: applicationPrimary: true systemPrimary: true Animated preview requested: (1206, 1608) ratio: tall Static artwork requested Animated video requested: (1206, 1608) ratio: tall Calling requestToBecomeSystemPrimary() directly has also consistently returned: internalFailure Playback itself continues correctly throughout all of this. So I’m trying to understand whether anyone else is seeing similar behavior with the iOS 27 Simulator: MediaSession becoming application-primary but not system-primary on the initial playback Now Playing metadata only appearing after a lock/unlock/re-registration cycle media commands being supplied but playback buttons missing from the Lock Screen requestToBecomeSystemPrimary() returning internalFailure I have not yet tested the same build on a physical iOS 27 device, so I’m particularly interested in whether this is currently a known Simulator limitation/bug or whether there is another step required when publishing a local playback MediaSession. Thanks!

We need guidance regarding the Python runtime bundled with Apple Command Line Tools. Environment: macOS Tahoe 26.5.2 (25F84) Xcode 26.6 (17F113) Device type: Mac Command Line Tools Python path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/ Version confirmed locally with: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/bin/python3 --version Output: Python 3.9.6 Our vulnerability-management platform, Qualys, reports this Apple Command Line Tools Python runtime as vulnerable under QID 387170, referencing CVE-2022-4303 and CVE-2023-0286. The detection points to: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/Resources/Python.app My understanding is that this runtime is bundled and managed by Apple as part of Command Line Tools, and that manually replacing or modifying this framework is not a supported remediation path. Installing a separate standalone Python version also does not remediate the finding at this Apple-managed path. Could Apple or the community confirm the supported approach for this scenario? Specifically: Is Python 3.9.6 intentionally bundled with the current Command Line Tools release for this macOS/Xcode version? Has Apple applied security fixes or backports to this bundled Python runtime that are not reflected in the upstream Python version number? Is updating Command Line Tools/Xcode the only supported remediation method for this component? Is manually replacing or modifying the bundled Python framework unsupported? Is there any known mitigation or official guidance for vulnerability-management exceptions while waiting for an Apple-provided update? I have also filed this through Feedback Assistant: FB23893693. Any official Apple guidance or reference to existing documentation would be very helpful, as we need to provide an auditable response to our internal security and audit teams.

Whenever I click the blue project button below for my ios application (in an attempt to get to Signing & Capabilities), my Xcode application crashes. I've tried the following: Deleting xcuserdata folder under project.xcworkspace Purging derived data in ~/Library/Developer/Xcode/DerivedData Clearing Xcode preferences with defaults delete com.apple.dt.Xcode

I like to use Window Tabs, setting them up with appropriate panels when working on SwiftUI views, writing tests, etc. Many times now, I open a project in Xcode only to discover the main window is very small, what was expanded in the project outline is incorrect, and the window tab bar is hidden. Showing the window tab bar then just shows a single empty tab named "New Editor". Since I didn't add any new files today or change project settings (nothing would have changed the .xcodeproj package of files), I restored a backup and that opened up a-ok. Though I first saved the bad project. In analyzing differences between the two .xcoeproj files, I can only imagine this an issue with UserInterfaceState.xcuserstate. Though it's not practical at all to see what the changes are due to different ordering. I did notice that the bad .xcodeproj version had a massive Base64 encoded block for some IDENavigatorModeSolitary entry. The working project had a much smaller encoded block. Anyone else run into this? For those that are now using the new JSON project files, has this still been an issue?

Hi Team, My Mac has already been upgraded to macOS 27 and currently has Xcode 27 installed. However, I have a development requirement to use Xcode 26.5 as well. Is there any supported way or workaround to install and run Xcode 26.5 on macOS 27? If it is not supported directly, what would be the recommended approach to use Xcode 26.5? Thanks, Reshma

Hello I cannot seem to get past the final step in pairing my Ultra Watch 3 to Xcode 27 RC1.. I have tried this on a Mac Mini M4 and a Mac M1.. Both Macs are running 26.6.2 In both cases, XCode seems my iPhone and I am able to deploy to that physical iPhone. I have my iPhone connected via a USB cable. When going into Developer Mode on the watch and then opening up the "Pair Nearby Device" in Device Hub, I can see either my M1 or my M4 (depending on which one is trying to connect), I can select it, it asks for a pass code and then asks me to pair. When I do, it simply returns back to the previous screen asking if I'd like to pair again.. Any ideas ?

Hello all, Yesterday, I found out that there's 60GB's of old simulator volumes on my mac in /Library/Developer/CoreSimulator/Volumes/. When I try to delete those through Xcode Settings -> Components under Other Installed Platforms, it looks like they are deleted, but after restarting my Mac, they simply return. I tried the solution proposed here (which is to delete the dmg files in /Library/Developer/CoreSimulator/Images/), but in my case, there are no dmg files in there. So it looks like they were properly deleted, unlike those in /Library/Developer/CoreSimulator/Volumes/. I could obviously try to delete the dmg files in /Library/Developer/CoreSimulator/Volumes/, but that doesn't work according to a post on reddit that I'm not allowed to show here (It's called 'Deleted 240GB of Xcode simulators multiple times but they keep remounting - how do I permanently remove them?') And I wonder if it's a safe thing to do. Do you have any suggestions for how to remove the old volumes correctly and permanently?

It looks like the other thread got locked. I would still like to be able to uncheck the box for "Connect via network" so I can develop with my iOS 17+ devices normally with Xcode 15. Or a method to use Xcode 14 with iOS 17+ without CoreDevice or whatever the problematic API is.

For the life of me, I cannot find how to bring up the Siri Remote in the Apple TV Simulator in Xcode 27 Device Hub (Beta). Is it no longer available? I have always seem to have had issues using the computer's keyboard for navigating my tvOS apps. Maybe it's me, but the Siri Remote always worked perfectly fine. I hope the remote will make a reappearance in the next beta... ?

Hello, I noticed that iPhone 18 series devices are missing from DeveloperDiskImages in Xcode 27.1 beta 1. I checked /Library/Developer/DeveloperDiskImages/iOS_DDI/Restore/BuildManifest.plist and found no entries for iPhone 19,x in SupportedProductTypes. Could this be due to downloading the wrong version of Xcode, or is there another reason? Latest iPhone type is iPhone18,5, here is the content of BuildManifest.plist from Xcode 27.1 beta 1: <key>ManifestVersion</key> <integer>0</integer> <key>ProductBuildVersion</key> <string>27A9269</string> <key>ProductVersion</key> <string>1.0</string> <key>SupportedProductTypes</key> <array> <string>ComputeModule13,1</string> <string>ComputeModule13,3</string> <string>ComputeModule14,2</string> <string>Mac14,14</string> <string>iPad11,1</string> <string>iPad11,2</string> <string>iPad11,3</string> <string>iPad11,4</string> <string>iPad11,6</string> <string>iPad11,7</string> <string>iPad12,1</string> <string>iPad12,2</string> <string>iPad13,1</string> <string>iPad13,10</string> <string>iPad13,11</string> <string>iPad13,16</string> <string>iPad13,17</string> <string>iPad13,18</string> <string>iPad13,19</string> <string>iPad13,2</string> <string>iPad13,4</string> <string>iPad13,5</string> <string>iPad13,6</string> <string>iPad13,7</string> <string>iPad13,8</string> <string>iPad13,9</string> <string>iPad14,1</string> <string>iPad14,10</string> <string>iPad14,11</string> <string>iPad14,2</string> <string>iPad14,3</string> <string>iPad14,4</string> <string>iPad14,5</string> <string>iPad14,6</string> <string>iPad14,8</string> <string>iPad14,9</string> <string>iPad15,3</string> <string>iPad15,4</string> <string>iPad15,5</string> <string>iPad15,6</string> <string>iPad15,7</string> <string>iPad15,8</string> <string>iPad16,1</string> <string>iPad16,10</string> <string>iPad16,11</string> <string>iPad16,2</string> <string>iPad16,3</string> <string>iPad16,4</string> <string>iPad16,5</string> <string>iPad16,6</string> <string>iPad16,8</string> <string>iPad16,9</string> <string>iPad17,1</string> <string>iPad17,2</string> <string>iPad17,3</string> <string>iPad17,4</string> <string>iPad5,1</string> <string>iPad5,2</string> <string>iPad5,3</string> <string>iPad5,4</string> <string>iPad6,11</string> <string>iPad6,12</string> <string>iPad6,3</string> <string>iPad6,4</string> <string>iPad6,7</string> <string>iPad6,8</string> <string>iPad7,1</string> <string>iPad7,11</string> <string>iPad7,12</string> <string>iPad7,2</string> <string>iPad7,3</string> <string>iPad7,4</string> <string>iPad7,5</string> <string>iPad7,6</string> <string>iPad8,1</string> <string>iPad8,10</string> <string>iPad8,11</string> <string>iPad8,12</string> <string>iPad8,2</string> <string>iPad8,3</string> <string>iPad8,4</string> <string>iPad8,5</string> <string>iPad8,6</string> <string>iPad8,7</string> <string>iPad8,8</string> <string>iPad8,9</string> <string>iPhone10,1</string> <string>iPhone10,2</string> <string>iPhone10,3</string> <string>iPhone10,4</string> <string>iPhone10,5</string> <string>iPhone10,6</string> <string>iPhone11,2</string> <string>iPhone11,4</string> <string>iPhone11,6</string> <string>iPhone11,8</string> <string>iPhone12,1</string> <string>iPhone12,3</string> <string>iPhone12,5</string> <string>iPhone12,8</string> <string>iPhone13,1</string> <string>iPhone13,2</string> <string>iPhone13,3</string> <string>iPhone13,4</string> <string>iPhone14,2</string> <string>iPhone14,3</string> <string>iPhone14,4</string> <string>iPhone14,5</string> <string>iPhone14,6</string> <string>iPhone14,7</string> <string>iPhone14,8</string> <string>iPhone15,2</string> <string>iPhone15,3</string> <string>iPhone15,4</string> <string>iPhone15,5</string> <string>iPhone16,1</string> <string>iPhone16,2</string> <string>iPhone17,1</string> <string>iPhone17,2</string> <string>iPhone17,3</string> <string>iPhone17,4</string> <string>iPhone17,5</string> <string>iPhone18,1</string> <string>iPhone18,2</string> <string>iPhone18,3</string> <string>iPhone18,4</string> <string>iPhone18,5</string> <string>iPhone8,1</string> <string>iPhone8,2</string> <string>iPhone8,4</string> <string>iPhone9,1</string> <string>iPhone9,2</string> <string>iPhone9,3</string> <string>iPhone9,4</string> <string>iPod9,1</string> <string>iSim1,1</string> </array>

I am unable to debug an iOS 27 device using Xcode 26. I can not currently update Xcode so I'm stuck with it for the time being. There used to be the hack where you could copy the newer /Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport into the older Xcode, but that path doesn't exist in Xcode 27. Is there any way to debug an iOS 27 device using Xcode 26? Currently I see "Insufficient metadata to manage symbols" in Devices & Simulators for that connected device.

Dear Friends, Is there a way to increase font size of xcode intelligence window? So the text i write, and the AI response. Why do i need this? I am using 4K monitor and i dont want to make Display setting bigger and lose all screen space.

Starting with Xcode 27, my attempt to start a debug session for my C++ project fails. The Run scheme used has the Console setting configured for "Terminal" fails. The Terminal opens, but there appears to be a failure in the execution of the 'darwin-debug' command in the shell spawned for the debug session: Here's the output in the Terminal: Last login: Sat Sep 19 13:46:54 on ttys001 /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en% paulrockwell@Upstairs ~ % /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en There appears to be a missing single quote in the command line, but if I complete it, darwin-debug fails to start with the following error message: darwin-debug: option `--en' requires an argument This worked on Xcode 26. Any thoughts on what might have changed and can I update the project to get around this? This issue is happening on any C++ project that I've created on prior versions of Xcode. And yes, I need to debug operation of one of the projects using the Terminal - the one project I'm interested in is GNU APL, which makes heavy use of terminfo and alternate character sets in its operation.

xcode cannot startup xcode cloud.

I'm trying to test on the new iPhone Duo simulator (Xcode 27.1 beta), but I cannot find a way to unfold the device anywhere in the Device Hub. The floating posture widget that is supposed to appear at the bottom center of the window simply isn't rendering for me. I thought it might just be hidden, but I've combed through the entire macOS menu bar (Device, Controls, View, etc.) and the options to change the fold state are completely absent from the dropdowns as well. Has anyone else run into this UI bug? Is there a hidden setting to toggle the posture controls back on, or a keyboard shortcut to force the simulator into its flat full-screen state in the meantime? Any help is appreciated!

I have been struggling with this for a while and have gone through every solution I have found on the forums, so I am hoping someone at Apple or in the community can shed some light on the actual root cause. Setup Mac: macOS 26.7 (Build 25G229) Xcode: 26.2 (Build 17C52) — also tried 16.8 and 26.0, same result Device: iPhone SE (3rd generation), iPhone14,6 — iOS 26.7 (Build 23H24) Developer Mode: enabled on device Pairing state: paired, tunnel connected The error When I connect my iPhone via cable, Xcode initiates pairing and device preparation, then immediately fails with: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Unable to find a valid DDI for the iOS platform. Run 'devicectl list preferredDDI' from the command line to get more details. User Info: { DVTErrorCreationDateKey = "2026-09-22 17:14:25 +0000"; DeviceIdentifier = "3B75FE83-5833-53B2-8ABE-9AA65A22A1C8"; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } Underlying errors: Code 12001 — Unable to find a valid DDI for the iOS platform. Code 12007 — Unable to find a developer disk image to use for the iOS platform (variants: Internal, Public). Diagnosing: no DDIs found for any platform Running the suggested command: xcrun devicectl list preferredDDI Output: Failed to load provisioning parameter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 "No provider was found." UserInfo={NSLocalizedDescription=No provider was found.} Host CoreDevice version: 518.27 WARNING: No DDI was found for the iOS platform. No DDI was found for the macOS platform. No DDI was found for the tvOS platform. No DDI was found for the watchOS platform. No DDI was found for the visionOS platform. The key signal here is Code=1002 "No provider was found." — this same error appears as a prefix in every devicectl command I run, regardless of the subcommand. I suspect this is the actual root cause, not a secondary issue. Additionally, /Library/Developer/DeveloperDiskImages does not exist on this machine. What I have already tried xcrun devicectl manage ddis update Updating host DDIs at /Library/Developer/DeveloperDiskImages The following directories provided candidate DDIs: /Library/Developer/CoreDevice/CandidateDDIs /Applications/Xcode-26.2.0.app/Contents/Resources/CoreDeviceDDIs After cleaning and updating the installed host DDIs in /Library/Developer/DeveloperDiskImages are equivalent to the original set. The command completes without error, but /Library/Developer/DeveloperDiskImages is still never created. Reinstalling Xcode system resources: sudo installer -target / -pkg $(xcode-select -p)/../Resources/Packages/XcodeSystemResources.pkg No change. Multiple Xcode versions — tested with 16.8 and 26.0 in addition to the current 26.2. Same failure across all. Multiple iOS versions on the device — the iPhone has been factory reset several times and tested on different iOS 26.x builds as Apple released them. Issue persists on all versions. Confirmed xcode-select -p points to the active Xcode installation and xcrun resolves tools correctly. Device info (for reference) xcrun devicectl list devices Name Identifier State Model iPhone de Carlos 3B75FE83-5833-53B2-8ABE-9AA65A22A1C8 connected (no DDI) iPhone SE (3rd generation) The device pairs and tunnels fine. The only blocker is DDI services (ddiServicesAvailable: false). Questions What does Code=1002 "No provider was found." actually mean in the context of devicectl? Is there a provisioning service or entitlement missing on the Mac side? Why does devicectl manage ddis update report success but never create /Library/Developer/DeveloperDiskImages? Is there a prerequisite directory or permission that needs to exist first? Is there a way to manually force-install the DDIs from the Xcode bundle, bypassing the update mechanism? Any guidance would be greatly appreciated. Happy to run additional diagnostics if needed.

Xcode 16 and 26 changes in painful way how the Tab key works during autocomplete. Previously, pressing Tab would extend the typed text up to the word match. For example, we have two classes: NSViewController and NSViewCoordinator BEFORE, typing: "NSV" + Tab used to complete to NSViewCo Now, in Xcode 26, pressing Tab just use the first suggestion. Stupidly. Especially when you want DispatchQueue and it gaves you DispatchSemaphore… That is very inconvenient because very often I want just see all possible cases with some prefix...without need of typing all prefix manually. How to restore the previous behavior? How to do autocomplete word-by-word?