When running an Xcode Cloud workflow pinned to Xcode 26.1, macOS 26.1 and using a Test Destination for iPhone 15 Pro and iOS 26.1, the following error appears in the xcodebuild-build-for-testing.log: 2025-11-13T19:08:31.855137440Z xcodebuild: error: Unable to find a destination matching the provided destination specifier: 2025-11-13T19:08:31.855318998Z { platform:iOS Simulator, id:704F84C8-025F-4F70-B2D9-FF19B7DC098F } 2025-11-13T19:08:31.855362640Z 2025-11-13T19:08:31.855370957Z Ineligible destinations for the "Inbound" scheme: 2025-11-13T19:08:31.855381964Z { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device, error:iOS 26.1 is not installed. Please download and install the platform from Xcode > Settings > Components. } This can be fixed if ci_pre_xcodebuild.sh is updated with the following: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '{print $2}' | cut -d. -f1) if [ "$XCODE_VERSION" -ge 26 ]; then if xcodebuild -downloadPlatform iOS >/dev/null 2>&1; then echo "iOS platform is installed" else echo "iOS platform is not installed. Failing the build." exit 1 fi fi Changing the workflow to use "Latest Release" of Xcode (26.1), macOS (26.1) and the Latest Test Destination iOS (26.1) version provided also does not work.

Hi everyone, After disabling Xcode Cloud for my team, I tried to enable it again for my product. However, I keep seeing this message when reconnecting to my source control: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been about a week since I disabled it, but I still can’t re-enable Xcode Cloud. I’ve tried reconnecting through GitHub and Bitbucket, and both show the same message. Could anyone share: How long does this “processing” phase usually take? Is there a way to check or request reactivation manually? Team type: Organization Region: Japan Thank you in advance for any suggestions or similar experiences!

Hi everyone, After opting out of Xcode Cloud, I tried to set it up again for my product. However, I’m getting the following message when attempting to reconnect to my source control provider: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been 7 days since I opted out, and I still haven’t been able to re-enable Xcode Cloud. I’ve tried reconnecting both GitHub and Bitbucket, but the same message appears in both cases. I’d like to know: How long does the opt-out (deregistration) process usually take to complete? Is there any way to check the current status or expedite the reactivation process? Team Type: Organization Region: Japan Any insights or similar experiences would be greatly appreciated. Thank you in advance!

Hi We have a project with one app, where we have multiple schemes to create either a staging or release version of the app. We change the bundle identifier of the app so it's a separate app in app store connect. One staging app and one release app. We are trying to integrate Xcode cloud workflows, however, there's only one app visible in the Xcode cloud tab and when we create a workflow it gets automatically assigned to the staging app in app store connect. We cannot create the workflow under the release app in app store connect, as the manage workflows button is not visible until you've created the first workflow for an app in xcode. How can we create a workflow and force it to be associated with the release app in app store connect?

We have a repository that contains two components: The SDK codebase A sample app that uses the SDK for testing purposes We’ve set up an Xcode Cloud pipeline for the sample app. In this setup, the sample app references the SDK from a local path. Within the ci_post_clone script, we build the SDK project for both the simulator and device, create an .xcframework, and then build the sample app. Everything works fine — the sample app builds successfully, and the resulting archive is uploaded to Xcode Cloud as an artifact. However, I also want to share the generated .xcframework with customers by including it as an artifact in the pipeline. The issue is that the .xcframework doesn’t appear in the App Store Connect build artifacts. I’ve tried the following without success: Placing the .xcframework inside a folder named artifacts at both the repository root and the project root Copying the .xcframework to the $CI_ARCHIVE_PATH directory There isn’t much documentation available on custom artifact creation in Xcode Cloud. Can someone point me to proper documentation or confirm if this is supported? I assume it should be possible, as this is a common workflow for SDK pipelines.

Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning "ITMS-90035: Invalid Signature" TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. The thing is the archives which are not intended for testflight not App Store connect are not failing. I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) : even though certificats seems ok, in Xcode I see a dev certificate in the managed release and if I try to force a distribution certificate in the build I then get the following warning It looks like my managed profile is not behaving properly, like not embedding a distribution certificate. I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name. Anyone has any idea on what is causing those build fails on the archive?

Hi, our builds with a Test action in Xcode Cloud are failing because of an internal Xcode Cloud crash. We see the "red cloud with an X" icon, that indicates that it's an Xcode Cloud issue, and the message says "The Test - iOS action could not complete due to an error. The error may not occur on rebuild." but this has been happening for a while now, and for repeated builds. In the artifacts there is a crash log apparently related to the "ibtoold" process, has anybody had this issue before? Thanks

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

My project build failed in Xcode Cloud(works well in my local Mac), and the error shows: Preparing build for App Store Connect failed The error message is not clear enough to help us find the solution to fix it. Can anyone help with it?

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.

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?

Hi there, We’re encountering this error in all of our builds when using the latest Xcode and macOS: 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. In short, all builds are failing. I’ve tried fixing this by installing Metal and applying other solutions, but none of them worked reliably. Is there a way to ensure that the Metal Toolchain is installed on the CI machine?

Hi everyone, Starting today, my Xcode Cloud CI workflow can no longer successfully build iOS/macOS/visionOS targets. The Archive step does not report any errors, but the xcodebuild command hangs indefinitely and eventually fails with the following message: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. My iOS and macOS targets can still be built, but the build time has increased by 2-3x compared to before. That's interesting. After I removed the visionOS target, the iOS target also failed to build. Additionally, since today, I’ve noticed a significant increase in network-related errors in Xcode Cloud. There have been multiple failures to download dependencies from Homebrew or GitHub. I have confirmed that CI versions which previously built successfully are now failing, while running the same build commands locally works fine. Based on these observations, I suspect there may be an issue with the Xcode Cloud environment itself. Has anyone else encountered similar problems? Any suggestions or updates would 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 ?

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?

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.

We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.

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

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

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)))