Hello, We've been using Xcode Cloud for a year in order to run a CI workflow : run the unit-tests, compile the iOS binaries and upload them to TestFlight. The "plug'n play" interface of Xcode Cloud is much appreciated. We also have a Mac-mini that is capable of running those unit-tests locally. It uses Jetbrain's Teamcity solution and some shell scripts we have written. Both Xcode Cloud and the Mac-mini run the unit-tests in the same duration : around 2 minutes. But Xcode Cloud has an additional step "Check project configuration" / "Catalog app product and scheme metadata". It takes around 6 minutes to complete ! We are often working in duo sessions "developer / tester", to clear a task list. In that context, those 6 minutes are frustrating. Plus, they are followed by an even-more-frustrating-very-long-Testflight-processing-time. Bottom line is we are thinking of moving our CI workflow back to the local Mac-mini, at least until someone has an idea about how we could speed up the Xcode Cloud chain ? best regards, l.

I've been using Xcode server for several years to run some UI tests for assurance quality. Even though it has some limitations and bugs, compared to Xcode Cloud, there is still a way to use it. In my case, it's mandatory, the UI Tests are running while connected to a local server application. Since I've updated to macOS 13.3 and Xcode 14.3, the user configured to run the tests is reported as "Logged out" on the Xcode Settings window, even though it is, in fact, logged in. Complete new install of the system, new install of Xcode and other tools : same results. I have a bunch of logs related to Xcode Server Builder in the console, but none is reported as an "error". Do someone have the same phenomenon ?

I've been using a shell script for several years, to reset / create the list of simulators I use with my projects. It's simply a bunch of calls of "xcrun simctl delete" and "create", with the proper simulators and sdk identifiers. With the last update of macOS 13.3 and Xcode 14.3, the behavior has changed. The simulators are properly created, I can see them in the "Devices and Simulators" window. But they don't show anymore in the Xcode "run destination" dropdown menu (except, surprisingly, two of them, always the same). After having try and understand the reason for a long time, I saw that if I change the value of "Show run destination" field, from "Automatic" to "Always" in the "Devices and Simulators" window, THEN the simulator shows in the dropdown menu. Did someone noticed the same effect ? Do someone know if I can control this field value from the "xcun simctl" command ? thank you all for any information, cheers, loïc b.

I've been using Xcode Server for a few days for the continuous integration of our projects. Most of the time, it works as expected : the projects compiles, the unit tests are executed with success, then I have a post-integration script that compiles an archive and upload it to TestFlight (using Fastlane). It works. Most of the time... Once in a while, I get a "internal-processing-error" value (instead of "success" or "warnings") in XCS_INTEGRATION_RESULT variable, after the unit tests have passed. I've been trying to look into the bot logs to find any useful information, but no luck 'til now. Does anyone have an idea about what I could do to move forward on this issue ?