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.

After writing the code, when debugging on VisionPro, the program will encounter a blocking situation when running from Xcode to VisionPro. It will take a long time for the execution information to appear on the Xcode console

Hello, While setting up Xcode Cloud using Bitbucket, I encountered an issue with Source Control and providing access to the repository. The problem most likely stems from the fact that Bitbucket has updated its policy, and the use of app passwords is no longer available (at least for new ones). However, in Xcode → Settings → Source Control, the login flow still requires an app password, which makes it impossible to authenticate using the new API tokens. Attempting to authenticate via SSH also does not resolve the issue. After connecting to GitHub, I also tried to connect through the web version, but I'm getting the same message: "Bitbucket Cloud installation was incomplete." I received this same message when I first tried to connect through Xcode. This problem does not occur when connecting to GitHub. I would appreciate receiving feedback from the Apple team on this issue. System Info: Xcode: 16.2 (latest from App Store) macOS: Sequoia 15.1

Hello, My project is GitLab and to access it we need VPN. How to connect Xcode Cloud to that repo if VPN is required for read it? Any solution to this? Any help is appreciated

Error: Preparing build for App Store Connect failed No error logs in log view. Download the archive and try to submit to App Store: Detailed logs: 2025-12-17 07:26:00 +0000 [MT] Command line name "app-store" is deprecated. Use "app-store-connect" instead. 2025-12-17 07:26:00 +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)")) 2025-12-17 07:26:00 +0000 App Store Connect response failed with unknown failure for credential <DVTFoundation.DVTServicesSessionProviderCredential: 0x600002e099c0>; response (null); error (null). 2025-12-17 07:26:00 +0000 App Store Connect request for store configuration for credential <DVTFoundation.DVTServicesSessionProviderCredential: 0x600002e099c0>; configuration: (null); error DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy 2025-12-17 07:26:00 +0000 [MT] Failed to find an account with App Store Connect access for team <IDEProvisioningBasicTeam: 0x6000029c0240; teamID='984L9QX9X5', teamName='(null)'> 2025-12-17 07:26:00 +0000 [MT] Running step: IDEDistributionFetchAppRecordStep with <IDEDistributionContext: 0x7fa62b216680; archive(resolved)="<IDEArchive: 0x600000315ea0>", distributionTask(resolved)="2", distributionDestination(resolved)="1", distributionMethod(resolved)="<IDEDistributionMethodiOSAppStoreDistribution: 0x600002a1f560>", team(resolved)="<IDEProvisioningBasicTeam: 0x6000029c0240; teamID='984L9QX9X5', teamName='(null)'>">

Since Dec 18th, my Xcode Cloud builds (for multiple apps) have been failing with this error: Command line name "app-store" is deprecated. Use "app-store-connect" instead. I haven't made any changes to my system, signing, etc, and two separate apps started failing at the same time. No matter what I change on my Workflows (environment, new workflow from scratch, etc), nothing seems to fix it, which leads me to believe this is a bug with Xcode Cloud itself. I've logged FB21456291 already, but just wanted to post here to see if I'm missing something.

Hello Apple Developer Support Team, I am writing to request assistance with an issue preventing me from distributing my iOS app to the App Store. I am able to successfully build and archive my app in Xcode without errors. However, after archiving, Xcode only shows the option “Distribute Content” instead of “Distribute App”. Because of this, I am unable to upload the app to App Store Connect. App & Account Details • App Bundle Identifier: com.yesbuy.yesbuyapp • Team Name: Fathima Sayed Mohamed • Team ID: Z327MG963D • Xcode Version: 26.2 • macOS Version: macOS 15.6.1 Signing & Certificates • Signing Method: Automatically manage signing (enabled) • Signing Certificate (Release): Apple Distribution: Fathima Sayed Mohamed • Provisioning Profile: Xcode Managed / App Store Distribution • Archive Status: Build succeeded What I’ve Already Verified • The archive is created using Release configuration • Skip Install is set to No for the main app target (Runner) • The app target is selected correctly during Archive • A valid Apple Distribution certificate exists • The app is registered correctly in App Store Connect • App Groups and capabilities are configured correctly • Notification Service Extension is present and signed Despite all of this, Xcode still treats the archive as a Generic Xcode Archive and only allows Distribute Content, not Distribute App. I have attached screenshots showing: 1. Xcode Archives screen (showing “Distribute Content” only) 2. Signing & Capabilities for the app target 3. Certificates and provisioning profiles 4. Team ID and bundle identifier configuration Could you please review this issue and let me know: • Why the archive is not recognized as an App Store–distributable app • Whether there is any account, certificate, or configuration issue on Apple’s side • Any steps I should take to resolve this and successfully upload the app to App Store Connect Thank you very much for your time and support. I look forward to your guidance.

I am getting this issue, whenever I am trying to reconnect XcodeCloud in App Store as the XcodeCloud builds are blocked. Steps we followed Go to App Store Connect -> select app -> select Xcode Cloud -> select build 2 we are able to see error message with connect button Xcode Cloud is unable to connect to the repository “**********”. Reconnect the repository to resume builds. 3. Tapping on connect -> shows a popup with option to authorize in bitbucket -> taping on it, takes us to another window which redirects continuously and nothing happens Can anyone help me with this

We have been using Xcode Cloud Build to test an internal app. A new build is triggered automatically by a merge to main in github. Up until a few weeks ago everything was fine, we would get a notarize button and a download link. On 1/29/2026 the process started timing out at the finalizing step. The logs in the UI show no errors just a "cancelled" flag after 8-12 hours. Clicking the logs tab shows all green up until the step you would normally expect a "stapling". Any thoughts on were to look to triage this?

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.

Dear App Review Team, I hope you are well. I am writing to respectfully follow up on my recent submission (Dev ID: 1770951123), which has now been in “Waiting for Review” status for approximately 12+ days. Currently, four of my applications are in a similar state, including one update for an app that was previously approved without issue. Given my past experience, reviews have generally been completed within a reasonable timeframe. While I fully understand that review times may vary depending on workload, the extended duration in this case has raised some concern. I previously submitted an expedited review request and opened a support case (Case ID: 102832785901). However, I have not yet received any response regarding the status of the review or the case. To better understand the situation, I would sincerely appreciate clarification on the following points: Whether there are any issues or flags currently preventing the review process from proceeding Whether any additional information or documentation is required from my side Or whether the submission is simply pending assignment to a reviewer I completely understand that the App Review team may be experiencing a high volume of submissions. Nevertheless, given the duration and the number of affected apps, I would be very grateful if someone could kindly review my case and advise on the current status. Thank you very much for your time and assistance. I look forward to your response. Kind regards, Lovesoft

Hello, I was told from Developer engineers to post an Xcode issue on Feedback Assistant. It has been 6 weeks and I have yet to receive a single reply or acknowledgement on my feedback post. I would just like to at least get some sort of acknowledgement from Feedback Assistant that my post is being tracked or if a resolution is in work please. Here's the post: https://feedbackassistant.apple.com/feedback/21824703

Showing All Messages [!] Error installing FBSDKLoginKit [!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20260316-6574-ros9od/file.zip https://github.com/facebook/facebook-ios-sdk/releases/download/v18.0.2/FacebookSDK_Dynamic.xcframework.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.16.2 cocoapods-downloader/2.1' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 curl: (35) Recv failure: Connection reset by peer Command exited with non-zero exit-code: 1 Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.

My app targets iOS 12.0 and crashes immediately on launch when installed via TestFlight on an iPad running iOS 12.x. The same archive works perfectly when installed via Ad Hoc distribution or directly from Xcode. This is a regression — the exact same source code, compiled with the same Xcode version, was successfully distributed via TestFlight and the App Store last month (March 2026) without issues. No changes were made to the code, Xcode version, or signing configuration. Steps to reproduce: Archive an app with IPHONEOS_DEPLOYMENT_TARGET = 12.0 using Xcode 16.4 Upload to App Store Connect Install via TestFlight on an iPad running iOS 12.x App crashes immediately on launch (pre-main, no crash log generated) Expected: App launches normally (as it did last month) Actual: App is killed immediately, process exits with reason: (none) Console.app shows the process never transitions from xpcproxy to the actual binary — it dies within ~260ms of bootstrap, indicating a dyld or app thinning issue. Environment: Xcode: 16.4 Deployment target: iOS 12.0 ENABLE_BITCODE: NO Device: iOS 12.x Ad Hoc install: WORKS Xcode direct install: WORKS TestFlight install: CRASHES App Store install: CRASHES Anyone else seeing this?

It is a bit strange what Xcode Cloud has implemented on how they manage the Build Numbers https://developer.apple.com/documentation/xcode/setting-the-next-build-number-for-xcode-cloud-builds Intead of just looking at the project configuration as the source of truth, they run their own build number and totally ignore the project config value. Also, interesting that instead of solving it they have a "Set Build Number" menu in the settings which is a pain to manually manage everytime they got out of sync. Is there any way to turn this madness off and consider the project config as the source of truth?

Hi - I was recently added to Apple Developer Team, and I am trying to upload an App to our Team's App Store Connect account for TestFlight distribution. I am trying to use XCode Cloud to this all automatically, but it is currently giving me this error: "Invalid Bundle ID. Bundle ID "com.XXX.YYY" could not be automatically registered because it is not available. Update the bundle ID of your project and try again." I am not sure if this is related to the fact that when I try to associate my XCode Account (XCode -> Settings -> Accounts), I only see my (Personal Team) account even after removing that account and re-adding it. Additionally, when I go my App -> Targets -> Signing & Capabilities and I check / uncheck automatically manage signing. I only see my Personal Team account. When I try to download a Provisioning Profile, I see "No Valid Teams, Unable to Find Any Valid Teams." I need to keep the bundle ID of the project as is because it is associated with a Firebase backend. What should I try next? Thanks!

im traying to update my app, however, the add for review button is not shoing in the appstoreconnect, there is not error or anything indicating im missing some sort of metadata.

Title Can’t accept App Store Connect team invitation – link forces “Create Apple ID” and rejects my existing e-mail Problem I just received an “X has invited you to access App Store Connect” e-mail. When I click Accept invitation, the browser opens the Apple ID page but it shows the “Create your Apple ID” form instead of a sign-in screen. If I enter my normal address, the form shows the red error: This email address is not available. Please choose another. Context I already have an Apple ID on that exact e-mail address. I was a member of a different App Store Connect team until this morning; I left that team before clicking the new invitation. Question How can I accept the invitation with my existing Apple ID instead of being forced to create a new one ?