With Xcode 26.3, and beta 26.4 (under macOS 26.4 Beta (25E5223i)) my loaded platforms for canvas and simulators keep disappearing. Try to add platforms, and the download just sits there.

I've yet to encounter these errors when running UI tests locally, but I'd estimate that 80-90% of my test runs on Xcode Cloud fail due to it. I'm just testing with iPhone simulators, I've set it to retry on failure, but no luck. Is there a setting or something I can tweak in my test code to improve the situation? I am on the latest xcode/iOS dev betas - but it was doing this before I switched to them from.

Showing All Messages [!] Error installing FBSDKLoginKit [!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20260316-6574-ros9od/file.zip https://github.com/facebook/facebook-ios-sdk/releases/download/v18.0.2/FacebookSDK_Dynamic.xcframework.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.16.2 cocoapods-downloader/2.1' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 curl: (35) Recv failure: Connection reset by peer Command exited with non-zero exit-code: 1 Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.

Hello, Our build in Xcode Cloud uses gradle via a custom script. Today we're seeing persistent errors when our build job attempts to download the Gradle binary in the Xcode Cloud env. Run custom shell script 'Build Shared KMP Framework' Downloading https://services.gradle.org/distributions/gradle-8.13-bin.zip Exception in thread "main" java.net.ConnectException: Connection refused at java.base/sun.nio.ch.Net.pollConnect(Native Method) So we're currently blocked from submitting an app update. Can an Xcode Cloud engineer please comment regarding whether this is an ephemeral issue related to other networking issues reported in the forum here or if this warrants other investigation on our side?

Recently, I have trouble with my Xcode Cloud builds, where they seemingly complete, but the very final step does not happen. I am building from the same codebase for both macOS and iOS (I have two “Archive” steps in my workflow, one for iOS and one for macOS). The iOS one usually completes fast without problems. The macOS log ending looks like this, and remains stuck forever, with the macOS build in the “spinning progress” state and never completing. Is there something I can do on my end to make this work better? I would not want to go back to manual builds, Xcode Cloud is convenient and was working well for a while, but this is really annoying lately.

Possible a duplicate of this resolved post from November, but I can't access any Xcode Cloud artefacts with the message "You are not authorized to access this team’s resources." Trying to access from within Xcode itself crashes Xcode 🙃

Am I doing something wrong? FB18269317

Hello, When archiving a binary with Xcode, I've always kept my archives in the Organizer so I can symbolicate crash logs using the dSYM files. I've been thinking about moving to Xcode Cloud for archiving. Will crash logs still be symbolicated and readable in the Xcode Organizer? Thank you, Axel

I'm setting up a first workflow in Xcode Cloud and when I go through the flow and reach the 'Grant Access to your source code' pane, my projects repo is listed as primary and has a green checkmark next to it, but one of my SPM dependencies does not. When I press the 'Grant Access' it launches AppStoreConnect which complains the repo can't be found or I don't have the correct admin permissions. I'm using BitBucket Cloud and both repos are mine and I am the admin for both. Xcode itself will build the dependency locally correctly. I did see that the dependent SPM package needs a Package.resolved checked in, which I've now done, but I can still no longer get past the Grant Access step. When I try to add myself as admin to the dependent repo, BitBucket says I can't be added because I'm already an admin. This is the same for the projects primary repo as well. But Xcode still thinks I only have read access. How do I get passed this? Xcode isn't even telling me what repo is troublesome: { "category" : "xcode-cloud-data", "column" : "23", "subsystem" : "com.apple.dt.XcodeCloudKit", "details" : "Error alert: You must have Admin or Write access to your repository. Your current permission level is read.: ModelErrorResponseError(error: XcodeCloudAPI.Components.Schemas.ErrorResponse(message: \"You must have Admin or Write access to your repository. Your current permission level is read.\", errorKey: nil, helpUrl: nil, details: [], body: nil, actions: []), httpStatus: XcodeCloudCombineAPI.LegacyHttpStatus.badRequest, traceId: Optional(\"ee71bf64b8cf2c27\"), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/69a6de89-4b61-47e3-e053-5b8c7c11a4d1\/products-v2\/A80C7CA9-25F0-4DCA-B7CC-D789A5022B88))\nError Description: Optional(\"You must have Admin or Write access to your repository. Your current permission level is read.\")\nRecovery Suggestion: nil\nHelp Anchor: nil", "createdAt" : "2025-06-28T18:49:15Z", "level" : "info", "filename" : "Logger+Additions.swift", "funcName" : "logError(_:)", "line" : "36" },

My post-build script takes the "developeridexport" archive export, zips it up and uses notarytool to notarize it. I then add the .zip to a .dmg disk image. The next step is to codesign the disk image before notarizing that too. The issue is my Developer ID Application certificate is not accessible to the build host. (When I was doing this in Microsoft AppCenter (now defunct), it had a copy of my Developer ID Application certificate.) What steps do I need to take to get the disk image signed for notarization? Thanks! Lance

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

Just learnt today that personal development teams do not support the Push Notifications and iCloud capabilities, is there any workaround besides pay another 99 for an enterprise development account? Thanks in advance.

We build TestFlight/App Store builds of our app through Xcode Cloud. Our app uses Metal shaders so we install the Metal toolchain through a ci_pre_xcodebuild.sh script which simply runs: xcodebuild -downloadComponent metalToolchain in our Xcode Cloud builds. This has been working well for us for the last 6 months or so, but since yesterday (March 5) we have been seeing consistent failures when running this script in our Xcode Cloud builds: Beginning asset download... 2026-03-06 04:14:34.727 xcodebuild[13315:58523] Writing error result bundle to /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/ResultBundle_2026-06-03_04-14-0034.xcresult xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 17C7003j; }) Prior to Mar 5 it looks like the toolchain image which was being downloaded/installed was 17C519 but this has now changed to 17C7003j. We haven't changed anything with our Xcode Cloud workflow setup, and the same macOS/Xcode images are being used for the workflow runs (macOS Tahoe 26.2 (25C56) and Xcode 26.3 (17C529) respectively) now as when our builds were succeeding a few days ago. What's the best way to resolve this issue? Looks like we can't even pass an image identifier to xcodebuild -downloadComponent so we're a bit stuck here.

I have checked that my scheme is shared and I do in fact have the scheme in my xcode project. But whenever I try to run Xcode cloud, it fails with the message that "A scheme named 'MyAppScheme' does not exist in MyAppProject.xcodeproj" Any tips on what I could be doing wrong?

Dear We try to generate IPA with Xcode Cloud but this task fail in Export archive phase (Export archive for app-store distribution). The error that appear in the archive logs is: error: exportArchive Provisioning profile "iOS Team Store Provisioning Profile: cl.app.myapp" doesn't include the com.apple.CommCenter.fine-grained entitlement. Any idea about to resolve this problem ? king regards

I've recently added iCloud backup on my chat app. Conversations are backing up fine but some users are losing their chats and when I see the telemetry it show "BAD_REQUEST" error. I couldn't find any details or solution for it. Does anyone has any idea what it could be? My development scheme is already fully deployed to production.

I am trying to find answers to the following questions about the XCode Cloud infrastructure for compliance purposes, but could not find it in the documentation. Where is the Xcode Cloud infrastructure hosted? Is there any way to specify that your builds happen in the US only? Does Xcode Cloud infra have any SLA on uptime? Does XCode Cloud meet any kind security compliance standards?

My Xcode Cloud workflows tell me the 'Latest Release' Xcode that it's using is Xcode 16.1 Release Candidate (16B40) Obviously that is well out of date at this point, plus, an RC is not a release version. How can I tell Xcode Cloud to always use the latest (non-RC) release version?

Hello guys, I currently have a problem with Xcode cloud. When I setup a simple workflow in my Xcode project that just archives it and builds the project for TestFlight Internal testing, it will fail and give the following error: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “DropIn.app/DropIn” 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. I've already been searching for solutions and double checked the documentation. My Xcode project is a simple iOS app with the app target and two other targets for tests and UI tests. I made sure the checkbox "Automatically manage signing" is ticked in all targets. The workflow has only one action "Archive - iOS" with TestFlight (Internal Testing Only) and a post-action "TestFlight Internal Testing - iOS" with an internal testing group assigned. I've seen people having similar problems where it turned out they had a non roman character in their name? This would also affect me if that's the case, since my name includes "ö". I also checked on app store connect and already deleted xcode cloud data, removed all certificates recreated the workflow, but it still gives this error. Any ideas on how to fix this?