Hi, I have Xcode Cloud with a start condition to start a build when any tag is pushed. Going into the settings repositories section it has a last accessed date which is before the latest push to does not appear accessing this anymore. I tried to refresh the connection but even this did not appear to do anything. If I try to remove the repo there is a Primary rep cannot be removed error. How do I get Xcode Cloud to starting receiving tag changes and automatically start building again? Also when I try and start a build manually, I still cannot "see" the latest tag. Thanks Ants

When setting our workflow to use Xcode 27 beta 5, the pipelines fail with the following (from IDEDistribution.critical.log): 2026-08-13 11:01:14 +0000 [MT] Command line name "app-store" is deprecated. Use "app-store-connect" instead. 2026-08-13 11:01:14 +0000 App Store Connect request for store configuration failed for account Session Proxy Provider (Account "Session Proxy Provider": Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)")) We're a multi tenant app (same code/project, multiple apps), so we've attempted this on two different AppStore Connect accounts, both resulting in the same error. Distributing from Xcode 27 beta 5 running on local machine works fine. For any Apple folks reading, I've filed a feedback (FB24286100) with links to multiple builds failing.

Membership began 1 month ago. I opened 9 tickets. No response received to date from the Support Team. "Before uploading a build of your app to App Store Connect, first create an app record in your App Store Connect account." https://developer.apple.com/help/app-store-connect/create-an-app-record/add-a-new-app

Has anyone run into Xcode Cloud becoming completely unreachable like this - and if so, how did you get it restored? I'm hoping either another developer who's been through this, or an Apple engineer who can look at the provisioning state or bump an internal Feedback, can point me somewhere. I'm a sole developer and I hold the Account Holder and Admin roles on this account. Xcode Cloud had been building this app successfully for over six months, most recently on 17 July 2026 - this is not a first-time setup or configuration issue. Then on 18 July it became completely unreachable, with no change on my side, and has stayed that way since. Symptoms (both reproduce every time, including in a fresh private/incognito browser session - so this is server-side, not local to Xcode or credentials): App Store Connect -> my app -> Xcode Cloud tab returns: "The page you're looking for does not exist, or you do not have permission to view it." (I am the Account Holder and Admin, so this is not a user-role or permission problem on my side - which points at server-side state, not my access level.) Starting a build in Xcode fails with: "An internal error occurred while authenticating. Try again later." No build is ever created. Everything the account controls is in order: membership active, all agreements and regulatory requirements complete, Paid Apps Agreement active, and the compute quota just reset normally to the full 100 hours. So billing/quota clearly still recognises the account - yet the Xcode Cloud entitlement is de-provisioned. It looks like a server-side provisioning state that was never restored. (For what it's worth: all agreements were completed after it broke, in an attempt to recover it, and made no difference - so this isn't an outstanding-agreement problem.) What I've already tried, so we can skip it: Standard first-line support steps: sign out/in of Xcode, relaunch, latest Xcode + macOS, bundle ID set, Archive checkbox enabled on the scheme. No change. Support is exhausted, so filing another ticket won't help: two Developer Support cycles confirmed they cannot re-provision the account or reach the team that can, and pointed to Feedback Assistant as the only route - which so far has had no response. A code-level technical support incident (DTS/TSI) doesn't apply either - this is account provisioning, not a code question. Feedback Assistant, FB23946235: first closed "unable to diagnose with current information." I reopened it with an exact traceable timestamp, the precise 404 URL (carrying my team UUID and app id), and full account state - no response, and the resolution never changed. I have since re-filed it as a fresh report. Ask: if you've hit this yourself and found a fix or an escalation path that actually worked, I'd love to hear it - that's probably my fastest route. And if any Apple engineer can look at the Xcode Cloud provisioning state for my account or nudge FB23946235 internally, I'd be hugely grateful. Team ID and app id are in the Feedback - happy to share whatever's needed via the report or DM. This has blocked all of my iOS CI for over three weeks.

I use Xcode Cloud with my Github repo to automatically trigger workloads any time I create a new PR or make changes to the PR. This has been working for a few years now but this week it stopped working from one day to the next with no explanation. If I trigger the workflow manually via Builds > Start Build > my PR build workflow, and selecting my Pull Request from the list. This means that Xcode Cloud has access to my Github account, it's not an auth issue or anything like that. The only thing that doesnt work is the auto detection of when a PR is created or updated.

所请求的app不可用或者不存在

My builds failed today with this error: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The thing is, I have Xcode Cloud configured to use the latest release. There is a separate configuration for "Latest beta or release", so why is it using the Xcode 16.2 Beta 3 build? This is clearly a beta. If you're going to give me an option to use the latest release, then it should do what it says.

delete

I am the account holder. I cannot log in to App Store Connect despite having paid the $99 and being given a membership id. https://developer.apple.com/help/app-store-connect/get-started/app-store-connect-workflow "Initially, only the Account Holder can sign in to App Store Connect using the Apple Account associated with their Apple Developer Program membership." Without access to App Store Connect, I am unable to create a team. Without a team, I am unable to use XCloud. https://developer.apple.com/help/app-store-connect/manage-your-team/overview-of-accounts-and-roles "You can manage users, add Sandbox testers, manage API keys, and manage access to the source code for Xcode Cloud in the Users and Access section of App Store Connect."

I am unable to connect Xcode Cloud to my GitHub organization repository despite being the organization owner. Error: CI.SCM.Error.RepositoryNotFound Xcode Version: 16.2 (or your version) Steps I have taken: Verified I am an Owner of the GitHub organization Uninstalled and reinstalled Xcode Cloud GitHub App multiple times Cleared all local Xcode caches and preferences Signed out of Apple ID on Mac and restarted Signed back in to Xcode only (not system level) Tried granting access again Attempted with multiple organization owner accounts Following API shows: 401 Unauthorized on https://appstoreconnect.apple.com/olympus/v1/providerSwitchRequests Additional context: GitHub App shows as successfully installed on organization Repository access set to "All repositories" Has anyone else encountered this or found a workaround? Thank you!

Hi, I am curious about why don't you provide an arm64 version of homebrew to your developers. To install arm64 homebrew in xcodecloud requires to compile packages from source. After 35 minutes still running ci_scripts/ci_post_clone.sh to install some packages: arm-brew install coreutils arm-brew install bash awk grep cat arm-brew install make arm-brew install gnu-tar gzip bzip2 xz arm-brew install automake autoconf m4 libtool arm-brew install llvm arm-brew install perl perl-build pod2man python3 meson ninja sqlite libtasn1 openssl libiconv gettext Further I need continues integration to build universal binaries and libraries. Maybe run the integration test suite, too. I think xcodecloud should provide arm64 and x86_64 versions of homebrew. Please consider this change.

I was previously able to test my app on Xcode 27 / iOS 27 by setting the Xcode Version to "Latest beta or release". I needed this to test PrivateCloudCompute on my apps in TestFlight. As of a few days ago this stopped working and only shows the stable 26 release, which removes PCC and my ability to test it. Am I doing something wrong? I didnt change any settings, I just noticed PCC wasnt working, checked the workflow and noticed that it no longer shows Xcode 27.

I've been getting intermittent failures on Xcode code compiling my app on multiple platforms because it fails to compile a metal shader. 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. Sometimes if I re-run it, it works fine. Then I'll run it again, and it will fail. If you tell me to file a feedback, please tell me what information would be useful and actionable, because this is all I have.

Hi, My full build with all dependencies takes approximately 2 hours plus about 1 hour to run integration tests. Sorry 120 minutes build timeout is too short. Is there a way to adjust build timeouts? by Joël

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?

I'm trying to build an Xcode Cloud workflow, but I keep getting this error. At first it just said I had to accept a license agreement, which I did, but it still didn't work after. I had recently added a new branch to the connected GitHub repository and committed to it so that I can have a beta branch separate from the main one. The only error that happens is when archiving. I am using Xcode 27 beta.

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.

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.

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

This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.