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?
Xcode Cloud
RSS for tagAutomate workflows to test, analyze, build, and distribute your app, and integrate them with other developer tools, such as TestFlight and App Store Connect.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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
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
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!
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.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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.
Hi,
Overview
I am using Xcode Cloud for my multi platform app.
The macOS test case fails, however the iOS test case runs and succeeds.
I don't have any UI test cases written, the test case are simple and have nothing platform (macOS) specific.
Questions
What can I do to fix this?
Is there any user privileges needed to launch the macOS app for testing? I ask because when I ran the UI tests locally it launched the app and asked for my macOS user password. Just wondering if that is the reason it didn't launch in Xcode Cloud.
Error:
<Appname> encountered an error (Failed to install or launch the test runner. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult.(Underlying Error: Could not launch "AppnameTests. The LaunchServices launcher has returned an error. Please check the system logs for
the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed) )))
× Could not launch "<Appname>"
× Could not launch "AppnameTests"
× AppnameUITests.testExample()
Failed to get launch progress for <XCUIApplicationImpl: 0x600000564630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.app>: Could not launch "app name". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:28
* AppnameUITests.testLaunchPerformance)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed))
AppnameUITests.swift:37 g
* AppnameUITestsLaunchTests.testLaunch)
Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/Testroducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed.
I use xcode to rename a view in my project. It renamed the file, the struct, and all related items. However; since doing that my xcode cloud workflow fails, indicating that the it cannot find it in scope.
I have confirmed that the file shows up in my BuildPhases - Compile Sources. I have confirmed it exists in my git repo, but Xcode Cloud still fails to find it in scope.
I have confirmed it shows up in the correct Target Membership. I even tried removing it from the BuildPhases and re-adding it.
How can I resolve this issue? Is there something else I can look at?
btw, application builds fine locally on my machine.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
My organization just started having problems with Xcode Cloud this week.
We have created a pretty simple 'Build on Pull Request'. The problem is our builds have started failing immediately because with the error.
"Could not resolve package dependencies:"
What is even more frustrating is the dependency that reported failed seem to changes every time.
This did not happen before this week.
Our build process is fairly vanilla, through Xcode. (We are NOT using CLI xcodebuild)
I can build a locally just fine from a clean build, and cleaning derived data.
Nothing has changed in our dependencies.
We are not using any private dependencies.
So I am stumped on what else to do how to debug, and fix this, because I am not sure how to encourage the Xcode Cloud build runner/server that the dependences are available and to jsut go get them.
Any help would be great, because we just started using Xcode Cloud to get away from Fastlane (which was causing problems), and it would be frustrating if this is a sign of things to come.
Sincerely,
Stan
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Swift Packages
Developer Tools
Continuous Integration
Xcode Cloud
Hi,
I'm trying to use the change url functionality to switch my Xcode Cloud setup from Gitlab.com to my self hosted Gitlab instance. The setup process completes successfully, however, Xcode Cloud does not create any web hooks in my repo and also is not able to fetch any branch/tag information from the Gitlab instance.
There is also no error displayed on Xcode Cloud UI. I even tried to debug by looking at requests on my server to see if there are any clues, to no avail.
The only clue seems to be that in my repositories page, I see the instance listed but the row is highlighted red (which I assume means there's an issue with the connection). The last accessed date is also empty. The call to the /repos-v3 endpoint from App Store Connect seems to indicate there's an authentication issue:
{
"primary_repos" : [ {
"repo" : {
"id" : "xxxxxxxxxxx",
"http_clone_url" : "xxxxxxxxxxx",
"owner_name" : "xxxxxxxxxxx",
"repo_name" : "xxxxxxxxxxx-ios",
"repo_id" : "7",
"provider" : "gitlab-hosted",
"ssh_clone_url" : "ssh://xxxxxxxxxxx",
"scp_clone_url" : "git@xxxxxxxxxxx",
"default_branch" : "master"
},
"authorization_state" : "unauthorized"
} ],
"additional_repos" : [ ],
"unauthorized_repos" : [ ],
"revoked_repos" : [ ]
}
On my end, when I try to add the repository to Xcode Cloud, I see a few requests to my GitLab instance, all of which succeed with 200:
{"time":"2025-03-11T21:10:26.217Z","severity":"INFO","duration_s":0.05674,"db_duration_s":0.00567,"view_duration_s":0.05107,"status":200,"method":"GET","path":"/api/v4/user",....
{"time":"2025-03-11T21:10:26.797Z","severity":"INFO","duration_s":0.16682,"db_duration_s":0.02024,"view_duration_s":0.14658,"status":200,"method":"GET","path":"/api/v4/projects/xxxxxx%2Fxxxxxx-ios",....
{"time":"2025-03-11T21:10:28.298Z","severity":"INFO","duration_s":0.06617,"db_duration_s":0.00835,"view_duration_s":0.05782,"status":200,"method":"GET","path":"/api/v4/user",....
{"time":"2025-03-11T21:10:28.867Z","severity":"INFO","duration_s":0.21071,"db_duration_s":0.03075,"view_duration_s":0.17996,"status":200,"method":"GET","path":"/api/v4/projects/xxxxxx%2Fxxxxxx-ios",....
{"time":"2025-03-11T21:10:30.621Z","severity":"INFO","duration_s":0.15613,"db_duration_s":0.01842,"view_duration_s":0.13771,"status":200,"method":"GET","path":"/api/v4/projects/7",....
{"time":"2025-03-11T21:10:31.239Z","severity":"INFO","duration_s":0.1672,"db_duration_s":0.01828,"view_duration_s":0.14892,"status":200,"method":"GET","path":"/api/v4/projects/7",.....
At this point I'm sure this is some sort of a bug with Xcode Cloud since the requests do succeed but Xcode Cloud is unable to process the responses and identify the correct branches and tags, as well as set the web hook for the repo.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
App Store Connect
App Store Connect API
Xcode Cloud
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 🙃
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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"
},
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
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
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Signing Certificates
Code Signing
Developer ID
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.
The build status has a green check in Xcode Cloud, but TestFlight see no builds and suggest that I submit one. Then it provides a link to an incredibly unhelpful list of upload tools, at least one of which suggests creating a developer account!!!
All our builds getting stuck on the que.
https://developer.apple.com/system-status/
is not showing xcode cloud as down.
Hello, when I open the "Cloud" tab in the Report navigator, it shows "Failed to analyze workspace" and I cannot do anything. I can't start a build, nor can I manage or create workflows. All options are greyed out.
When loading the project, in Console I see the following errors from Xcode:
fault 11:07:19.805349+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
error 11:07:19.816641+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48
1 XcodeCloudKit 0x00000001192583c4 $s13XcodeCloudKit26ShellBasedProjectDescriberPAAE17describePublishery7Combine03AnyI0Vy6OutputQzs5Error_pG5InputQzFAKs5Int32V_10Foundation4DataVARtcfU_AA021AllArchivableProductsdG0V_Tg5 + 2012
2 XcodeCloudKit 0x000000011925ec90 $ss5Int32V10Foundation4DataVAE7Combine12AnyPublisherVy6Output13XcodeCloudKit26ShellBasedProjectDescriberPQzs5Error_pGIegyggo_AB8exitCode_AE6stdoutAE6stderrtAOIegnr_AjKRzlTRAJ021AllArchivableProductskN0V_TG5TA + 40
3 Combine 0x00000001a072351c $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2009FAF507AE039LLC7receiveyAA11SubscribersO6DemandV6OutputQy_F + 300
4 Combine 0x00000001a0725128 $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2<…>
<<
fault 11:07:19.822299+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
fault 11:07:19.822405+0100 Xcode ❌❌❌ Assertion failure #0 in <private>
error 11:07:19.824577+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48
1 XcodeCloudKit 0x00000001195e088c $s13XcodeCloudKit17DiscoveredProductO16DescriptorsCacheC13updatePlanner11environmentyAA21DeploymentEnvironmentO_tFys6ResultOySayAC0E10DescriptorVGs5Error_pGcfU_ + 740
2 XcodeCloudKit 0x0000000119289fa8 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7SchemasO13BuildArtifactVGsAQ_pG_Tg5Tm + 68
3 XcodeCloudKit 0x00000001192a1ef4 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7Sc<…>
<<
Obtained by filtering by xcode-cloud-assertion category.
Is there anything I can do to fix this? Thanks!