Opened a FB already (FB20928652) but wanted to check here if anybody has seen similar or has better workarounds.
xcresulttool merge appears to crash immediately after launch in Xcode 26.1 (and in 26.2b1).
It does so regardless of any inputs passed in; the crash appears to be during argument parsing before any other logic is run, so it's not contingent on inputs.
Working example from 26.0.1 (passing in arbitrary strings for a minimum-reproducible-case, so we expect to see an error message) :
% /Applications/Xcode-26.0.1.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
Error: File or directory doesn't exist at path: b.
Usage: xcresulttool <subcommand>
See 'xcresulttool --help' for more information.
The same example crashes in 26.1:
/Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
zsh: trace trap /Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge
Again, this does crash in real use cases as well, the arbitrary strings are just for quick reproduction.
The stack trace appears to be during argument parsing (which from a quick look, did indeed change between 26.0.1 and 26.1). On 26.1+, garbage data seemingly gets passed to AbsolutePath.init.
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00000001002c6748 xcresulttool-26.1`normalize(absolute:)
frame #1: 0x00000001002c6438 xcresulttool-26.1`AbsolutePath.init(_:) + 28
frame #2: 0x000000010005a2c0 xcresulttool-26.1`Merge.run() + 372
frame #3: 0x000000010005b180 xcresulttool-26.1`protocol witness for ParsableCommand.run() in conformance Merge + 12
frame #4: 0x000000010011d3e4 xcresulttool-26.1`dispatch thunk of ReadableStream.close() + 16
frame #5: 0x000000010000148c xcresulttool-26.1`main + 156
frame #6: 0x00000001804d5d54 dyld`start + 7184
The only workaround we've found is to keep using 26.0.1's copy of xcresulttool, though that's obviously not ideal.
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Since a few days, I'm trying to fetch our private SPM repo hosted on Azure via Xcode but without success. Actually they now accept only ssh key RSA-SHA2-256 or RSA-SHA2-512.
So I created a new SSH key, but it seems the problem persists when I try to fetch spm repo or git clone via xcode:
"You’re using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7) (-20)"
Even so I'm choosing the good new ssh key, it seems Xcode is sending wrong information about the new generated ssh key.
Anyone is experiencing the same here?
Hi there,
When I deploy my app to the iPhone for testing, I get the following error:
Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity used to sign the
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.
executable is no longer valid.)
My account was mistakenly deactivated by Apple last month. After appealing, Apple restored it at the end of last month. Currently, my Apple Developer account seems to be working fine.
Today, I recreated the developer certificate and identifier, added the account in XCode, everything seemed fine, and I clicked the XCode button (Start the active scheme). The build was successful, but I got the error:
Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.4gpZFc/extracted/c_mll.app : 0xe8008018 (The identity used to sign the executable is no longer valid.)
Both my certificate and identifier were created just a few hours ago and show no issues.
Before my account was deactivated, everything was working fine.
I used a regular non-Apple developer account in XCode and performed the same steps, and it worked fine.
I looked at relevant posts on the forum and tried the suggestions, but none of them solved my problem.
Hi,
I am reaching out to seek assistance with a persistent code signing issue that is preventing our team from installing our iOS app, "Scoopz" (https://apps.apple.com/us/app/scoopz-real-life-real-video/id6449206831) on physical devices. We suspect there may be an issue with our Apple Developer account, as we have exhausted all standard troubleshooting steps without success. Below, I’ve provided details about the issue, the error logs, and the steps we’ve taken.
Issue Description:
When attempting to install the app on an iPhone using Xcode, we encounter the following error:
Unable to Install “Scoopz: Debug”
Domain: IXUserPresentableErrorDomain
Code: 14
Recovery Suggestion: Failed to verify code signature of /[REDACTED_PATH]/OurApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.)
The app builds successfully to the iOS Simulator and can be released to the App Store without issues, but it fails to debug on physical devices.
Steps Taken:
Our team has attempted the following troubleshooting steps without resolving the issue:
Verified that our Apple Developer account is active and our team membership is valid.
Checked certificates in Keychain Access and the Apple Developer Portal, ensuring they are not expired or revoked. We created and installed new Apple Development certificates.
Confirmed that the provisioning profile includes the target device’s UDID, is associated with a valid certificate, and is not expired. We regenerated and reinstalled the profile. We tried both xcode managed and manually installed profiles.
Cleaned the Xcode build folder, deleted the app from the device, and rebuilt the project.
Despite these efforts, the issue persists across our entire development team, leading us to believe there may be a problem with our Apple Developer account or its associated certificates/profiles.
Request for Assistance:
We kindly request your help to:
Investigate any potential issues with our Apple Developer account that could be causing this code signing error.
Verify the status of our certificates and provisioning profiles on Apple’s servers.
Provide guidance on any additional steps or configurations needed to resolve the error.
If necessary, suggest how we can escalate this issue for further investigation.
Full error log:
Unable to Install “Scoopz: Debug”
Domain: IXUserPresentableErrorDomain
Code: 14
Recovery Suggestion: Failed to verify code signature of /[REDACTED_PATH]/OurApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.)
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 = "2025-08-20 23:50:11 +0000";
IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker;
}
Failed to install the app on the device.
Domain: com.apple.dt.CoreDeviceError
Code: 3002
User Info: {
***
}
Unable to Install “Scoopz: Debug”
Domain: IXUserPresentableErrorDomain
Code: 14
Failure Reason: This app cannot be installed because its integrity could not be verified.
Recovery Suggestion: Failed to verify code signature of /[REDACTED_PATH]/OurApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.)
Failed to verify code signature of /[REDACTED_PATH]/OurApp.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 = 78;
}
Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
"device_identifier" = "-*********";
"device_isCoreDevice" = 1;
"device_model" = "iPhone16,2";
"device_osBuild" = "17.1 (21B80)";
"device_platform" = "com.apple.platform.iphoneos";
"device_thinningType" = "iPhone16,2";
"dvt_coredevice_version" = "397.21";
"dvt_coresimulator_version" = 987;
"dvt_mobiledevice_version" = "1784.101.1";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 1;
"launchSession_targetArch" = arm64;
"operation_duration_ms" = 4926;
"operation_errorCode" = 14;
"operation_errorDomain" = IXUserPresentableErrorDomain;
"operation_errorWorker" = IDEInstallCoreDeviceWorker;
"operation_name" = IDERunOperationWorkerGroup;
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 3;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphoneos";
"param_diag_113575882_enable" = 0;
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 1;
"param_diag_gpu_frameCapture_enable" = 0;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_guardMalloc_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_mtc_enable" = 1;
"param_diag_queueDebugging_enable" = 1;
"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_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_structuredConsoleMode" = 1;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphoneos18.0";
"sdk_osVersion" = "18.0";
"sdk_variant" = iphoneos;
}
System Information
macOS Version 15.4.1 (Build 24E263)
Xcode 16.0 (23051) (Build 16A242d)
Timestamp: 2025-08-20T16:50:11-07:00
An error occurred preventing Xcode from downloading version information from App Store Connect for account "xxxxxxxx".
An unexpected error occurred: [<__NSDictionaryM 0x600003ed4fe0> valueForUndefinedKey:]: this class is not key value coding-compliant for the <app name! 5.00.12 (iOS App).
I have no idea what the hell is causing this. I have checked all of the links between screens and objects and none are missing. This is a live active version on the store.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode
Xcode Static Analyzer
Organizer Window
Hello
I have developed a standalone app for watchOS - trying my best to use best practices and floowing the (limited)documentation. But here I am, unable to distribute - or even Validate - my apps archive in Xcode.
As far as I can tell, bundle_id's are correct. It has an iOS wrapper (set up by New Project), Skip install has been tried in every combination.
I'm at a loss.
I'm sure there is some simple setting or workflow that I am missing, but I've been at it for days. Yes. Days.
Has anyone recently created and successfully distributed a standalone watch app that could help me troubleshoot?
I would be extremely appreciative. My kids would too. They miss their dad (just one 5 more minutes, I think I got it!)(I didn't get it)
Thank you
bob
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi everyone,
After updating my Mac and Xcode to 26, I’m running into a consistent crash whenever I try to launch an app from Xcode.
Environment:
Mac: Apple Silicon M3
macOS: 26.0 (25A354)
Xcode: 26.0.1 (17A400)
Issue:
When I press Run on any project (including new, empty projects), Xcode immediately crashes.
This started only after updating to the latest macOS and Xcode.
Crash details:
The crash log shows:
Application Specific Signatures:
___localError
Thread 0 crashed inside -[IDEScheme _executionOperationForSchemeOperationParameters:...] from IDEFoundation/IDEKit.
I also noticed background threads calling DVTPortal (developer portal requests) right before the crash.
What I’ve tried so far:
Cleared DerivedData, ModuleCache.noindex, and Xcode caches.
Signed out/in of my Apple ID in Xcode.
Recreated project schemes.
Verified provisioning profiles.
Reinstalled Xcode 26.
Unfortunately, the crash still happens.
Question:
Is this a known issue with Xcode 26 on Apple Silicon (M3)?
Has anyone seen a workaround?
Any guidance would be greatly appreciated — I can’t currently launch apps in Xcode at all.
Thanks!
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi all, very new "developer" trying to build my own app. The app works, just trying to improve it.
I’m implementing a Live Activity in a widget extension (Swift/SwiftUI) for an app built with Flutter as the host app. ActivityKit is functioning correctly—activities start, update, and end normally, and the widget extension receives all state updates.
However, the Live Activity UI renders as a completely black capsule (both compact and expanded Dynamic Island, as well as the Lock Screen presentation). The system shows the Live Activity container, but none of the SwiftUI content displays.
Verified so far:
ActivityAttributes contains at least one stored property (previously empty).
ContentState fully Codable + Hashable.
All Dynamic Island regions return visible test UI (Text/Image).
No .containerBackground() usage.
Added explicit .activityBackgroundTint() + system foreground colors.
All Swift files included in widget extension target.
No runtime errors, no decode failures, no SwiftUI logs.
Widget previews work.
Clean build, app reinstall, device reboot.
Entitlements and Info.plist appear valid.
Problem:
The widget extension returns a completely black UI on-device, despite valid SwiftUI content in ActivityConfiguration. The Live Activity “shell” renders, so the activity is recognized, but the widget’s view hierarchy is visually empty.
Question:
Under what conditions would a widget extension produce a black, empty UI for a Live Activity even when ActivityKit, previews, and the SwiftUI layout are correct?
Are there known cases where:
Widget extension Info.plist misconfiguration,
Incorrect background/tint handling,
Rendering issues in Dynamic Island,
Host app integrations (Flutter),
Or extension isolation issues
cause valid SwiftUI to fail to render in a Live Activity?
Any guidance on deeper debugging steps or known system pitfalls would be appreciated.
Hi everyone,
I’m a student developer currently building a watchOS app that uses HealthKit and HKWorkoutSession to estimate core body temperature from real-time heart rate data. The app runs well in the simulator, but testing on a physical Apple Watch has been extremely difficult.
Each time I try to run the app from Xcode (Version 16.3), the build gets stuck on:
“Copying shared cache symbols from MyWatchName (0% completed)”
Sometimes it just stops stating connection failure. However, more often no errors are shown, but the sync never finishes. I’ve tried the following without success:
Restarting the watch, iPhone, and Xcode
Switching networks (Wi-Fi and hotspot)
USB wired pairing
Resetting developer settings and trust prompts
Deleting derived data
Rebuilding the project
This is especially limiting for a real-time health tracking app where I need to monitor HKLiveWorkoutBuilder data while the screen sleeps — which can’t be tested effectively in the simulator.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Watch Connectivity
WatchKit
watchOS
HealthKit
Archive failing while executing command:
xcodebuild -project Unity-VisionOS.xcodeproj -scheme Unity-VisionOS -destination generic/platform=xros archive -archivePath Unity-VisionOS.xcarchive -quiet > logs/visionos_archive.log
Next error happens:
2025-11-18 15:33:12.161 ibtoold[56062:4395005] [MT] IBPlatformTool: *** Failed to launch tool with description <IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null): Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'.
Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x)
Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Device: (null)
** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`.: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Failure reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: (
"IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)"
)): Incompatible device
/* com.apple.ibtool.document.warnings */
/Users/xcode_dir_path/xcode/LaunchScreen-iPhone.storyboard:global: warning: Compiling Interface Builder products for visionOS will not be supported in a future version of Xcode. [9]
/* com.apple.ibtool.errors */
/Users/xcode_dir_path/LaunchScreen-iPhone.storyboard: error: Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'.
Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x)
Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Device: (null)
** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`.
Underlying Errors:
Description: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Failure Reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: (
"IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)"
)
Underlying Errors:
Description: Incompatible device
It appears when command was executed from TeamCity. And when it launches manually from console, it works fine.
I tried reinstalling SDK, switching different Xcode versions, removing cache, clearing IB folder, nothing helps.
xcrun simctl list
command prints next:
== Device Types ==
iPhone 17 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro)
iPhone 17 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro-Max)
iPhone Air (com.apple.CoreSimulator.SimDeviceType.iPhone-Air)
iPhone 17 (com.apple.CoreSimulator.SimDeviceType.iPhone-17)
iPhone 16 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro)
iPhone 16 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro-Max)
iPhone 16e (com.apple.CoreSimulator.SimDeviceType.iPhone-16e)
iPhone 16 (com.apple.CoreSimulator.SimDeviceType.iPhone-16)
iPhone 16 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Plus)
iPhone 15 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro)
iPhone 15 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro-Max)
iPhone 15 (com.apple.CoreSimulator.SimDeviceType.iPhone-15)
iPhone 15 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Plus)
iPhone 14 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro)
...
Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro-4K)
Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro)
iPod touch (7th generation) (com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-)
== Runtimes ==
iOS 18.1 (18.1 - 22B81) - com.apple.CoreSimulator.SimRuntime.iOS-18-1
iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6
visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
== Devices ==
-- iOS 18.1 --
iPhone 16 Pro (78683AE0-6238-4EF1-BD47-192FC0DC2559) (Shutdown)
iPhone 16 Pro Max (98BFE915-787D-4673-991A-5D3EC448CC51) (Shutdown)
iPhone 16 (D3E6FED8-9E65-4141-A31C-FC7EA3492111) (Shutdown)
...
iPad mini (A17 Pro) (10F1862E-E27B-42C5-9B02-1FA71D2F4707) (Shutdown)
iPad (10th generation) (E6E0D31F-91E4-4D3E-898D-516D79DDD58E) (Shutdown)
-- visionOS 2.1 --
Apple Vision Pro (E4D22A75-A38E-4135-9152-EF4D64BEC3F2) (Shutdown)
Failed to generate code coverage report when doing Swift Testing on iPhone device, but it's ok in UI testing or running on "My Mac(Designed for iPad)". I have enable code coverage in test plan.
My app can't run on simulator due to frameworks limitations.
Platform: Mac mini M2 w/ macOS15.7, iPhoneXR 18.6.2
Xcode version: 26.1 & 16.0
error msg:
Failed to download profiles from paths ["/private/var/mobile/Containers/Data/Application/76A1F9BC-98C8-4349-998B-0FC030DEE3EC/tmp/3A424286-872D-40AD-B4CA-65B232B57EB4"] on device 'iPhoneXR' for application with bundle ID 'xxx.xxxx.xxxx' to directory /Users//Library/Developer/Xcode/DerivedData/-bosqsqmqiqwweldrfrtgsfpnhroht/Build/ProfileData/00008020-00042C2A3E38002E: Failed to retrieve the file node for tmp/3A424286-872D-40AD-B4CA-65B232B57EB4. (Underlying Error: Failed to retrieve the file node for tmp/3A424286-872D-40AD-B4CA-65B232B57EB4)
I am getting this error msg when I try to run a SwiftUI Preview on an iOS 15.5 simulator:
Termination Reason: Namespace DYLD, Code 1, Library missing
| Library not loaded: /usr/lib/swift/libswift_StringProcessing.dylib
| Referenced from: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator/libLiveExecutionResultsLogger.dylib
| Reason: tried: '/Users/hfg/Library/Developer/Xcode/DerivedData/Testios15sim-aawlbfbtggzozseoekycwwpadhrc/Build/Intermediates.noindex/Previews/iphonesimulator/Testios15sim/Products/Debug-iphonesimulator/libswift_StringProcessing.dylib' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswift_StringProcessing.dylib' (no such file), '/usr/lib/swift/libswift_StringProcessing.dylib' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswift_StringProcessing.dylib' (no such file)
FYI I tried with the Legacy Preview Execution both on and off
CRITICAL: iOS 26.1 Simulator Runtime (Build 23B86) Missing / MobileAsset Catalog Failing
Summary
After updating macOS and Xcode, I can no longer download or install the required iOS 26.1 simulator runtime. The Xcode Components system fails for all assets, and the MobileAsset catalog for iOS simulator runtimes appears to be missing or invalid. The runtime is also not listed on developer.apple.com.
This issue blocks me from running any iOS simulators.
Steps to Reproduce
Update to:
macOS 26.1 (25B78)
Xcode 26.1.1 (24455 / 17B100)
Open Xcode → Settings → Platforms/Components
Attempt to download:
iOS 26.1 Simulator Runtime
Any other downloadable component (e.g., Predictive Code Completion Model)
Alternatively, try using:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads
xcodebuild -downloadPlatform iOS -buildVersion 26
Observed Behaviour
Xcode Components Downloads Fail
Attempting to download the iOS 26.1 runtime results in:
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
Additional detail:
Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime)
Domain: DVTDownloadsUtilitiesErrorDomain
Code: -1
And:
Download failed due to a bad URL.
Domain: com.apple.MobileAssetError.Download
Code: 49
User Info: { checkConfiguration = 1 }
Predictive Code Completion Model Also Fails
The operation couldn’t be completed. (IDELanguageModelKit.IDEModelDownloadAdapter.DownloadError error 2.)
Domain: IDELanguageModelKit.IDEModelDownloadAdapter.DownloadError
Code: 2
There was an error transferring over the network.
Code: 2
CLI Downloads Fail
Command:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads
Result:
DVTDownloadable: Download Failed … iOS 26.1 Simulator (23B86)
Command:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26
Result:
iOS 26 is not available for download.
Runtime Not Listed on Developer Downloads
The following page does not list iOS 26.1 simulator runtime:
https://developer.apple.com/download/all/
Expected Behaviour
Xcode should be able to fetch the MobileAsset catalog and download iOS 26.1 simulator runtime.
The runtime should appear in the Components tab and on developer.apple.com/download/all/.
CLI tools should successfully download the platform.
System Information
macOS: 26.1 (Build 25B78)
Xcode: 26.1.1 (24455) (Build 17B100)
Timestamp: 2025-11-17
Impact
This issue currently prevents:
Running any iOS simulator
Testing or building on the required runtime
Using other Xcode downloadable components (language models, etc.)
This is a blocking issue for development.
Notes
Multiple Xcode reinstallations attempted
macOS restarts performed
Network connectivity normal
Issue persists across all download methods (GUI + CLI)
Hello,
I am facing a recurring issue with Xcode iOS simulator (preview). I want to preview a SwiftUI for iOS in Xcode, but the Simulator app fails to boot up.
I receive the following error in Xcode:
Cannot Preview in this file. Simulator was shutdown during an update.
I have tried the following:
Completely uninstalling XCode and deleting all developer data, then reinstalling everthing again.
Shutdown and restart
Deleting all developer data, deleting XCode cache
Reinstalling iOS Simulator runtimes and reconfiguration of simulators.
Tested using different simulator and runtime versions.
"xcrun simctl --set previews delete al"
My reported issues:
FB20987522
FB20485454
Thank you
Best regards,
Jens
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode Previews
Xcode
Simulator
Business and Enterprise
I have a question concerning Xcode version 26.
Ever since I installed this version on my Mac, I have been experiencing issues with the StoreKit configuration file. The Simulated StoreKit Failures check boxes and selections are all grayed out.
Once in a while, I see a pop-up stating "The document 'TaConfig.storekit' could not be autosaved. The file has been changed by another application. The pop-up Save as... points to where my config file is located, but the config file is grayed out. I thought maybe the directory where the file is located is write protected, but I have been able to save other files to the same directory.
The Edit Scheme... -> Run -> Options has the StoreKit Configuration set for my file TaConfig.storekit.
It feels like there is an option somewhere that I'm missing.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hello,
Is there any plan to integrate realtime sanitier (RTSan) in Apple Clang?
This tool has been introduced in Clang 20.1.0 back in March 2025. This tool is incredibly useful, and having it in AppleClang (and ideally integrated in Xcode and xcodebuild) would be great.
Thank you,
Best,
Thomas
Where are the instructions for this process
Hi,
I'm working on an app that integrates third-party UWB accessories using the Nearby Interaction framework. I want to display real-time data via Live Activities, and ideally, I hope the app can continue ranging/interacting with the accessory even when it's in the background—triggering updates in the Live Activity.
Specifically:
Can I use Live Activity to keep Nearby Interaction sessions running in the background, as long as the accessory is still nearby and connected? Or do I always need to initiate sessions in the foreground?
Are there ways to maintain or trigger new Nearby Interaction sessions entirely in the background, when using third-party UWB accessories?
Is there any official guidance regarding permissions, user authorization requirements, or restrictions for background ranging with third-party hardware?
Are there recommended strategies or patterns for updating Live Activity widgets with data from Nearby Interaction or UWB accessories while backgrounded? (e.g. Bluetooth triggers, push notifications, background tasks)
Any advice, experiences, or official recommendations would be greatly appreciated! I want to ensure my implementation is compliant and offers the best possible user experience.
Thanks!
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Nearby Interaction
WidgetKit
Background Tasks
Core Bluetooth
Hi everyone,
In the previous Xcode version, I was using Intelligence with ChatGPT to refactor and fix code. It worked great: it applied changes across files in a few seconds and the code preview updated quickly.
In the new Xcode version, something strange is happening:
• With Claude, responses are almost instant.
• With ChatGPT, it starts fine but then it shows the entire file instead of just the relevant section and, after a few lines, it starts streaming character by character, becoming extremely slow.
This only started after updating Xcode.
Is there any setting (streaming, token limits, formatting, etc.) that I can tweak to get ChatGPT back to the previous performance? Is anyone else seeing this issue with ChatGPT in Intelligence, or is it just my setup?
Thanks in advance for any help!
Topic:
Developer Tools & Services
SubTopic:
Xcode
What possessed Apple developers to redesign the Behaviors UX? It is not as flexible, and at least Custom Behaviors do not work all the way through 26.2beta.
You cannot name or rename behaviors. It just keeps "New Behavior."
You cannot delete behaviors.
Running shell scripts does not work.
I gave up after that.
Why was the Xcode 16 model changed and NOT TESTED!
Topic:
Developer Tools & Services
SubTopic:
Xcode