Claude Agent OAuth token silently expires and fails to refresh in Xcode 26.4 — requires manual re-auth every 12-24 hours. this was not happening in 26.3, its a regression in 26.4 Details and sysdiagnose submitted: FB22421882

I am unable to use my iPhone 17 Pro as a run destination in Xcode. The device appears at a low level, but CoreDevice / devicectl keeps reporting it as unavailable. Environment • Mac mini (Apple Silicon) • macOS 26.3 (Build 25D125) • iPhone 17 Pro • iOS 26.3 • Xcode 26.3 (Build 17C529) • Xcode 26.4 beta 2 (Build 17E5170d) Symptoms • The iPhone appears in Finder • On the iPhone, I tapped “Trust This Computer” • Developer Mode is enabled • Apple ID is added in Xcode Accounts • Team is configured in Signing & Capabilities • iOS Platform Support is installed • The device still does not become available as a run destination • Devices and Simulators does not show it in a usable state • xcrun devicectl list devices still shows unavailable Output of xcrun devicectl list devices Failed to load provisioning paramter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 "No provider was found." UserInfo={NSLocalizedDescription=No provider was found.}. devicectl manage create may support a reduced set of arguments. Name Hostname Identifier State Model CAC1B56A-C3B4-59FF-8F9D-659277C7C76C.coredevice.local CAC1B56A-C3B4-59FF-8F9D-659277C7C76C unavailable iPhone18,1 What I already tried • Apple cable • Different USB/Thunderbolt ports • Direct connection to rear ports • Restarted both Mac and iPhone • Restarted Xcode • Ran sudo killall usbmuxd • Ran sudo pkill -9 remoted • Upgraded Xcode from 26.2 to 26.3, then to 26.4 beta 2 • Ran sudo xcode-select -s /Applications/Xcode-beta.app • Ran sudo xcodebuild -runFirstLaunch • Reset “Location & Privacy” on the iPhone, then trusted the Mac again • Still remains unavailable Additional note ioreg shows the iPhone, so the physical USB connection seems to exist. However, at the CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run. Is this a known issue with macOS 26.3 / iOS 26.3 / Xcode 26.4 beta 2? Any workaround or additional debugging steps would be appreciated.

Hello! I'm new to xcode and am developing an iOS app. I hit the following error when build my app: MY_SHA no identity found Command CodeSign failed with a nonzero exit code I have generated my certificate through xcode. I can see the Certificate and the private key in Keychain -> login. But it's not that private key is under the Certificate. They are listed in parallel. The certificate appears in Certificate tab but not in My Certificate Tab. Would that matter? security find-certificate -a -Z | grep -A1 "Apple Development" Gives me the certificate. But security find-identity -v -p codesigning give 0 valid identity found. Could you help me figure out what could be the reason for this? I've been stuck for several days now. Thank you so much!

Since a combined upgrade to macOS 26.4 and Xcode 26.4 I am plagued by .DS_Store and UserInterfaceState files appearing in my repository list of uncommitted changes. This is preventing commits and merging etc. I have added the following list to both the .gitignore_global file via directly editing the file and also the Xcode>Settings>Git Settings>Ignore Files # Mac OS X .DS_Store # Xcode *.pbxuser *.mode1v3 *.mode2v3 *.perspectivev3 *.xcuserstate UserInterfaceState.xcuserstate project.xcworkspace/ xcuserdata/ # Generated files *.o *.pyc # Build directories DerivedData/ build/ # CocoaPods Pods/ # Carthage Carthage/ # Other *.swp *.lock This has been to no avail. I have raised Feedback FB22370688 for this issue. It has been marked as no similar reports which is odd because there are a lot of mentions of the .DS_Store files appearing in Git and also of problems with the ignore settings of Git. For a while, I successfully prevented the .DS_Store files from showing up as uncommitted changes but now they are back again. I did a git status on the project and got this output for a while Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: Target Analysis.xcodeproj/project.xcworkspace/xcuserdata/myuserid.xcuserdatad/UserInterfaceState.xcuserstate Ignored files: (use "git add -f <file>..." to include in what will be committed) Target Analysis iOS/ Target Analysis macOS/ Views/Testing/.DS_Store Now, in Xcode it looks like this So the .DS_Store files are no longer being ignored. I have raised an Apple Developer Tech Support (DTS) Question as I have exhausted every avenue that I could find. DTS said to just remove the file(s) in Git. Neither this nor the .gitignore_global file are fixing the problem. This all just seems to be so unnecessarily difficult especially as many others have faced the same problem.

I just submitted a feedback for this (FB9662125) but in the spirit of “share and enjoy”… The cool new Generate Info.plist File feature in Xcode 13 crashes if you try to put an NSLocationTemporaryUsageDescriptionDictionary in your Info.plist file. Here’s a simple repro scenario: Create a minimal iOS app (no Core Data, no tests) Go to target settings → Info tab → Custom iOS Target Properties Click the (+) button on any row to begin inserting a new row Select Privacy - Location Temporary Usage Description Dictionary Click somewhere else or press Return to commit the selection Xcode crashes immediately More generally, it seems that Xcode crashes any time it tries to regenerate your Info.plist file if it contains an NSLocationTemporaryUsageDescriptionDictionary, even if (for example) you manually pasted that dictionary into the file earlier. In that case, merely tapping the (+) button in step 3 above is enough to crash it.

Compile with xcode26 due to the need to maintain compatibility with older third-party libraries and other linker flags -ObjC -ld_classic -Wl,-U,ld64_classic_ordinal_for_proxy -Wl,-no_fixup_chains Will using these settings have any impact

I'm running a macOS 15.2 guest on a macOS 15.1.1 host with UTM. I'm trying to install Xcode from within the App Store but cannot login to the App Store. When I enter credentials and click 'Sign In' I get the Error 'An unknown error occurred'.

‌Using Xcode 26, the built package encounters device compatibility issues — while it installs successfully on supported iPhone devices, but it crashes immediately upon launch and cannot run normally.‌‌In previous versions of Xcode, the same "minimum deployment" setting in the project did not cause such compatibility issues.‌ The app built with Xcode 26 shows the following behavior when installed and tested on various devices:‌ iPhone6p iOS12.5.8 fails to run 2.iPhone6 iOS11 fails to run 3.Iphone6 iOS12.5.7 fails to run 4.iPhone7 iOS12.1.3 ok 5.iPhoneX iOS 12.2 ok 6.iphone6s plus iOS10.3.1 ok 7.iphoneXS. iOS 12.1.4 ok 8.iPhone11 iOS 13.6.1 ok 9.iPhone7. iOS 13.7 ok We have tested and found that an iPhone 6s Plus running iOS 10.3.1 can normally run the app. We would like to know whether apps built with Xcode 26 are inherently incompatible with iPhone 6 and older devices. Has Xcode 26’s underlying build environment removed full support for the A8 chip, resulting in binary files containing instructions or memory models that older devices cannot parse? ‌Looking forward to your reply‌.

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone. Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination). What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM) Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report? If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend. Thank you in advance,

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?

Hi guys, Two annoying issues I'm having at the moment with agentic coding. Xcode signs out of Claude every single day and gives the error Failed to authenticate. API Error: 401. The only solution is go to settings and sign out of Claude and in again. Apple removed the little arrow to select the model, so now every time you start a new conversation you have to pick the model. I just want to start a new conversation with the model I'm using. The extra click is a time waster. Any solutions would be appreciated. Thanks

Hi, I'm using Bitbucket for remote repository. I try to change the Bitbucket App Password used so far to the remote repository with the new API token with scope as the App Password will be deprecated.. I created the API token successfully but I cannot configure it in Xcode. Does someone has already successfully replaced the App Password with the new API token in Xcode? Thank you in advance Jean MacBook Air 26.3.1 Xcode Version 26.4 (17E192)

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’m currently working on a macOS application to control a USB camera’s optical zoom via a direct USB connection. My situation: I am using a USB camera that supports optical zoom. I downloaded an open-source project, CameraController. The prebuilt binary provided on GitHub works perfectly, and I can successfully control the camera’s optical zoom. However, when I build and run the same project from source in Xcode, the zoom control UI appears disabled (grayed out). The project compiles without errors. Additionally, I attempted to implement zoom control myself using the UVC protocol in Swift . However, it seems that the zoom control commands are not successfully sent or recognized by the camera. Questions: Why would the prebuilt app work, but the same source code built locally results in disabled zoom controls? Are there known limitations on sending zoom control requests via USB on macOS? Is there a recommended modern approach for controlling optical zoom programmatically via Swift? Any insights, debugging suggestions, or references would be greatly appreciated. Thanks in advance!

Upgraded to Tahoe 26.4 and Xcode 26.4 and realized Xcode is missing the documentation for Foundation. Occasionally, if other (not yet missing) documentation references a Foundation entity, such as a type, clicking on it may open in a web browser pointing to the externally hosted Apple documentation. Anyone else experiencing this or have a workaround (perhaps the documentation files are on disk but were somehow lost / disconnected from the Xcode doc browser)? I checked the release notes for 26.4 and for 26.3 but did not find a mention of anything like that. Filed an issue with Apple, please do too if you are affected so hopefully it will see some love and lead to restoring the documentation. Edited: found some possibly related files in my ~/Library and the newer version v302 (26.4 related, I think, is considerably smaller): du -sh ~/Library/Developer/Xcode/DocumentationCache/* | awk -F/ '{print $NF "\t" $1}' v296 1.0G v302 507M

We are encountering an issue in an iOS application where functionality works correctly in Debug builds but fails in Release builds distributed via TestFlight. Details Debug (No Optimization -Onone): Works correctly Release (Optimize for Speed -O): Fails Release with -Onone: Works, but app size nearly doubles Context The issue is related to integration with the Microsoft ONNX runtime library. It appears that the Swift/Clang compiler is aggressively optimizing certain parts of the code in Release builds, possibly removing or altering required logic. Observations The issue started appearing with recent iOS/Xcode updates. No code changes affecting this logic were made recently. Behavior strongly suggests optimization-related side effects. Questions Are there known issues with aggressive optimization (-O) affecting third-party libraries? Are there recommended flags to selectively disable optimization for specific modules or functions? Any tools or diagnostics to identify what is being optimized out? Temporary Workaround Using -Onone resolves the issue but is not viable for production due to significant increase in app size. Any guidance would be greatly appreciated.

Hi Apple Developer Forums and Final Cut Pro team, I am developing a Final Cut Pro Workflow Extension focused on speech-to-text / subtitle recognition and generation. The extension runs inside Final Cut Pro, analyzes clips, generates accurate subtitles (often hundreds of individual elements), and allows users to drag the generated subtitles directly back into the FCP timeline as a clean, editable Compound Clip or Storyline. We are implementing this drag-and-drop functionality using the official pasteboard mechanism (com.apple.finalcutpro.xml and versioned types such as com.apple.finalcutpro.xml.v1-10). While the high-level documentation is helpful: Supporting Drag and Drop for Data Sent to Final Cut Pro FCPXML Reference Designing Workflow Extensions There is still no detailed public specification for the exact internal XML structure that Final Cut Pro expects for a drag operation to reliably result in a usable Compound Clip (or direct Storyline insertion), especially when dealing with large numbers of subtitle titles. After extensive systematic testing (multiple rounds over several weeks, with full experiment logs), we have observed the following: Short subtitle sequences work with many different structures (various combinations of , , , inline titles, etc.). Long subtitle lists (800+ individual elements) only succeed reliably when the outer structure uses a specific shell: root= containing + (often combined with a mainflow sequence and inner / layers). In all working cases, the dropped result appears as a “fake” / nested Compound Clip that requires 2–3 Break Apart (unpack) operations before the real editable Storyline with individual titles is revealed. Almost all other structures — pure as root, as root, wrapper layers, direct inline titles without the clip + gap + storyline shell, etc. — are immediately rejected by Final Cut Pro when the subtitle count is high. This undocumented behavior forces third-party Workflow Extension developers to engage in time-consuming blind guesswork and reverse-engineering just to achieve basic, reliable drag-and-drop integration. Our request: We kindly ask Apple to publish a detailed, official specification for the Draggable FCPXML Text Protocol (or expand the existing FCPXML Reference) that clearly defines: The minimal and recommended XML structure for dragging content into the timeline as a Compound Clip or Storyline. Exact roles and requirements for , , , , , and any implicit “mainflow” patterns. Best practices for handling large numbers of nested titles/subtitles. Reasons why certain nesting patterns are rejected or produce multi-level fake compounds. Any version-specific differences across FCPXML DTD versions. This specification is critically necessary for the FCPX Workflow Extension ecosystem. Reliable drag-and-drop from extensions back to the timeline is one of the most valuable integration points for subtitle/caption tools, transcription services, title generators, and other workflow utilities. Without clear guidelines, developers waste significant time on trial-and-error, leading to inconsistent user experiences and slower innovation in the Final Cut Pro community. We are more than happy to share our complete experiment logs, working and failing XML samples, and GitHub repository with the documentation or engineering team if it helps accelerate this. Thank you in advance for any official clarification or guidance. Clear documentation in this area would greatly benefit both developers and Final Cut Pro users.

After updating to Xcode 26.4 and also the update on the simulator the copy paste feature in the simulators doesn't work anymore and i can't build my app without it because the user has to copy and paste api keys in it. Is there an solution for it I have tried to install an other simulator ios version but then the simulator doesn't work on the the new xcode. Have someone already found an solution?

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.

Since I have downloaded latest Xcode version I am having Project Navigator in the Menu Style UI and not in the Tab based UI, the one earlier. Also, I am not able to find any options to change Project Navigator style. Please provide user the option to change UI to either Menu based or Tab based Project Navigator UI ( Projects, Source Control, Bookmark, find etc )