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?

Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. "Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds." I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)

Hi, I am attempting to setup Xcode Cloud for my project. The repository for the project is in Azure Devops. When I look on the internet, I get the answer: Go to AppstoreConnect, your app, Xcode Cloud and configure the repo. However, in my version of Xcode I am immediately sent back to Xcode to configure it. When looking in this forum, I see some old Posts from 2022 and 2024 without any answer. I assume I need to pick 'Github Enterprise' as the GIT provider. If I do, It attempts to connect to devops.azure.com, which sounds about right. But then I get a permission error. I would like to configure Xcode Cloud to access Azure Devops using one of the PATs that I have configured. Has anybody been able to Mae this work? Or should I make a Mirror Repo in Github (ir BitBucket or Gitlab) and let Apple connect to that? Kind regards Wouter

I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.

我在xcode cloud授权github的时候, 提示: Xcode Cloud 与你的源代码控制提供商之间的连接未完成。但是github里查看app是安装好了

Description: I'm trying to set up Xcode Cloud for a tvOS project that uses Tuist for project generation. The workflow is created successfully, but when I try to manually start a build, no branches are listed — it just shows "There are no branches available." Setup: tvOS app project using Tuist 4.x for project generation Hosted on GitHub (private repository, organization) The .xcodeproj and .xcworkspace files were originally in .gitignore (standard practice for Tuist projects) ci_scripts/ci_post_clone.sh is configured to install Tuist and run tuist generate --no-open after cloning What I've tried: Removed *.xcodeproj and *.xcworkspace from .gitignore and committed the generated project.pbxproj to Git — branches still not visible Changed the "Project or Workspace" path in the workflow settings to match the actual location of project.pbxproj (Projects/App/.xcodeproj) — no change Temporarily changed the default branch to one that contains the committed .xcodeproj with project.pbxproj — still no branches available Verified GitHub App (Xcode Cloud) has proper repository access with read permissions for code, metadata, and pull requests Confirmed no webhook configuration issues (compared with another working repository that also has no webhooks) Key observation: When I switch the workflow's source repository to a different repository (a standard Xcode project, not Tuist-based) within the same organization, branches appear correctly. Switching back to the Tuist-based repository shows no branches again. This suggests the issue is specific to the repository structure, not GitHub permissions or workflow configuration. Project structure: Root/ ├── Workspace.swift # Tuist workspace definition ├── Tuist/ │ └── Package.swift # SPM dependencies ├── Projects/ │ └── App/ │ ├── Project.swift # Tuist project definition │ └── <project>.xcodeproj/ │ └── project.pbxproj ← (committed to Git) ├── <project>.xcodeproj/ # Root-level (no project.pbxproj, only xcshareddata/schemes) ├── ci_scripts/ │ └── ci_post_clone.sh # Installs Tuist & generates project └── .gitignore Environment: Xcode version: Latest Release (26.4) macOS: Latest Release (Tahoe 26.4) Tuist version: 4.161.0 Question How does Xcode Cloud discover branches for a repository? Does it require a valid .xcodeproj with project.pbxproj at a specific path on every branch? Is there a known limitation or recommended setup for Tuist-based projects where project files are generated at build time via ci_post_clone.sh?

Xcode Cloud builds fail at the export archive step. The critical log shows: Account "Session Proxy Provider": Unable to authenticate with App Store Connect Error Domain=DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)" And in DVTITunesSoftwareService.log: App Store Connect response failed with unknown failure; response (null); error (null) error: DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy Environment: Xcode Cloud, iOS app, team type Individual (S43L28SVX2) What I have ruled out: Regenerated all DISTRIBUTION_MANAGED certificates (per thread 744683) — portal API is reachable, certs issued successfully Removed an obsolete App Groups entitlement that was causing a secondary error — that error is now gone All agreements accepted, no pending legal items Failure persists across multiple builds with identical symptoms The developer portal API responds correctly. The failure is isolated to the App Store Connect store configuration endpoint specifically, where the proxy returns response (null) — no HTTP response at all. This appears identical to thread https://developer.apple.com/forums/thread/810658 where Apple confirmed the root cause was a backend API permission issue for the team requiring an Apple-side fix. Support case 102857550486 was opened but redirected to admin support without technical investigation. Has anyone else hit this recently, or can an Apple engineer look at the backend state for this team?

It's my first time I am configuring the Xcode cloud to build my project. Here is the crash and stack trace Stack trace One thing I noticed when I setup Xcode Cloud - it asked me to grant access to every public github library I have as dependency, I can't do that, as I am not owner or member of those libraries (firebase, swift algorithms, etc) when I tapped "Continue" there was an alert saying if I continue without granting access CI might not be able to fetch dependencies

I'm seeing this repository issue on my ASC Xcode Cloud page, and when I click "Reconnect" it shows me a lovely huge green checkmark with "GitHub has been successfully connected." but the error remains, and I cannot kick off new builds.

Hello, I have Xcode Cloud set up on a project with multiple targets. One target is a Framework that hosts a Swift Package that's used to host modules. I recently added a large number of files (at least 20,000) to some test targets and I can no longer access Xcode Cloud from the Cloud Reports section. Xcode prepares to analyze the project and then fails with Could not load Xcode Cloud Data Removing the files from the package results in the project being analyzed successfully. So it appears to be some sort of a timeout issue. Thank you

When I chose a watchOS Test and set the watch with latest watchOS on Xcode Cloud, I could not pass the CI because it showed "xcodebuild: error: Unable to find a destination matching the provided destination specifier: { platform:watchOS Simulator, id:9863C79E-3793-483E-BAA1-F96A0BD34005 }" I've change some destination, but it's not worked. Is there any idea what I can do? The watch app is along with the mobile, not standalone.

Did I saw right that Xcode Cloud will use Apple Silicon from now on ? What's the ETA for that ?

Is there a way for me to set CFBundleVersion before TestFlight and/or Notarization actions occur and have it stick? When I've tried doing this with ci_scripts or Script Phases, the system overwrites CFBundleVersion with the Xcode Cloud build number before publishing to TestFlight or notarizing. We have a rather odd setup where we have two apps which are built from the same source & historically have used identical build numbers. So e.g. App A build 3 is built from the same commit as App B build 3. We have a bunch of tooling & processes which assume this, but it's really tough to achieve on Xcode Cloud because the build numbers for two different projects get out of sync really quickly.