Hi,
Ever since I updated to macOS Tahoe and started using Xcode 26 daily, I've run into an issue where it gets stuck very frequently when launching and running my app in the simulator. It happens with the main app target as well as when running unit tests. If I restart Xcode and the simulator app, it works fine again for a while, but after some use, it goes back to the same situation. In Activity Monitor, Xcode ends up at 1000% CPU utilization for a minute or more, basically rendering the simulator and the debugger stuck. If I untick the "Debug Executable" option in the scheme editor, it works fine as well.
Anyone else run into the same situation, or are there any tips I can follow to fix this issue? It makes it really tedious to make changes and then be stalled for a minute or more to see the app run. I've restarted the Mac, erased the booted simulator as well. I'm on a MacBook Pro M4 Pro. Everything used to run fine before macOS Tahoe / Xcode 26 on my main device. In fact, I used to run macOS Tahoe / Xcode 26 beta versions on a separate partition without any problems.
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
Hello,
I'm unable to run any test cases in Xcode 16 with the iOS 18 simulator.
Steps to Reproduce:
Create a new iOS project in Xcode 16 using the default iOS app template with the testing option checked.
Run any test or UI test case by clicking the "Play" icon in the Test navigator.
Xcode gets stuck at the "Testing" state indefinitely.
Environment:
macOS 15 beta 8
Xcode 16 beta 6
iOS 18 beta 7 simulator
I want to use a ci_script to change the CI_BUILD_NUMBER to a new value.
But in XCODE CLOUD there seems to be no programmatic way to change it?
Hi everyone,
I recently updated to Xcode 26.0 and noticed that the “Extract Subview” refactoring option seems to be missing.
Now, in Xcode 26, the only options I see under Editor -> Refactor -> are:
Extract to Selection File
Extract to Method
Extract to Variable
Extract All Occurrences
But there’s no Extract Subview as there was before.
Was Extract Subview intentionally removed in Xcode 26? Or is it hidden behind a new menu location or renamed?
Since the latest Xcode has become available users in our environment are seeing this error any time they try to launch a simulator (Primarily iOS devices, but others provided the same error) We have tested on 16.4 and 26.0.1 with various suggested fixes including uninstalling and reinstalling all of Xcode. Nothing has helped.
I am using the latest version of Xcode 16, and I have created a GPX file in my project. However, I am unable to see or select the file to simulate the GPS location. I have attempted to uninstall and reinstall Xcode completely, but the issue persists. Has anyone encountered a similar problem? How can I resolve this? Thank you.
Submitted feedback FB17075016
Xcode 16.3 release
macOS 15.4
iOS 18.4 / iPadOS 18.4 release builds
Memory graph fails to build when targeting physical devices running release builds referenced above. Memory graph will build against a simulator device.
After not happening to me for a few months, this issue has started hitting me again with currently %100 reproducability.
If turn on VPN on my Mac then instantly the developer certificates within the keychain become untrusted.
But that's not all, if VPN is then turned off the certificates do not revert to their trusted status but remain untrusted.
The consequence of this is that if VPN is turned on and then a build is perform, it fails, and the only way to fix things is to delete the cert(s) from they keychain and re-install them.
As a remote worker, having this happen several or even dozens of times a day is incredibly annoying and frustrating.
This issue has been occurring for literally years, sometimes it occurs very often, others while its quiet for a while, and has spanned multiple versions of Xcode and Mac OS. So whatever the cause is its endemic. It doesn't just affect myself, but all the members in my development team.
I'm currently using Xcode 14.1 RC 2 and Monterey but I've seen this issue occur with many versions of Xcode and Mac. (I'm using Cisco AnyConnect Secure Mobility Client).
If the VPN is somehow interfering/affecting the connectivity aspect when an attempt is made by Xcode to validate the certificate, then why does it not rectify itself after turning off VPN?
This is so so so so annoying.
Can somebody please comment on why this happens and if there's a way to prevent it.
Hi
I've downloaded the latest version of Xcode 14.2 but when I run the app in Simulator I can only test it on iOS16.2 Is there a way to run it in 16.3?
xcode 15.2, mac m2 mini, 14.2.1 sonoma
i need a pdf file to stage my app for screen shots for the market. icloud wont sync, cant drag files to the home screen or any screen, it just does not work.
i am at the end of my rope here, i just need some screen shots, my app is approved and ready
am i wrong>? is there a way to do this or is it just broken now in the name of (lazy) security?
edit--the more i read the more i angry and frustrated i get. this is broken and will not be fixed. i need to just workaround via email. so happy my second 100 dollar developer subscription bill is coming up!
Issue Report — Xcode 26.0 beta (17A5241e)
In Xcode 26.0 beta, double-clicking a file in the project navigator does not open it in a new tab as it normally should. Instead, it opens the file in the current editor window. Interestingly, Option-clicking a file still opens it in a new tab as expected.
I’ve confirmed that my Navigation preferences are properly set (see the attached screenshot), so this seems like a possible regression or bug in the current beta version.
When test support code relies on production code, a diamond can occur. If this occurs across packages, it can lead to duplicated symbols and incorrect behavior at runtime despite no warnings at build time. This only occurs in Xcode and top-level application testing. This doesn't occur when the code being tested is in a separate package.
I'm trying to understand how to correctly manage shared test support code which needs to access production code, or if this is the correct way and it is an Xcode bug.
For a minimized example project, see https://github.com/rnapier/SupportCode.
The setup includes three packages: Dependencies, which manages all the dependencies for the app and tests; Core which contains core logic and test support; and Feature, which relies on Core an contains feature-related logic and test support.
Building this system causes Core.framework to show up three times in DerivedData:
./App.app/PlugIns/AppTests.xctest/Frameworks/Core_59974D35D_PackageProduct.framework
./App.app/Frameworks/Core_59974D35D_PackageProduct.framework
./PackageFrameworks/Core_59974D35D_PackageProduct.framework
When unit tests are run, there is a collision on the symbol for Keychain:
objc[48914]: Class _TtC8Keychain8Keychain is implemented in both /Users/ornapier/Library/Developer/Xcode/DerivedData/App-grdjljgevqofhqgflgtrqvhvbtej/Build/Products/Debug-iphonesimulator/PackageFrameworks/Core_59974D35D_PackageProduct.framework/Core_59974D35D_PackageProduct (0x100a98118) and /Users/ornapier/Library/Developer/CoreSimulator/Devices/216C441E-4AE5-45EC-8E52-FA42D8562365/data/Containers/Bundle/Application/7197F2F2-EB26-42FF-B7DB-67116159897D/App.app/PlugIns/AppTests.xctest/AppTests (0x1011002c0). One of the two will be used. Which one is undefined.
This is not a benign warning. There are two distinct copies of _TtC8Keychain8Keychain and test cases will access one and the app will access a different one. This leads to mismatches when accessing static instances such as .shared.
I believe this dependency graph should work, and it does work as long as the top-level testing system is a Swift module. But if it is the application, it builds successfully, but behaves incorrectly in subtle ways.
On devices and simulators with iOS 26.1, the animation does not work correctly (the initial and final screens are distorted). I use open class func transition(with view: UIView, duration: TimeInterval, options: UIView.AnimationOptions = [], animations: (() -> Void)?, completion: ((Bool) -> Void)? = nil)
with options: .transitionFlipFromRight
We have an existing app in which we have implemented AppShortcuts. The snippet view works fine in iOS 17 while in iOS18 beta, it doesn't able to fetch color from xcassets. If we use system colours or UIColor it's working fine.
Not working
Color("progressColor")
Working
Color(uiColor: UIColor(named: "progressColor")!)
Color.red
Color(hex: "3881d3") // Note: We created Color extension to generate color from hex string.
I'm getting following message when launching #Playgrounds canvas with Xcode 26 beta 4.
Here are things I've tried:
Reinstall Xcode
Reinstall components
Removed derived data
Run Disk Utility to fix permissions
Tried to change Default Actor Isolation, Approachable Concurrency
Changed around settings on Schemes: Run: Options and Diagnostics
Created brand new project with default settings.
Filed FB19003005 in Feedback Assistant.
I'm surprised to see that I didn't see any posts on this during my search. So this could be isolated matter just to me.
We are preparing builds using Xcode 16.0 given we have a large set of users on iOS 12.
Now we have doubts wether we will run into issues if we ship using it (even if it compiles, archives and uploads successfully) given the table columns and content has changed since the last time we checked this table: https://developer.apple.com/support/xcode/.
1- Is the Deployment Targets range for Xcode 16 value correct for iOS? (On the 24th of February it had iOS 12-18, now it has iOS 15-18)
2- Are we OK to ship for iOS 12 using xcode 16.3?
Thanks,
Joao Garcia
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
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
How to download the runtime simulators for the most recent Xcode 26 beta? The current download command I’m using doesn’t seem to work, and I’m encountering the following issues:
The runtime simulator download command (xcodebuild) requires the version number to be specified explicitly. I’ve tried multiple variations of version names/numbers but haven’t been able to identify the correct naming convention used by Apple for the Xcode 26 beta simulator runtimes.
$ xcodebuild -downloadPlatform IOS -exportPath ~/Downloads -buildVersion 26
Finding content...iOS 26 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0
Finding content...iOS 26.0 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0 beta
Finding content...iOS 26.0 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion "26.0 beta"
Finding content...iOS 26.0 beta is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion "26.0_beta"
Finding content...iOS 26.0_beta is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0_beta
Finding content...iOS 26.0_beta is not available for download.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Is there a way to use CFBundleVersion instead of CI_BUILD_NUMBER from XCode Cloud's workflow on Web ?
We would like to have control over the major and minor version numbers of the build from the workflow.