I'm getting this error, don't really understand why... Showing All Errors Only Build Archive Export archive for ad-hoc distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for development distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for app-store distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Activity Log Complete 6/26/25, 10:06 PM 0.4 seconds

We just changed the repository from Bitbucket > Github. While all connected successfully, none of the branches are appearing. I understand usually it takes time (cache etc) but its been a good few hours. Also tried to remove the integration and re-setup but to no avail.

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!

I have two apps in App Store Connect (same app but different bundle IDs), and I would like to manage workflows for both. However, when configuring workflows, although both apps appear on the list for configuration at first, selecting and configuring the first will be the only app available, since after that, there's no way to add the other app. It looks like a bug, but I couldn't find any additional reports of this case while browsing the web.

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",

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?

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?

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

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.

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.

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?

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!

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.

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally. So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly? You can find a detailed instruction how server is launched on a github page I provided.

Hi, Our team uses Xcode Cloud to run unit tests, and since around November, we’ve been frequently experiencing timeouts with the following type of process: @Test func hogeTest() async { // do something hoge.do() // wait until done await wait(condition: { hoge.isDone }) // test result #expect(hoge.isSucceeded) } private func wait(condition: () async -> Bool, timeout: TimeInterval = 0.5, pollingInterval: TimeInterval = 0.01) async throws { let deadline = Date().addingTimeInterval(timeout) while Date() < deadline { if await condition() { return } try await Task.sleep(nanoseconds: UInt64(round(pollingInterval * TimeInterval(NSEC_PER_SEC)))) } Issue.record("timeout") } Although sleep is supposed to wait for only a few milliseconds, there are cases where it takes more than 10 seconds, leading to a timeout. What could be causing this instability in the sleep duration? Additionally, if there are other recommended ways to implement polling and waiting in Swift Testing, I would appreciate it if you could share them. A feedback report (FB15899163) has already been submitted. Best regards,

I have an existing project, that's hosted in a self-hosted gitlab instance. Git works through terminal just fine (and has for years!) and the Source Control Navigator pane in Xcode shows the remote repository. However when I try to setup Xcode cloud I get a warning that there's the project does not hav a remote repository. I've tried clearing derived data, cleaning the build folder, restarting to no avail. I even tried creating a new project in Xcode, and having Xcode create the remote repository (which it did successfully). But no matter what I try it will not recognize the remote repository. I've also tried adding another remote origin, and I can see it just fine in the Xcode Source Control pane, but the Xcode cloud setup does not recognize it. Any suggestions?

All tests build and run locally just fine. Xcode Cloud can build my code, but always fails to run tests with the below errors. How can I even begin to troubleshoot this? I think my setup is pretty straightforward. Just a simple test plan that execute some unit tests with Swift Testing. Run command: 'xcodebuild test-without-building -destination 'platform=iOS Simulator,id=1EB80431-1A0B-4AD8-8EA6-968EA09C3F23' -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStream679e7ce9-a095-4be5-8dfa-4c9df982e547.json -IDEPostProgressNotifications=YES -DTDKDisableSymbolCopying=YES -test-timeouts-enabled YES -maximum-test-execution-time-allowance 1800 -hideShellScriptEnvironment -maximum-parallel-testing-workers 8 -testProductsPath /Volumes/workspace/TestProducts.xctestproducts' (6378) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal ill before starting test execution.)) May be related to: https://developer.apple.com/forums/thread/725660