So, our app imports CoreML and loads the CoreML models when starting up. Locally all tests succeed consistently. Running Tests on Xcode Cloud, they all fail with (UI and Unit Tests) App (6846) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal ill before establishing connection.)) the test instance is busy for 35min and then just aborts, with all tests failing. This sounds to me like the simulator is maybe showing some exception or is stuck? Or is it possible that xcode server runs in a special environment that gets stuck on loading CoreML models?

I have a workflow where I want to specifically run some tests in the iOS 18 simulator. All while using Xcode 26 on Xcode Cloud. In my Xcode Cloud workflow I can set the iOS version, but just iOS 16, 17 and 26, but no 18? I'm very confused here Not sure which is the right channel anyway to request support to Xcode Cloud too

We are integrating Xcode Cloud into a larger CI/CD pipeline and ran into a serious limitation that makes proper build status reporting nearly impossible. Currently, Xcode Cloud provides only the following custom script phases: • ci_post_clone.sh • ci_pre_xcodebuild.sh • ci_post_xcodebuild.sh However, if a build fails during the actual Xcode build phase (for example, due to a compilation error, unit test failure, or signing issue), the ci_post_xcodebuild.sh script does not run. This means there is no guaranteed way to execute cleanup steps or send external notifications (e.g., updating build status in Bitbucket, Slack, or any external CI system). In any robust CI/CD setup, it’s critical to have a “finally” or “always run” hook that executes regardless of build success or failure — similar to post blocks in Jenkins, finally steps in GitHub Actions, or after_script in GitLab CI. Without such a mechanism, we cannot reliably integrate Xcode Cloud with the rest of our automation and monitoring ecosystem. This effectively breaks standard CI/CD practices, since external systems will never know if a build failed unless they constantly poll the Xcode Cloud API. Feature request: Please add a new hook (e.g., ci_finally.sh or ci_post_build.sh) that always executes after the build, whether it succeeded, failed, or was canceled. This would make Xcode Cloud much more suitable for professional CI/CD environments and allow proper integration with third-party systems.

In courses like Compose interactive 3D content in Reality Composer Pro Realitykit Engineers recommended working with Reality Composer Pro to create RealityKit packages to embed in our Realitykit Xcode projects. And, comparing the workflow to Unity/Unreal, I can see the reasoning since it is nice to prepare scenes/materials/assets visually. Now when we also want to run a Xcode Cloud CI/CD pipeline this seems to come into conflict: When adding a basic *.usdz to the RealityKitContent.rkassets folder, every build we run on Xcode cloud fails with: Compile Reality Asset RealityKitContent.rkassets ❌realitytool requires Metal for this operation and it is not available in this build environment I have also found this related forum post here but it was specifically about compiling a *.skybox.

I've been getting intermittent failures on Xcode code compiling my app on multiple platforms because it fails to compile a metal shader. The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. Sometimes if I re-run it, it works fine. Then I'll run it again, and it will fail. If you tell me to file a feedback, please tell me what information would be useful and actionable, because this is all I have.

Hello everyone! I found that the Xcode Cloud workflows under my project are completely stuck. The tasks that are already running cannot be completed. Newly started tasks remain in the queued state forever and cannot be canceled. They are consuming my usage quota 😢. Has anyone else encountered the same issue?

Hi! For the past few days I have been experiencing slower builds in my workflows, without a clear reason of the cause as sometimes they run with the old usual time. I tried contacting the Developer Support without success in finding out the reason of these issues, the case number was 102661768064. As an example, I have a workflow for Pull request checks that involves testing and analyzing. This usually ran for 11-15mins, but now it could take up to 30mins or more. Looking into the logs it just seems that the machine it's particularly slow, then in another build it goes with usual times again. As an example, below are the summaries of two builds of the same branch: Being in the free tier, these new long times are burning my free time quite faster and probably will need to look into running this checks in GitHub Actions if it doesn't improve. A hint of what might be wrong is also found in an error in the test workflow, which denotes a problem booting a simulator. Any help on this will be appreciated, thanks!

Hi, We successfully migrated to the new AppIcon from Icon Composer. Everything works great on simulator and on real devices. We also released a manually generated build that works great. However when we build the same project from Xcode Cloud we get the following error: None of the input catalogs contained a matching stickers icon set, app icon set, or icon stack named "AppIcon" The previous line seems to indicate that no icon is passed: /Applications/Xcode.app/Contents/Developer/usr/bin/actool /Volumes/workspace/repository/Mail/Assets.xcassets --compile /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_output/thinned --output-format human-readable-text --notices --warnings --export-dependency-info /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_dependencies_thinned --output-partial-info-plist /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_generated_info.plist_thinned --app-icon AppIcon --accent-color AccentColor --compress-pngs --enable-on-demand-resources YES --development-region en --target-device iphone --target-device ipad --minimum-deployment-target 15.0 --platform iphoneos However when I archive locally, the icon seems correctly referenced: /Applications/Xcode.app/Contents/Developer/usr/bin/actool /Users/<my name>/Developer/ios/infomaniak/apps/ios-kMail/Mail/Resources/AppIcon.icon /Users/<my name>/Developer/ios/infomaniak/apps/ios-kMail/Mail/Resources/Assets.xcassets --compile /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_output/thinned --output-format human-readable-text --notices --warnings --export-dependency-info /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_dependencies_thinned --output-partial-info-plist /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_generated_info.plist_thinned --app-icon AppIcon --accent-color AccentColor --compress-pngs --enable-on-demand-resources YES --development-region en --target-device iphone --target-device ipad --minimum-deployment-target 15.0 --platform iphoneos Has anyone encountered a similar issue ?

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?

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.

Some of my apps are configured to use Xcode Cloud. Some time ago, this service was blocked for developers from Russia. I want to transfer one of my apps to another account. But there is the following requirement in the checklist: "You must remove all Xcode Cloud related data from the app you want transferred." I can't do it myself because I see an error in App Store Connect: "The page you’re looking for can’t be found.". It is also not available through Xcode. I would like to delete all Xcode Cloud settings for all my apps. Can you help me with this?

Hi I have an developer app tied that is the account owner for our ABM and also for our Apple Developer account. When i go to the developer app and try to purchase additional hours it doesnt let me "Apple account cant be used to make purchases" And i am the account holder for both. The email tied to it is an "username/@/domain.appleid.com". Any help appreciated

We would like to request an enhancement to Xcode Cloud workflows to support skipping builds when a GitHub Pull Request is in Draft state. Our team frequently collaborates on pull requests that go through multiple iterations during the code review cycle. Each small commit or push triggers an Xcode Cloud workflow run, even if the PR is still in draft and not ready for final review or CI validation. This leads to: Wasted compute resources and time on draft work that is not yet intended for integration. Increased noise in Xcode Cloud logs and dashboards. Longer feedback cycles for meaningful PRs, since draft workflows compete for available concurrency. A simple option in the workflow configuration (e.g., “Skip runs for draft pull requests”) would address this problem by: Reducing unnecessary workflow executions. Freeing up capacity for production-ready and review-ready builds. Improving overall developer productivity by aligning CI runs with the actual readiness of a PR. This feature would be especially valuable for teams with frequent collaboration and long-lived PRs. Thank you for considering this request—we believe it would significantly improve the efficiency of Xcode Cloud for real-world development workflows.

Hey, We're crunching to get our products ready for the announcements next week but are being slowed down by Xcode Cloud. Builds are failing and are extremely slow. We're using the latest Xcode beta and latest macOS release so we can upload our builds continuously to TestFlight. We're seeing builds taking up to almost an hour, even though takes around 10-15 minutes when it doesn't fail. The errors we're seeing seem to be timeout, for example: Showing All Errors Only The step invocation hit a user timeout. The xcodebuild build invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Here are links to some builds which have been restarted multiple times but keep failing for reasons out of our control. Please advice on how to get unblocked. https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/8da12ae3-b454-4810-abe8-829f1af56a54 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/ee7b1fae-1363-4265-9d64-692434b7ebf2 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/fd915140-db2c-4b3b-bff4-16939c22665a

So my xcode cloud build have been stuck for 12 hours, is there something wrong with me or the service isnt working rn?

Hi Apple DTS & community folks, I’m reaching out regarding an issue we’ve encountered with the com.apple.developer.mail-client capability for our app (bundle identifier: so.notion.Mail). We were granted this entitlement last week to allow the app to be set as a default Mail client. While everything works as expected when archiving and distributing builds locally in Xcode, we’re running into a problem when using Xcode Cloud. Specifically, Xcode Cloud attempts to archive and distribute an Ad-Hoc build, but the Ad-Hoc provisioning profile does not include this special entitlement. Since we’re using Xcode-managed profiles, we don’t have the ability to create or adjust an explicit profile ourselves. This issue only arises in Xcode Cloud—local distribution works unless we explicitly attempt an Ad-Hoc build (which is not our intent). I’ve included a screenshot of the error for reference. We found this forum post describing the same issue, where the resolution was Apple enabling the entitlement for Ad-Hoc builds. We’d like to request that Apple enable this capability for Ad-Hoc builds for the Notion Mail application so that Xcode Cloud distribution functions correctly. Thank you for your help!

We have a simple workflow that just runs the Test action on my unit_tests scheme (see Xcode Cloud workflow configuration screenshot). The workflow is configured to use Xcode 16.4 (Latest Release), macOS Sequoia 15.6 (Latest Release), and iOS 18.0 simulators. Today, this workflow has been consistently running indefinitely. The Xcode cloud runner tries to launch the simulator to execute the tests, but it fails. See the error message in the screenshot from Xcode Cloud logs. Link to corresponding build is in my Feedback Assistant ticket. It continues to retry this operation for a very long time — I had one job that ran for over 90 minutes. Link to corresponding build also in that same Feedback Assistant ticket. Are Xcode Cloud runners perhaps currently undergoing maintenance? Or is something else going on. I would appreciate if Xcode Cloud usage from today could be refunded to my team’s account. Feedback Assistant ticket #FB20195292. Error message: MyApp encountered an error (Failed to prepare device 'iPhone 16' for impending launch. (Underlying Error: Unable to boot the Simulator. launchd failed to respond. (Underlying Error: Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding)))

I have now signed out of my account in Xcode, quit the application, signed back in, and also cleared the Xcode derived data and cache. However, I am still receiving the 401 Unauthorized error Any operation related to Xcode Cloud (e.g., viewing the dashboard, creating a workflow) fails immediately across all Xcode projects, including brand-new empty projects. The error is consistent and always appears as: API Invalid status code: 401. Domain: XcodeCloudCombineAPI.XCCResponseError Code: 1 System Information: macOS Version 15.6.1 (Build 24G90) "details" : "Error alert: API Invalid status code: 401.: XCCResponseError(responseErrorType: XcodeCloudCombineAPI.XCCResponseError.XCCResponseErrorType.invalidStatusCode(XcodeCloudCombineAPI.LegacyHttpStatus.unauthorized), requestUrl: Optional(https://appstoreconnect.apple.com/ci/api/teams//apps/find?bundle_id=), traceId: Optional("2ab09bea8da9ef39"), retryAfterSecsStr: nil, response: Optional(<NSHTTPURLResponse: 0x600000c6a800> { URL: https://appstoreconnect.apple.com/ci/api/teams//apps/find?bundle_id=} { Status Code: 401, Headers {\n "Content-Length" = (\n 0\n );\n Date = (\n "Fri, 05 Sep 2025 10:04:07 GMT"\n );\n Server = (\n nginx\n );\n "Set-Cookie" = (\n "dqsid=; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Path=/; Secure; HTTPOnly",\n "dqsid=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE3NTcwNjY2NDQsImp0aSI6IlNQZ1FxVXd1UFF1UjI1X2wtZ2ZjN2cifQ.uoE9MRTx-TCY03Sw1qgMBcWrPVA8adtKd-nOZVwllS4; Max-Age=1800; Expires=Fri, 05 Sep 2025 10:34:04 GMT; Path=/; Secure; HTTPOnly"\n );\n "Strict-Transport-Security" = (\n "max-age=31536000; includeSubDomains; preload"\n );\n "x-apple-jingle-correlation-key" = (\n ZNGYRW2NJQJKAYDKU5FGCY6VVE\n );\n "x-b3-traceid" = (\n 2ab09bea8da9ef39\n );\n "x-cache-status" = (\n BYPASS\n );\n "x-content-security-policy" = (\n "script-src 'self' *.apple.com"\n );\n "x-content-type-options" = (\n nosniff\n );\n "x-daiquiri-instance" = (\n "daiquiri:15751001:mr36p00it-hyhk07174801:7987:25RELEASE91:daiquiri-amp-dsce-asc-int-002-mr",\n "daiquiri:18493001:mr85p00it-hyhk03154801:7987:25RELEASE91:daiquiri-amp-all-shared-ext-001-mr"\n );\n "x-frame-options" = (\n SAMEORIGIN\n );\n "x-via" = (\n "2.0 PS-WUH-01zra68 [BYPASS]"\n );\n "x-ws-request-id" = (\n "68bab594_PS-WUH-01zra68_27159-54435"\n );\n "x-xss-protection" = (\n "1; mode=block"\n );\n} }))\nError Description: Optional("API Invalid status code: 401.")\nRecovery Suggestion: nil\nHelp Anchor: nil",

Xcode 26 RC is not available on Xcode Cloud. This is a serious blocker affecting developers trying to be on App Store on day 1 of the OS 26 release. Is there an estimate when this can be in place?

I cannot setup a workflow - every time it says "This operation could not be completed" after granting access to the source code. I removed the app from AppStore Connect, I logged out from Xcode, removed and reset the app from Github, initialized a new repository, reset Xcode Derived Data, reset the Profiles and Certificates. I tried everything and nothing worked. Any help?