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

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.

I am seeing Xcode Cloud reuse and reassign a single ciProduct when onboarding multiple iOS app targets from one Xcode project. Each target has its own bundle ID, PBXNativeTarget, product reference, and shared scheme. Environment: Xcode 26.6 (17F113) macOS Tahoe 26.5.2 GitHub repository connected to Xcode Cloud Project: pilot-ios/Airtap.xcodeproj Targets / shared schemes: PocketPilot.ai DEV1 — ai.airtap.dev1 PocketPilot.ai DEV2 — ai.airtap.dev2 PocketPilot.ai DEV3 — ai.airtap.dev3 PocketPilot.ai DEV4 — ai.airtap.dev4 PocketPilot.ai QA1 — ai.airtap.qa1 PocketPilot.ai QA3 — ai.airtap.qa3 Every entry above is a separate PBXNativeTarget with a distinct productReference. Each shared scheme is stored under Airtap.xcodeproj/xcshareddata/xcschemes and builds its corresponding target. QA1 and QA3 were onboarded earlier and received independent Xcode Cloud products as expected. Reproduction: In Xcode, open Xcode Cloud Reports and choose Create Workflow. Select target PocketPilot.ai DEV1 and create an archive workflow using scheme PocketPilot.ai DEV1. DEV1 appears under the correct App Store Connect app. Create another workflow for target PocketPilot.ai DEV2 using scheme PocketPilot.ai DEV2. DEV1 disappears as a separate Xcode Cloud product. Both the DEV1 and DEV2 workflows now appear under the DEV2 App Store Connect app. The App Store Connect API confirms this is not only an Xcode UI or cache issue: Before DEV2 onboarding, ciProduct F048BF00-CECF-4926-84DB-D3474CB030A9 was related to bundle ID ai.airtap.dev1. After DEV2 onboarding, that same ciProduct ID became related to bundle ID ai.airtap.dev2. The product now contains both workflows: PocketPilot DEV1 Archive / scheme PocketPilot.ai DEV1 PocketPilot DEV2 Archive / scheme PocketPilot.ai DEV2 No build was started, and both workflows are currently disabled. Expected behavior: Because every target has a different bundle ID, Xcode should create a separate Xcode Cloud product for each target, as described in the Xcode Cloud onboarding documentation. Actual behavior: The newest onboarding changes the existing ciProduct-to-App Store Connect app relationship instead of creating a new ciProduct. This moves all earlier workflows to the newest app. The public App Store Connect API cannot repair this because it supports reading and deleting ciProducts, but not creating one; ciWorkflows can only be created under an existing ciProduct. I also encountered an Xcode crash while adding another product. The crash stack included XcodeCloudNavigableItemCoordinator.removeNavigableItem(for:) and IDENavigableItemCoordinator, which may be related to the product reassignment. I can provide the crash report in Feedback Assistant if needed. A recent forum thread reports the same high-level symptom: previously created workflows migrate to the newest app. In our case, the API relationship change above makes the backend reassignment directly observable. Is this a current Xcode Cloud onboarding/backend regression? Is there a supported workaround, or can Apple Support create or restore separate ciProducts for these bundle IDs?

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

When I use Xcode to create an Xcode Cloud workflow through Xcode > Integrate > Create Workflow for App A, and later create another workflow for App B, both workflows appear only under App B in App Store Connect, under App B > Xcode Cloud > Builds. I would expect the first workflow to remain associated with and visible only under App A, while the second workflow should be associated with and visible only under App B. This worked as expected previously, but the behavior appears to have changed recently, and it is now causing my builds to fail.

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

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 can't enable Xcode Cloud for my app. Integrate > Xcode Cloud > Create Workflow is greyed out in Xcode. Environment: macOS: 27 beta (paired with iOS 27 beta on device) Xcode: 27 beta (only version that opens on this macOS) Xcode 26.6 (stable) fails to launch with: "This version of Xcode is not supported by this version of macOS" I am the Account Holder on my team (confirmed in Users and Access) What I've tried: Signed out and back into Xcode with my Apple ID Confirmed Team is set correctly in Signing & Capabilities Restarted Xcode App Store Connect also rejects my build upload with: "This build uses a beta version of Xcode and can't be submitted. Be sure to use the latest Xcode or Xcode GM seed available in News and Updates." Is there a way to run an Xcode Cloud workflow with Xcode 26.6 as the build environment without having 26.6 installed locally? Or is Create Workflow expected to be disabled while on macOS beta?

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

I'm trying to start using Xcode Cloud from a project, but the only thing I get is the message saying "Failed to create workflow" with the actual error being "Could not find item. Domain: XcodeCloudKit.XcodeCloudCommandHandler.CommandHandlerError Code: 5". Initially, it did lead me to configuring permissions on GitHub. But it failed in the end probably because the git remote of the project was pointing to another organisation, that transferred the ownership to me. I switched remote to my org, but it didn't help. So, I revoked the permission and deleted Xcode Cloud app from my GitHub in hopes that the config process would start again. It does not. All I get is this senseless error. Is Xcode Cloud functionality functioning at all in Xcode beta 27 for anyone?

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 ?