Xcode 26.4 on macOS 26.3.1 cannot pair a real Apple Watch for development. iPhone companion is visible and stable in Devices and Simulators. Watch is paired to iPhone and works normally, but Xcode shows: CoreDeviceError Code: 4 RemotePairingError Code: 1007 “The device rejected the connection request.” “Ensure the device is paired with this machine.” What I already tried: trusted Mac on iPhone re-paired Watch with iPhone reconnected iPhone by cable reset authorized computers on Watch restarted devices reopened Devices and Simulators Result: iPhone remains stable Watch is seen intermittently or stays reconnecting / rejects pairing app logic is otherwise working on iPhone side Need: steps to restore Watch ↔ Xcode development pairing without further destructive resets.

after update to xocde14, build my old project , and get error build: Command SwiftCompile failed with a nonzero exit code.

I managed to install watchOS 2 without having registered my Watch's UDID, but as it's part of the instructions for installing watchOS betas I thought I'd better do it now in case beta 2 bricks my Watch or something.However, the Watch isn't appearing in Xcode. I've tried both the latest public release and Xcode 7 beta, but there's "no paired devices" section under my iPhone when I connect it to Xcode and look in the Devices window.

In Interface Builder there use to be a segmented control to switch Inspectors. It's been this way forever. I could switch from: File Inspector Attributes Inspector Size Inspector Etc... Now in Xcode 26.4, it is this clunky pop up button? What? I thought Apple didn't like Interface Builder anymore so I'm surprised they are even touching it. This part of a SwiftUI rewrite or just bad vibes?

Watch has latest watchOS 10.6.2. Xcode tries to connect and fails. I insured that both the Mac and the watch are using the same WiFi network (2.4) - and the mac has no other network interface. I have successfully paired to my iPhone and iPad. I quit and restarted Xcode. I close and reopen the "Devices and Simulators" window (to get it to retry). I restarted my watch. The watch is at 98% battery level. Suggestions? [Or do I need to purchase a new watch?]

There's a regression in Xcode 26.x (26.0 ... 26.5 beta) where xcodebuild is not able to download platforms when it is behind proxy. $ env | grep PROXY HTTP_PROXY=..... HTTPS_PROXY=..... $ xcodebuild -version Xcode 26.5 Build version 17F5012f $ xcodebuild -downloadPlatform iOS -buildVersion 23E244 -exportPath ./test Finding content... iOS 23E244 is not available for download. Xcode 26.x GUI is able to download from behind proxy though. The last known Xcode which used to be able to download platforms from behind a proxy was Xcode 16.4. $ xcodebuild -version Xcode 16.4 Build version 16F6 $ xcodebuild -downloadPlatform iOS -buildVersion 23E244 -exportPath ./test Downloading iOS 26.4 Simulator (23E244): 0.0% (66 kB of 10.6 GB) The relevant feedback ID: FB22125784

Domain: MIInstallerErrorDomain Code: 13 Recovery Suggestion: Please ensure that the certificates used to sign your app have not expired. If this issue persists, please attach an IPA of your app when sending a report to Apple. User Info: { DVTErrorCreationDateKey = "2026-04-03 11:27:29 +0000"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } Failed to install the app on the device. Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { NSURL = "file:///Users/admin/Library/Developer/Xcode/DerivedData/Unity-iPhone-cafeohisbuqbtbfzphrtkslqqokm/Build/Products/ReleaseForRunning-iphoneos/UnitySDK.app"; 无法安装“UnitySDK” Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: 无法安装此App，因为无法验证其完整性。 Recovery Suggestion: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.D7k1ON/extracted/UnitySDK.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.D7k1ON/extracted/UnitySDK.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) Domain: MIInstallerErrorDomain Code: 13 User Info: { FunctionName = "+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]"; LegacyErrorString = ApplicationVerificationFailed; LibMISErrorNumber = "-402620392"; SourceFileLine = 80; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_identifier" = "00008120-000C58283600201E"; "device_isCoreDevice" = 1; "device_model" = "iPhone15,3"; "device_osBuild" = "26.4 (23E246)"; "device_osBuild_monotonic" = 2304024600; "device_os_variant" = 1; "device_platform" = "com.apple.platform.iphoneos"; "device_platform_family" = 2; "device_reality" = 1; "device_thinningType" = "iPhone15,3"; "device_transport" = 1; "launchSession_schemeCommand" = Run; "launchSession_schemeCommand_enum" = 1; "launchSession_targetArch" = arm64; "launchSession_targetArch_enum" = 6; "operation_duration_ms" = 2915; "operation_errorCode" = 13; "operation_errorDomain" = MIInstallerErrorDomain; "operation_errorWorker" = IDEInstallCoreDeviceWorker; "operation_error_reportable" = 1; "operation_name" = IDERunOperationWorkerGroup; "param_consoleMode" = 1; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 0; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_MTE_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_mtc_enable" = 1; "param_diag_checker_tpc_enable" = 0; "param_diag_gpu_frameCapture_enable" = 3; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 1; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 0; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_lldbVersion_component_idx_1" = 0; "param_lldbVersion_monotonic" = 210000160004; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos26.4"; "sdk_osVersion" = "26.4"; "sdk_platformID" = 2; "sdk_variant" = iphoneos; "sdk_version_monotonic" = 2304023700; } System Information macOS Version 26.4 (Build 25E246) Xcode 26.4 (24909) (Build 17E192) Timestamp: 2026-04-03T19:27:29+08:00

Good morning, I assume that coredata model changes are automatically created on the development cloudkit (CD_*) as that has been the behaviour in the past and than you deploy the schema changes to prod. I have a case were a new field in a existing table is not appearing in the dev cloudkit table is there a way to "force" it to show up? thanks in advance

Environment: Xcode 26.3 RC macOS 26.3 (25D125) (Apple Silicon / arm64) Setup: Xcode > Settings > Intelligence > Claude Agent: Signed In (account status shows "Signed In") Model: Default Steps to reproduce: Open a new chat in Xcode's Coding Assistant Select "Claude Agent" from the agent dropdown (instead of "Claude Sonnet 4.5") Send any message (e.g. "HI") Expected result: Claude Agent responds normally. Actual result: The message is sent but immediately returns the error: "Your request couldn't be completed." 🚩I have an active Claude Code subscription with remaining usage. Running claude in Terminal works perfectly, confirming the subscription and quota are valid.

Setup: macOS 26.4 Xcode 26.4 Claude premium subscription Claude account logged in Xcode settings The issue usually surfaces after initially setting up Claude integration in Xcode and then leaving Xcode open for at least a day or so. The integration works initially (right after logging in). But then after some time it starts responding with this error. Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011Ya....."} Restarting Xcode does not help. The only thing that helps is log out from Claude account and log back in. Sounds like the token refresh logic is broken or missing. Please improve moving forward.

Mac Pro 2019, Tahoe 26.3, Xcode 26.2 Mac Mini 2023 M2, Tahoe 26.3, Xcode 26.2 On Mac Pro 2019 the app is only Intel while on Mac Mini 2023 M2 it is ARM64 only. Both have Standard Architectures (Apple Silicon, Intel). Both have Build Active Architecture Only is set to No (Debug + Release). Happen for default new projet macOS -> App and Obj-C, Xib. No change to defaults setting except uncheck "Automaticaly manage signing" and "Signing Certificate" set to "Sign to Run Locally" HOWEVER On Mac Pro 2019, BigSur 11.7.10, Xcode 14.10 the application is build Universal ! Why cannot build universal with Tahoe 26.3, Xcode 26.2 ? Can I submit a Mac applcation to App Store Connect with BigSur 11.7.10, Xcode 14.10 ? What are the minimal version of Mac Os and Xcode to submit a Mac applcation to App Store Connect ?

Hello, I am experiencing a critical blocking issue developing a watchOS app. While the iPhone 15 Pro Max is fully "Connected" via USB (confirmed green light in Network Settings), the Apple Watch Series 7 (watchOS 11.2) remains unreachable by Xcode. Mac: Mac Mini (macOS 15/16). Devices: iPhone 15 Pro Max (iOS 18+), Apple Watch Series 7 (watchOS 11.2). Xcode: 16.4 / Build 26.4. Hardware: Direct USB-C connection (USB 2.0 480Mb/s protocol). Technical Evidence of Protocol Failure: Missing Staging Folders: ~/Library/Developer/Xcode/watchOS DeviceSupport does not exist, implying the handshake fails before symbol stripping/sync begins. CoreDevice Error: Consistently receiving: "Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters." Missing Keychain Entries: No com.apple.coredevice keys found in Keychain Access, suggesting the Trusted Host handshake is incomplete. mDNS/Discovery: xcrun devicectl list devices shows the iPhone as connected but the Watch as available (paired). Steps Taken (Zero Success): Wiped ~/Library/Developer/CoreDevice and killed remoted. Disabled "Location Simulation" in Scheme Options. Reset "Location & Privacy" on iPhone; trusted Mac on both devices. Disabled Wi-Fi on all 3 devices to force Bluetooth/Wired relay. Performed "Offload App" on the iOS Watch app to reset the daemon. The "Developer Mode" toggle is missing from the Watch's Privacy & Security menu and refuses to reappear despite successful iPhone-to-Mac connectivity. Logs: I have a full sysdiagnose (300MB) ready. (Feedback ID: FB22425709). Does anyone know a specific defaults write command to force-trigger the watchOS CoreDevice tunnel or a way to manually inject the Developer Mode profile?

Somehow I ended up with three info.plist and entitlement files in my macOS project. Is this ok, should I merge them? There is only one target.

Hi everyone, I am struggling with a persistent issue regarding my Developer Program membership and Xcode syncing. Even though the Apple Developer Portal shows that my developer license is active and I have full access to App Store Connect, it is unfortunately not possible to sign applications with this account. It behaves as if the license wasn't active. The Symptoms: -Portal status: Active (Account Holder/Admin), -Xcode Settings: When I navigate to Settings > Accounts and select my team, there is a Red X displayed next to "Certificates, Identifiers & Profiles.", Xcode suggests there is an issue accessing these resources and I cannot sign any binaries. Confirmed the membership is active in the web portal. Everything seems configured correctly on the web side, but the account simply doesn't work locally in Xcode. Has anyone faced this specific "Red X" issue despite a valid membership? Is there a specific cache I need to clear or a way to force Xcode to re-fetch the correct status? Any advice on how to resolve this loop would be greatly appreciated. Thanks! :)

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