We are seeing repeated occurrences of the following log line in test runs triggered via .xctestrun files on iOS 26:
IDERunDestination: Supported platforms for the buildables in the current scheme is empty.
This line is printed n number of times after a test fails, significantly increasing test execution duration (2–3 minutes extra in some cases).
The issue does not occur when tests are built and run together from Xcode directly — it’s specific to .xctestrun-based executions using xcodebuild test-without-building.
Steps to Reproduce:
Use Xcode 26 to build a sample XCTest target (we used a simple UI test project).
Locate the generated .xctestrun file under DerivedData/.../Build/Products/....
Run tests using:
xcodebuild -xctestrun /path/to/sample.xctestrun \
-destination "id=<device_id>" \
test-without-building
Observe the logs during test failure.
Observed Behavior:
The log line
IDERunDestination: Supported platforms for the buildables in the current scheme is empty
appears multiple times.
The test cleanup and teardown phase takes significantly longer (2–3 minutes).
Expected Behavior:
The log should appear once or not at all.
Test cleanup time should remain consistent.
Additional Information:
Affects only iOS 26 devices and .xctestrun-based runs.
Not reproducible on iOS < 26.
Xcode 26 and 26.x beta versions tried.
Reproducible both locally and on CI systems using real devices.
Same .xctestrun file, when used on older OS versions, does not cause delay.
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
I still use my own Info.plist, and I run a script as the last step of my builds to modify the final built Info.plist to have information about the build, like date, machine, git build count, etc. Works fine on latest Xcode 26.0.1 for archive builds, but on DEBUG builds to an attached device Xcode overwrites my processed plist with a copy of the original unmodified build, unless I first do a Clean Build Folder. Any ideas on how to fix this? Annoying, but not critical
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.
My MBP M1 Pro gets really hot. iOS 26.1 Simulator in Xcode 26.1 makes ReportCrash process run at 60-160% of CPU shows Activity Monitor.
MacOS 26.1. I've reported this via Feedback Assistant: FB20918609.
Is there a way to quit this process permanently? When I Force Quit this it opens again immediately. Only way to stop it is to quit Simulator. But then again, I need to use the Simulator.
I often use a Wi-Fi network where:
Whatever mechanism Xcode uses to automatically discover a previously paired iOS device seems to be blocked (the Devices and Simulators window shows "Browsing on the local area network for [iPhone]" and never proceeds), but
I can connect to the iOS device from my Mac if I know its IP address, such as by pinging it
The same hardware/software configuration works with wireless Xcode connections on a different Wi-Fi network.
Thus I'm wondering if there's any functionality that allows the IP address to be manually entered into Xcode to avoid needing to connect a cable from my Mac to my iPhone during development. Searching around seems to suggest this existed at some point in the past but I can no longer find this in a current version of Xcode. Or if there are any other workarounds, although I can't modify the network itself as it's not my network.
Hi,
I'm running Xcode version 26.0.1 (17A400). Every time I restart Xcode, it seems to not recognize my Claude login anymore, and I have to go through the whole authentication flow again. It's quite annoying. Does anyone have a solution for it?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hello,
I’m new to macOS after many years on iPhone, and I’m trying to run a simple app on my iPhone directly from Xcode. The app builds fine in the simulator, but deploying to a real device fails with this error:
The tunnel connection failed while the system tried to connect to the device.
Domain: com.apple.dt.CoreDeviceError
Code: 4
Failure Reason: The tunnel connection failed while the system tried to connect to the device.
User Info: {
DVTErrorCreationDateKey = "2025-10-02 16:55:53 +0000";
"com.apple.dt.DVTCoreDevice.operationName" = connect;
}
--
The tunnel connection failed while the system tried to connect to the device.
Domain: com.apple.dt.RemotePairingError
Code: 4
--
I get the same error via command line, e.g. for
xcrun devicectl device info apps --device "..."
My setup:
macOS Version 26.0.1 (Build 25A362)
Xcode 26.0.1 (Build 17A400)
iPhone 13 on iOS 26.0.1
iPhone is paired with the Mac (I can see it in Finder and in Xcode alongside the simulator).
Developer Mode is enabled on the iPhone.
I also see my Apple Watch listed in Xcode.
I might have enabled Multipath networking in the past - but in iOS 26.0.1, the setting is missing in the Developer settings - so there is no way to check if it's enabled or to disable it. I know this was the solution to a similar problem: https://developer.apple.com/forums/thread/737907
What I tried:
Restarted both Mac and iPhone, unpaired them, paired them again.
Disabled and re-nabled development mode
Tried both Wi-Fi and wired connection (Apple-certified cable).
Reset privacy and network settings on the iPhone.
Verified I’m not running any VPN.
Despite this, deployment always fails with the same tunnel connection error.
Has anyone encountered this before or found a solution/workaround?
Thank you very much,
Martin
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm working in a constrained environment where sending source is not an option if any part of it is stored in outside systems. However, I also have some projects which don't have these constraints which led me to these questions. Thanks!
Can I disable intelligence per project or workspace?
Is any project data sent if intelligence is enabled but I'm not typing any requests in the coding assistant?
Is source/metadata persisted in any way when using the ChatGPT mode without an account?
Hello!
Ive been working on a package tracking app for iOS and was looking forward to pushing it to TestFlight for some testers to use. When I go to archive the package, I get a warning about the "...TrackerIntents.appex is an ExtensionKit extension and must be embedded in the parent app bundle's Extensions directory, but is embedded in the parent app bundle's Tracker.app/Extensions directory". The extension is for siri integration with shortcuts.
I have done quite a lot of things to try and diagnose this but cant seem to get passed this warning. I know it's a warning but would rather it not exist. Ideally I would think its a matter of "moving" the items but in the navigation area, I dont see an extensions area.
The main app target has it in the dependencies along with the EmbedExtensionKit Extensions in the Build Phases.
Any ideas or configs I can try? I can provide more information if needed.
This is on the latest Xcode version 26.0.1 for iOS 26.
Thank you.
I have an iOS app with a QuickLook extension. I also added Apple Vision Pro in the target's General > Supported Destinations section. About one year ago, I was able to run the app on iPhone, iPad and Apple Vision Pro Simulators.
Today I tried running it again on Apple Vision Pro with Xcode 26.0.1, but Xcode shows this error:
Try again later. Appex bundle at ~/Library/Developer/CoreSimulator/Devices/F6B3CCA8-82FA-485F-A306-CF85FF589096/data/Library/Caches/com.apple.mobile.installd.staging/temp.PWLT59/extracted/problem.app/PlugIns/problemQuickLook.appex with id org.example.problem.problemQuickLook specifies a value (com.apple.quicklook.preview) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point.
I tried again later a couple times, even after running Clean Build Folder Immediately, without any change. I can reproduce this with a fresh Xcode project to which I add a Quick Look Preview Extension and Apple Vision Pro as a supported destination. The error doesn't happen when running on Apple Vision Pro (Designed for iPad) or iPad Pro 13-inch (M4) destinations. What is the problem?
I created FB20448815.
Hello,
I'm encountering a persistent issue when building my project with Xcode 26 and iOS 26. The console shows errors related to font file references that don't actually exist in my project.
GSFont: file doesn't exist - "file:///private/var/containers/Bundle/Application/...../HiraginoKakuGothic.ttc"
After investigation, I found that the issue originates from XIB files incorrectly referencing HiraginoKakuGothic.ttc:
<customFonts key="customFonts">
<array key="HiraginoKakuGothic.ttc">
<string>HiraginoSans-W3</string>
</array>
</customFonts>
The problem appears to be triggered when setting UILabel fonts to "ヒラギノ角ゴシック W3 16.0" in Interface Builder, which causes the XIB to reference HiraginoKakuGothic.ttc.
Interestingly, when I create a new project and use the same fonts ("ヒラギノ角ゴシック W3 16.0"), it does NOT automatically reference HiraginoKakuGothic.ttc.
Here's what I've tried:
①Changed both UILabels' fonts to system font
②Verified in XIB Source Code that the .ttc references were gone
③Cleaned Build Folder
④Cleared DerivedData
⑤Restarted Xcode
⑥Set the labels back to "ヒラギノ角ゴシック W3 16.0"
⑦Checked XIB Source Code again - the non-existent .ttc references reappeared
Even if I manually remove the customFonts references from the source code, they get regenerated as soon as I make any font changes in Interface Builder.
I've also noticed that Xcode 16.1 has the same underlying issue, though it doesn't produce the console errors that Xcode 26 does.
This seems to be a long-standing XIB issue, possibly related to reference caching. While new projects aren't affected, existing projects continue to maintain these incorrect references.
My questions:
How can I permanently resolve this issue in my existing project?
What's the potential impact of these incorrect font references?
Is there a way to clean up these cached references without affecting the rest of the project?
Any insights or workarounds would be greatly appreciated.
Thank you.
The Files app in the iOS 18 beta simulator appears to be read-only. I am unable to:
create folders
copy files into it by dragging them from macOS
safe files from safari
I have been unsuccessful at finding a way to popular any file or folder in the Files app which is preventing me from testing some scenarios in my app where I import files using the files sheet.
The earliest I tried was beta 3 and it still persists in beta 7. The iOS 17 simulator works fine in comparison.
My mac is a 2019 macbook pro running Sonoma 14.5.
To reproduce:
New folder
Launch Files app in iOS simulator
Tap into "On my phone"
From the top menu tap "New Folder"
(nothing happens)
Download a file
Launch safari
Find a file like a PDF to download
Tap on the down arrow in the toolbar
Files opens up with the filename in the textfield at the bottom
The "Save" button is grayed out.
Copy from macOS
Open the Files app in iOS and browse to a local folder
drag a file from the macbook onto the simulator
the sheet appears with the filename in the text field
The "Save" button is grayed out
On iOS 18.0+ simulators, tap any share link button from any app, select "Save to Files", the "Save" button is disabled.
In all previous simulator versions this works. This behavior even happens with default Apple apps like Photos.
Simulator: Version 16.0 (1037)
XCode: Version 16.1 beta (16B5001e)
macOS: 14.6.1 (23G93)
Hello,
When trying to download the latest version of iOS simulator on xCode i get this error:
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
User Info: {
DVTErrorCreationDateKey = "2025-02-21 09:05:50 +0000";
}
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({
RequestedBuild = 22D8075;
})
Domain: DVTDownloadsUtilitiesErrorDomain
Code: -1
Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime)
Domain: com.apple.MobileAssetError.Download
Code: 49
User Info: {
checkConfiguration = 1;
}
System Information
macOS Version 15.0 (Build 24A335)
Xcode 16.2 (23507) (Build 16C5032a)
Timestamp: 2025-02-21T11:05:50+02:00
Hello, I wanted to get the lat & lon where map is clicked/tapped
but Gives Error on Tap onTapGesture
"<0x10bf0....> Gesture: System gesture gate timed out"
2 out of 10 clicks it works , 8 times gives error
Please help
MapReader { reader in
Map(position: $MapKit_Position_default , scope: mapScope) {
//...
}
.onTapGesture(perform: { screenCoord in
let pinLocation = reader.convert(screenCoord, from: .local)
print("[OnTap]:\(pinLocation)")
isLocationSetMarkerActive = true
})
.gesture(SpatialTapGesture().onEnded { event in
// Use event.location for the tap location
print("[gesture]:Tapped location: \(event.location)")
})
My main app target builds fine and can run on Simulator without issue.
Whenever I try to run a Preview, I get this error:
== DATE:
Monday, November 3, 2025 at 2:52:23 PM Pacific Standard Time
2025-11-03T22:52:23Z
== PREVIEW UPDATE ERROR:
SimulatorShutdownUnexpectedlyError: Simulator was shutdown during an update
Simulator [F85A5AF1-F52C-4662-AFCD-762F87AF537D] failed to boot and may have crashed.
This seems like it started happening after updating to MacOS 26. I've tried reinstalling all Simulators, tried on Xcode 26, deleted derived data, restarted Xcode and my Mac several times.
What other troubleshooting steps can I take?
Hello,
I am currently working on personal project based on Matter.
I need to create a Basic Video Player as specified in Matter's standard embedding the Media Playback Cluster.
I went through the reading of how Apple now supports Matter as a standard :
linkText
My understanding of the following schematic, is alongside :
HomeKit Accessory Protocol (HAP) Framework API
Related HAP accessories underneath the homeKit framework.
Developpers also find under the Homekit framework :
CHIP (Connected Home IP) Framework API
Related Matter accessories this time
Both types of accessories/devices can be commissioned in the HomeKit ecosystem seemlessly.
Each framework has it's documentation :
HAP : https://developer.apple.com/documentation/homekit/hmhomemanager
CHIP : https://developer.apple.com/documentation/matter
I want through the process of installing XCode and the HomeKit Accessory Simulator. In the list of HomeKit Accessories I did not see any Media related devices :
The list of currently supported devices is limited as I read here and will be enriched with time :
https://support.apple.com/en-us/102135#:~:text=The%20Home%20app%20currently%20supports,%2C%20temperature%2C%20and%20humidity).
In the meantime, as I read the matter documentation, I read several references made to the Media Playback :
https://developer.apple.com/documentation/matter/mtrclustermediaplayback
https://developer.apple.com/documentation/matter/mtrbaseclustermediaplayback
https://developer.apple.com/documentation/matter/clusters#Interacting-with-the-Media-Playback-cluster
My questions are :
Are Matter Basic Video Players, (Media Playback) supported in HomeKit ?
Why aren't they listed in HomeKit Accessory Simulator ?
How can I add a Basic Video Player in HomeKit and display it's Media Playback controls once I have added the device to HomeKit ?
Thank you for your Answer.
Regards
David
Since upgrading my iPhone 13 Pro Max to iOS 26, apps have become nearly impossible to debug. The recent update to iOS 26.1 has made this even worse.
Going from app start to a fully rendered & responding screen takes <1 second on a Debug build when no debugger is attached, but with the debugger attached I get these times (measured manually with a stopwatch):
First render:
<1 second without debugger
5 seconds on USB debugger
30 seconds on wireless debugger
Data loaded from webserver and UI responding:
<1 second without debugger
19 seconds on USB debugger
5 minutes on wireless debugger!
Doing an online speed test reports 55 Mbps for the phone and 60 Mbps on the MacBook, so I doubt it's my WiFi.
Having a debugger attached used to make minimal difference on iOS 18, but the performance has tanked completely since the last major release. What happened?
I just discovered xcresulttool - provided with the Xcode Command Line Tools. It does an amazing job generating a JSON report of warnings/failures. The tool requires a xcresult file path - my issue is that xcodebuild build does not produce an xcresult file so I can't find a way to generate a similar report for that action.
My use case is simple - in my CI job, I want to report back on specific failures during builds and tests. I run xcodebuild build-for-testing and then later xcodebuild test-without-building. If there is a failure during the test phase, I can easily parse the issues from the JSON report in xcresult. However, if there is a failure during build, there is no result file to parse from.
What is more confusing is that if you run xcodebuild test (build and test in one command) compilation errors are put in the xcresult file and you can read them just fine with xcresulttool.
Is there any way to get a failure report from xcodebuild build actions without parsing stdout/stderror? I am aware of 3rd party tools such as xcpretty or xcbeautify - I would like to avoid anything that requires parsing the output.
Hi everyone,
I’ve run into a strange issue while building my app with Xcode 26 beta 6 (targeting iOS 26). When I include an app icon created using Icon Composer, the build time jumps to over 5 minutes. During this time, I noticed that a utility called AssetCatalogSimulatorAgent is consuming a significant amount of CPU.
If I remove the Icon Composer-generated icon from my target, the build completes in about 40 seconds. This behavior is consistent across multiple builds.
Has anyone else experienced this? Is there a known workaround or optimization for icons created with Icon Composer? I’d love to keep using the new icon format, but the build time is becoming a real bottleneck.
Thanks in advance!