I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 Command exited with non-zero exit-code: 70 The same pattern repeats for ad-hoc and app-store distribution exports. What I've verified: The build itself compiles successfully (all modules compile, command executed successfully) No code changes were made that would affect signing The workflow is configured with automatic signing managed by Xcode Cloud Post-action is set to TestFlight External Testing Additional constraint — Remote Mac: I'm building on a Remote Mac, which adds complexity to code signing and keychain access. The Remote Mac environment has known limitations with certificate and provisioning profile management compared to a local Mac. This may be a contributing factor to the export failures. This appears to be an issue with how Xcode Cloud is handling the Apple Distribution and Apple Development signing certificates during the export phase, not a build compilation issue. Has anyone encountered this recently, or is there a known issue with Xcode Cloud's managed signing on Remote Mac environments? Any guidance on resolving exit code 70 during the export step would be greatly appreciated.

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?

Client error - operationID: onboardTarget, operationInput: Input(path: XcodeCloudAPI.Operations.onboardTarget.Input.Path(teamId: ""), query: XcodeCloudAPI.Operations.onboardTarget.Input.Query(), headers: XcodeCloudAPI.Operations.onboardTarget.Input.Headers(), cookies: XcodeCloudAPI.Operations.onboardTarget.Input.Cookies(), body: XcodeCloudAPI.Operations.onboardTarget.Input.Body.json(XcodeCloudAPI.Components.Schemas.TargetOnboardingRequest(projectName: "Runner", targetName: "Runner", targetType: app, repoHandle: XcodeCloudAPI.Components.Schemas.RepoHandle(host: Optional("bitbucket.org"), provider: bitbucket, repoId: ""), deviceFamilies: Optional([iPhone, iPad]), deploymentTarget: Optional("15.0"), productCreationEntryPoint: xcode_product_menu))), request: path: /teams/onboard-target, query: , method: HTTPMethod(value: OpenAPIRuntime.HTTPMethod.(unknown context at $14c94d79c).OpenAPIHTTPMethod.POST), header fields: [accept: application/json, content-type: application/json; charset=utf-8], body (prefix): { "deployment_target" : "15.0", "device_families" : [ "iPhone", "iPad" ], "product_creation_entry_point" : "xcode_product_menu", "project_name" : "Runner", "repo_handle" : { "host" : "bitbucket.org", "provider" : "bitbucket", , baseURL: https://appstoreconnect.apple.com/ci/api, response: , underlying error: The operation couldn’t be completed. (XcodeCloudCombineAPI.NetworkResponseError error 1.) Domain: OpenAPIRuntime.ClientError Code: 1 System Information: macOS Version 27.0 (Build 26A428)

Hello Apple Developer Community, I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response. Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403 I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository. What I have already checked I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection. Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket. Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp. They indicated that the failure could potentially involve: Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect? Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions? If an Apple engineer is able to review the server-side logs, could the following details help identify the failure? Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403 Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs. Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated. Thank you.

Hello Apple Developer Community, I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response. Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403 I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository. What I have already checked I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection. Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket. Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp. They indicated that the failure could potentially involve: Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect? Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions? If an Apple engineer is able to review the server-side logs, could the following details help identify the failure? Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403 Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs. Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated. Thank you.

I'm gettign webhook error with 403

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

System: Xcode 27.0 GitHub Xcode Cloud Worked this morning (green build on a PR), then the repo mirror froze ~15:00 and by 19:00 Xcode showed: "An internal error occurred while authenticating" and the Xcode Cloud tab vanished from App Store Connect. Root cause via the API (team key, not Xcode's login): GET /v1/ciProducts?include=primaryRepositories → 500 UNEXPECTED_ERROR every time, while /ciProducts/{id}/primaryRepositories alone is 200. Xcode and the web both load with that include. The "authenticating" text is misleading; clearing ~/Library/Developer/Xcode/UserData/XcodeCloud brought the tab back. Tried a reset: DELETE /v1/ciProducts/{id} 204 GET /v1/ciProducts/{id} 404 GET /v1/ciProducts 200, still lists the deleted id (45+ min) DELETE /v1/ciProducts/{id} 404 now That orphan makes Xcode → Create Workflow fail ("Failed to create workflow. An unexpected error occurred"). Uninstalling the Xcode Cloud GitHub App didn't remove scmProviders/scmRepositories either. POST /ciProducts, PATCH primaryRepositories, DELETE scm* all 403. Has anyone seen an orphaned ciProducts entry clear on its own, or found a purge path? Filed with DTS + Feedback Assistant. Trace ids: d4b1165164dfc962dae834b672ada029, fbf240e08a78733b84d4d9b83a707baf.

Xcode 27 RC is not available on Xcode Cloud. Is there an estimate when this will be updated?

While validating Xcode Cloud with a self-managed GitLab instance, I found what appears to be an OAuth scope issue affecting private repositories. Apple’s documentation says to configure the GitLab OAuth application with: api, read_repository, read_user However, the actual /oauth/authorize URL generated by Xcode Cloud requests only: scope=api+read_user With a private GitLab repository, OAuth completes successfully and Xcode Cloud can call: GET /api/v4/user → 200 GET /api/v4/projects/:project → 200 But repository setup fails with: Repository was not found. Either the repository does not exist or you do not have permission to access it. The GitLab user had Maintainer-or-higher access. I reproduced this from a clean Xcode Cloud setup. As a control test, I repeated the exact same flow but manually changed the OAuth authorization request to: scope=api+read_user+read_repository GitLab then explicitly requested read-only access to private repositories over Git HTTP. After authorization, the same private repository connected successfully to Xcode Cloud, and a build could be queued normally. A public repository works without read_repository, which can hide the issue. So the reproducible difference was: Private repo + Apple-generated api read_user → fails Private repo + api read_user read_repository → succeeds This also appears inconsistent with Apple’s own self-managed GitLab setup documentation, which instructs users to enable read_repository. I’m sharing this mainly for others who may run into the same issue with private repositories.

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?

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.

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

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.