Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
10
7
442
10h
Good morning NSPersistent​Cloud​Kit​Container share URL stays nil and mirroring repeatedly resets after CKError​.zone​Not​Found on stale Core Data share zone
I am debugging a CloudKit sharing issue in an iOS app that uses NSPersistent​Cloud​Kit​Container with Core Data backed sharing. The symptom is that collaboration/share creation appears to succeed locally, but the resulting CKShare never gets a server-backed URL. UICloud​Sharing​Controller therefore cannot proceed because share​.url remains nil. (I do see the UICloudSharingcontroller Dialog and am abble to select people to share, one executed the share icon in the message window just spins After adding extensive logging, it looks like the real problem is not the sharing UI itself, but that Core Data + CloudKit mirroring is already in a bad state before share presentation begins. What I am seeing: Repeated CloudKit import failures with CKError​.partial​Failure The partial failure always contains one stale share zone with: • CKError​.zone​Not​Found • server message: "​Zone does not exist" Core Data then repeatedly logs: • NSCloud​Kit​Mirroring​Delegate​Will​Reset​Sync​Notification​Name • reason: Zone​Deleted • followed by a full mirroring reset Only after that reset loop do I attempt to prepare the collaboration share fetch​Share(object:) returns a share record named cloudkit​.zoneshare participants is 1 but share​.url remains nil forever, even after polling for ~20 attempts / ~20+ seconds Representative log sequence: CoreData+CloudKit ... Fetch finished with error: <CKError ... "Partial Failure"... partial errors: { com.apple.coredata.cloudkit.share.33781809-778A-461C-ABAB-872746C8F80D:defaultOwner = <CKError ... "Zone Not Found" (26/2036); server message = "Zone does not exist"> }> NSCloudKitMirroringDelegateWillResetSyncNotificationName reason: 'ZoneDeleted' NSCloudKitMirroringDelegateDidResetSyncNotificationName reason: 'ZoneDeleted' Preparing collaboration share for cruise 'Share 658' Fetching existing collaboration share for cruise 'Share 658' Fetch existing collaboration share result: found record='cloudkit.zoneshare' url='nil' participants='1' You cannot get the URL of a share until it's been saved to the server Collaboration share URL polling attempt 1/20 ... ... Collaboration share URL polling attempt 20/20 ... Collaboration share 'cloudkit.zoneshare' never produced a URL Important detail: This stale-zone Zone ​Not ​Found / Zone​Deleted reset cycle happens before the collaboration flow starts, so it looks like sharing is running inside an already unhealthy mirroring state rather than causing the corruption itself. Questions: Is this a known failure mode where a deleted/stale Core Data CloudKit share zone can keep the mirroring delegate in a reset loop and prevent newly fetched/created CKShare objects from ever receiving a server URL? Is there an Apple-recommended way to recover from this in development besides deleting the app / resetting local data / clearing CloudKit development data? Is there any supported way to identify and purge stale share metadata or orphaned Core Data share zones without fully resetting the local store? If fetch​Share returns a CKShare whose record exists locally as cloudkit​.zoneshare but url stays nil, does that generally mean the share was never fully saved to the server, or can mirroring-reset churn itself prevent the URL from materializing? Environment: • iOS app • Core Data + NSPersistent​Cloud​Kit​Container • CloudKit sharing enabled • issue observed in development environment At this point my working theory is: • stale/deleted share zone in CloudKit development environment • NSPersistent​Cloud​Kit​Container import repeatedly hits zone​Not​Found • mirroring resets continuously • collaboration share can be fetched locally but never becomes server-backed enough to produce share​.url If anyone from Apple or anyone who has hit this exact Zone​Deleted reset loop has guidance on the correct recovery path, I’d appreciate it.
2
0
58
1d
Xcode 26.4 rc
Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.
23
8
1.1k
2d
Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We are seeing what looks like a signing / managed-capability mismatch for Contactless Pass Provisioning. Environment Team ID: S7AUTD2C2B Bundle IDs: com.swiftpass.ios com.swiftpass.ios.dev Xcode: 26.4 macOS: 26.4 Problem Our app has had Contactless Pass Provisioning approved by Apple for a long time, and builds were working until a few days ago. Without any intentional signing/capability changes on our side, Xcode started failing with the following error: Provisioning profile "Swiftpass prod Appstore" doesn't include the Contactless Pass Provisioning capability. Contactless Pass Provisioning capability needs to be assigned to your team and bundle identifier by Apple in order to be included in a profile. Observed behavior Xcode marks the relevant provisioning profiles as "Ineligible" in the profile selector. This affects both development/debug and release/App Store builds. If we remove Contactless Pass Provisioning from the app entitlements/capabilities, the exact same profiles immediately become eligible and the signing error disappears. Important detail The downloaded provisioning profiles already contain the entitlement that Xcode claims is missing. We verified the downloaded profile with: security cms -D -i /Users/sergej/Downloads/Swiftpass_prod_Appstore\(1\).mobileprovision and it contains: <key>com.apple.developer.contactless-payment-pass-provisioning</key> <array> <string>shareablecredential</string> </array> So the issue appears to be that the profile contents look correct the capability is still present in the developer portal but Xcode's eligibility check still says the profile does not include the capability What we verified Contactless Pass Provisioning is still enabled for the App ID in the Apple Developer portal Newly recreated / redownloaded profiles still contain the entitlement Both dev and distribution profiles are affected The behavior is reproducible across profile refreshes and local cleanup What we already tried Reinstalled Xcode Updated Xcode and macOS Updated command line tools Cleaned DerivedData Deleted local provisioning profile cache Refreshed/redownloaded profiles from Xcode Recreated provisioning profiles in the developer portal Removed and re-added the capability in Xcode Expected behavior If the downloaded provisioning profile contains com.apple.developer.contactless-payment-pass-provisioning, Xcode should treat that profile as eligible. Actual behavior Xcode reports that the capability is missing and marks the profile as ineligible, even though the entitlement is present in the downloaded profile. Question Has anyone seen this specific mismatch with Contactless Pass Provisioning or other managed capabilities? This currently looks like either: an Apple backend/App ID capability-assignment sync problem, or an Xcode eligibility-validation bug for managed capabilities Feedback Assistant ID: FB22439399. It contains screenshots that showcase the issue as well.
12
6
439
2d
Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
After updating my Xcode to the latest, I am unable to download an installed app container from the Xcode Devices screen. This currently works with older versions of Xcode with the same app on the same iPad. This worked with older versions of Xcode on the same MacBook as well (including the Xcode 26 beta before updating to the official release yesterday) The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = "2025-09-18 20:31:01 +0000"; NSURL = "file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/"; } The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = "file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/"; } Failed to perform I/O operations. Domain: com.apple.dt.remoteservices.error Code: 11001 Failure Reason: Cannot open destination file /Users/thomsk2/Desktop/com.test.polarisdev 2025-09-18 15:30.53.744.xcappdata/AppData/Library/Caches/com.apple.dyld/standaloneapp.ios.dyld4: Permission denied System Information macOS Version 15.6.1 (Build 24G90) Xcode 26.0 (24228) (Build 17A324) Timestamp: 2025-09-18T15:31:01-05:00
6
7
470
2d
Xcode 26.4 cannot pair real Apple Watch for development (RemotePairingError 1007, iPhone stable)
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.
0
0
16
2d
Xcode now hangs; SDKs are "status unavailable"
My development work is paused as Xcode is now non-functional on my Macs. Loading any project into Xcode soon leads to a hang and Force Quit. The SDKs are listed as "status unavailable". No Simulators are available. I've tried previous versions of Xcode; removing everything and re-installing; installation from the Store and direct from the Apple Developer site. I've created a Feedback issue. This happens on both of my Mac minis. I'm running Tahoe 26.4 (25E246) on both.
26
9
818
2d
Paired Watch not appearing in Xcode
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.
9
2
11k
3d
Interface Builder - Xcode 26.4 - Changing Between Attributes Inspector, File Inspector, Etc. Is Now A Pop Up Button?
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?
2
0
104
5d
Xcode 26.4 refuses to pair with my Series 4 iWatch
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?]
4
0
72
5d
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
11
9
1.1k
5d
xcodebuild -downloadPlatform does not download via proxy
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
0
0
53
5d
The app can be signed successfully, but an error occurs when installing it on an iOS device.
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
0
0
50
5d
Good morning, I assume that coredata model changes are automatically created on the development cloudkit (CD_*)
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
3
0
60
5d
Xcode 26.3 RC - Claude Agent returns "Your request couldn't be completed"
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.
4
0
651
6d
Claude integration in Xcode 26.4 results in 401 after some time
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.
1
0
85
6d
Can’t paste into Simulator after updating to Xcode 26.4
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?
Replies
26
Boosts
29
Views
5.3k
Activity
1h
Xcode 26.4 Simulator Won't Load Game Center Data
For apps that support Game Center, calling presentViewController on a GKGameCenterViewController yields no data for leaderboards or achievements, regardless of which iOS version you're simulating (works fine on device, but doesn't work in simulator).
Replies
0
Boosts
0
Views
6
Activity
3h
Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
Replies
10
Boosts
7
Views
442
Activity
10h
Good morning NSPersistent​Cloud​Kit​Container share URL stays nil and mirroring repeatedly resets after CKError​.zone​Not​Found on stale Core Data share zone
I am debugging a CloudKit sharing issue in an iOS app that uses NSPersistent​Cloud​Kit​Container with Core Data backed sharing. The symptom is that collaboration/share creation appears to succeed locally, but the resulting CKShare never gets a server-backed URL. UICloud​Sharing​Controller therefore cannot proceed because share​.url remains nil. (I do see the UICloudSharingcontroller Dialog and am abble to select people to share, one executed the share icon in the message window just spins After adding extensive logging, it looks like the real problem is not the sharing UI itself, but that Core Data + CloudKit mirroring is already in a bad state before share presentation begins. What I am seeing: Repeated CloudKit import failures with CKError​.partial​Failure The partial failure always contains one stale share zone with: • CKError​.zone​Not​Found • server message: "​Zone does not exist" Core Data then repeatedly logs: • NSCloud​Kit​Mirroring​Delegate​Will​Reset​Sync​Notification​Name • reason: Zone​Deleted • followed by a full mirroring reset Only after that reset loop do I attempt to prepare the collaboration share fetch​Share(object:) returns a share record named cloudkit​.zoneshare participants is 1 but share​.url remains nil forever, even after polling for ~20 attempts / ~20+ seconds Representative log sequence: CoreData+CloudKit ... Fetch finished with error: <CKError ... "Partial Failure"... partial errors: { com.apple.coredata.cloudkit.share.33781809-778A-461C-ABAB-872746C8F80D:defaultOwner = <CKError ... "Zone Not Found" (26/2036); server message = "Zone does not exist"> }> NSCloudKitMirroringDelegateWillResetSyncNotificationName reason: 'ZoneDeleted' NSCloudKitMirroringDelegateDidResetSyncNotificationName reason: 'ZoneDeleted' Preparing collaboration share for cruise 'Share 658' Fetching existing collaboration share for cruise 'Share 658' Fetch existing collaboration share result: found record='cloudkit.zoneshare' url='nil' participants='1' You cannot get the URL of a share until it's been saved to the server Collaboration share URL polling attempt 1/20 ... ... Collaboration share URL polling attempt 20/20 ... Collaboration share 'cloudkit.zoneshare' never produced a URL Important detail: This stale-zone Zone ​Not ​Found / Zone​Deleted reset cycle happens before the collaboration flow starts, so it looks like sharing is running inside an already unhealthy mirroring state rather than causing the corruption itself. Questions: Is this a known failure mode where a deleted/stale Core Data CloudKit share zone can keep the mirroring delegate in a reset loop and prevent newly fetched/created CKShare objects from ever receiving a server URL? Is there an Apple-recommended way to recover from this in development besides deleting the app / resetting local data / clearing CloudKit development data? Is there any supported way to identify and purge stale share metadata or orphaned Core Data share zones without fully resetting the local store? If fetch​Share returns a CKShare whose record exists locally as cloudkit​.zoneshare but url stays nil, does that generally mean the share was never fully saved to the server, or can mirroring-reset churn itself prevent the URL from materializing? Environment: • iOS app • Core Data + NSPersistent​Cloud​Kit​Container • CloudKit sharing enabled • issue observed in development environment At this point my working theory is: • stale/deleted share zone in CloudKit development environment • NSPersistent​Cloud​Kit​Container import repeatedly hits zone​Not​Found • mirroring resets continuously • collaboration share can be fetched locally but never becomes server-backed enough to produce share​.url If anyone from Apple or anyone who has hit this exact Zone​Deleted reset loop has guidance on the correct recovery path, I’d appreciate it.
Replies
2
Boosts
0
Views
58
Activity
1d
Xcode 26.4 rc
Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.
Replies
23
Boosts
8
Views
1.1k
Activity
2d
Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We are seeing what looks like a signing / managed-capability mismatch for Contactless Pass Provisioning. Environment Team ID: S7AUTD2C2B Bundle IDs: com.swiftpass.ios com.swiftpass.ios.dev Xcode: 26.4 macOS: 26.4 Problem Our app has had Contactless Pass Provisioning approved by Apple for a long time, and builds were working until a few days ago. Without any intentional signing/capability changes on our side, Xcode started failing with the following error: Provisioning profile "Swiftpass prod Appstore" doesn't include the Contactless Pass Provisioning capability. Contactless Pass Provisioning capability needs to be assigned to your team and bundle identifier by Apple in order to be included in a profile. Observed behavior Xcode marks the relevant provisioning profiles as "Ineligible" in the profile selector. This affects both development/debug and release/App Store builds. If we remove Contactless Pass Provisioning from the app entitlements/capabilities, the exact same profiles immediately become eligible and the signing error disappears. Important detail The downloaded provisioning profiles already contain the entitlement that Xcode claims is missing. We verified the downloaded profile with: security cms -D -i /Users/sergej/Downloads/Swiftpass_prod_Appstore\(1\).mobileprovision and it contains: <key>com.apple.developer.contactless-payment-pass-provisioning</key> <array> <string>shareablecredential</string> </array> So the issue appears to be that the profile contents look correct the capability is still present in the developer portal but Xcode's eligibility check still says the profile does not include the capability What we verified Contactless Pass Provisioning is still enabled for the App ID in the Apple Developer portal Newly recreated / redownloaded profiles still contain the entitlement Both dev and distribution profiles are affected The behavior is reproducible across profile refreshes and local cleanup What we already tried Reinstalled Xcode Updated Xcode and macOS Updated command line tools Cleaned DerivedData Deleted local provisioning profile cache Refreshed/redownloaded profiles from Xcode Recreated provisioning profiles in the developer portal Removed and re-added the capability in Xcode Expected behavior If the downloaded provisioning profile contains com.apple.developer.contactless-payment-pass-provisioning, Xcode should treat that profile as eligible. Actual behavior Xcode reports that the capability is missing and marks the profile as ineligible, even though the entitlement is present in the downloaded profile. Question Has anyone seen this specific mismatch with Contactless Pass Provisioning or other managed capabilities? This currently looks like either: an Apple backend/App ID capability-assignment sync problem, or an Xcode eligibility-validation bug for managed capabilities Feedback Assistant ID: FB22439399. It contains screenshots that showcase the issue as well.
Replies
12
Boosts
6
Views
439
Activity
2d
Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
After updating my Xcode to the latest, I am unable to download an installed app container from the Xcode Devices screen. This currently works with older versions of Xcode with the same app on the same iPad. This worked with older versions of Xcode on the same MacBook as well (including the Xcode 26 beta before updating to the official release yesterday) The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = "2025-09-18 20:31:01 +0000"; NSURL = "file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/"; } The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = "file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/"; } Failed to perform I/O operations. Domain: com.apple.dt.remoteservices.error Code: 11001 Failure Reason: Cannot open destination file /Users/thomsk2/Desktop/com.test.polarisdev 2025-09-18 15:30.53.744.xcappdata/AppData/Library/Caches/com.apple.dyld/standaloneapp.ios.dyld4: Permission denied System Information macOS Version 15.6.1 (Build 24G90) Xcode 26.0 (24228) (Build 17A324) Timestamp: 2025-09-18T15:31:01-05:00
Replies
6
Boosts
7
Views
470
Activity
2d
Clipboard issues with simulators
After updating to Xcode 26.4 the pasteboard sharing feature in the simulators doesn't work.
Replies
28
Boosts
31
Views
5.1k
Activity
2d
Xcode 26.4 cannot pair real Apple Watch for development (RemotePairingError 1007, iPhone stable)
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.
Replies
0
Boosts
0
Views
16
Activity
2d
Xcode now hangs; SDKs are "status unavailable"
My development work is paused as Xcode is now non-functional on my Macs. Loading any project into Xcode soon leads to a hang and Force Quit. The SDKs are listed as "status unavailable". No Simulators are available. I've tried previous versions of Xcode; removing everything and re-installing; installation from the Store and direct from the Apple Developer site. I've created a Feedback issue. This happens on both of my Mac minis. I'm running Tahoe 26.4 (25E246) on both.
Replies
26
Boosts
9
Views
818
Activity
2d
error build: Command SwiftCompile failed with a nonzero exit code
after update to xocde14, build my old project , and get error build: Command SwiftCompile failed with a nonzero exit code.
Replies
11
Boosts
5
Views
18k
Activity
3d
Paired Watch not appearing in Xcode
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.
Replies
9
Boosts
2
Views
11k
Activity
3d
Interface Builder - Xcode 26.4 - Changing Between Attributes Inspector, File Inspector, Etc. Is Now A Pop Up Button?
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?
Replies
2
Boosts
0
Views
104
Activity
5d
Xcode 26.4 refuses to pair with my Series 4 iWatch
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?]
Replies
4
Boosts
0
Views
72
Activity
5d
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
Replies
11
Boosts
9
Views
1.1k
Activity
5d
xcodebuild -downloadPlatform does not download via proxy
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
Replies
0
Boosts
0
Views
53
Activity
5d
The app can be signed successfully, but an error occurs when installing it on an iOS device.
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
Replies
0
Boosts
0
Views
50
Activity
5d
Good morning, I assume that coredata model changes are automatically created on the development cloudkit (CD_*)
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
Replies
3
Boosts
0
Views
60
Activity
5d
Xcode 26.3 RC - Claude Agent returns "Your request couldn't be completed"
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.
Replies
4
Boosts
0
Views
651
Activity
6d
Claude integration in Xcode 26.4 results in 401 after some time
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.
Replies
1
Boosts
0
Views
85
Activity
6d