Xcode 26 RC is not available on Xcode Cloud. This is a serious blocker affecting developers trying to be on App Store on day 1 of the OS 26 release. Is there an estimate when this can be in place?

So my xcode cloud build have been stuck for 12 hours, is there something wrong with me or the service isnt working rn?

Hi I have an developer app tied that is the account owner for our ABM and also for our Apple Developer account. When i go to the developer app and try to purchase additional hours it doesnt let me "Apple account cant be used to make purchases" And i am the account holder for both. The email tied to it is an "username/@/domain.appleid.com". Any help appreciated

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.

Hi We have a project with one app, where we have multiple schemes to create either a staging or release version of the app. We change the bundle identifier of the app so it's a separate app in app store connect. One staging app and one release app. We are trying to integrate Xcode cloud workflows, however, there's only one app visible in the Xcode cloud tab and when we create a workflow it gets automatically assigned to the staging app in app store connect. We cannot create the workflow under the release app in app store connect, as the manage workflows button is not visible until you've created the first workflow for an app in xcode. How can we create a workflow and force it to be associated with the release app in app store connect?

Hi everyone, After disabling Xcode Cloud for my team, I tried to enable it again for my product. However, I keep seeing this message when reconnecting to my source control: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been about a week since I disabled it, but I still can’t re-enable Xcode Cloud. I’ve tried reconnecting through GitHub and Bitbucket, and both show the same message. Could anyone share: How long does this “processing” phase usually take? Is there a way to check or request reactivation manually? Team type: Organization Region: Japan Thank you in advance for any suggestions or similar experiences!

When running an Xcode Cloud workflow pinned to Xcode 26.1, macOS 26.1 and using a Test Destination for iPhone 15 Pro and iOS 26.1, the following error appears in the xcodebuild-build-for-testing.log: 2025-11-13T19:08:31.855137440Z xcodebuild: error: Unable to find a destination matching the provided destination specifier: 2025-11-13T19:08:31.855318998Z { platform:iOS Simulator, id:704F84C8-025F-4F70-B2D9-FF19B7DC098F } 2025-11-13T19:08:31.855362640Z 2025-11-13T19:08:31.855370957Z Ineligible destinations for the "Inbound" scheme: 2025-11-13T19:08:31.855381964Z { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device, error:iOS 26.1 is not installed. Please download and install the platform from Xcode > Settings > Components. } This can be fixed if ci_pre_xcodebuild.sh is updated with the following: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '{print $2}' | cut -d. -f1) if [ "$XCODE_VERSION" -ge 26 ]; then if xcodebuild -downloadPlatform iOS >/dev/null 2>&1; then echo "iOS platform is installed" else echo "iOS platform is not installed. Failing the build." exit 1 fi fi Changing the workflow to use "Latest Release" of Xcode (26.1), macOS (26.1) and the Latest Test Destination iOS (26.1) version provided also does not work.

Hi all... The app I'm building is not really a beginner level test app, it's intended to be published so I want everything to be done properly while I'm both learning and building the app. I'm new to swift ecosystem but well experienced with python and JS ecosystems. These two models are causing my app to crash @Model final class CustomerModel { var id: String = UUID().uuidString var name: String = "" var email: String = "" var phone: String = "" var address: String = "" var city: String = "" var postalCode: String = "" var country: String = "" @Relationship(deleteRule: .nullify) var orders: [OrderModel]? @Relationship(deleteRule: .nullify) var invoices: [InvoiceModel]? init() {} } @Model final class OrderModel { var id: String = UUID().uuidString var total: Double = 0 var status: String = "processing" var tracking_id: String = "" var order_date: Date = Date.now var updated: Date = Date.now var delivery_date: Date? var active: Bool = true var createdAt: Date = Date.now var items: [OrderItem]? @Relationship(deleteRule: .nullify) var invoice: InvoiceModel? @Relationship(deleteRule: .nullify) var customer: CustomerModel? init() {} } both referenced in this model: @Model final class InvoiceModel{ var id: String = UUID().uuidString var status: String = "Pending" var comment: String = "" var dueDate: Date = Date.now var createdAt: Date = Date.now var updated: Date = Date.now var amount: Double = 0.0 var paymentTerms: String = "Once" var paymentMethod: String = "" var paymentDates: [Date] = [] var numOfPayments: Int = 1 @Relationship(deleteRule: .nullify, inverse: \OrderModel.invoice) var order: OrderModel? @Relationship(deleteRule: .nullify) var customer: CustomerModel? init() {} } This is my modelContainer in my index structure: @main struct Aje: App { var appContainer: ModelContainer = { let schema = Schema([UserModel.self, TaskModel.self, SubtaskModel.self, InventoryModel.self, SupplierModel.self]) let config = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false, allowsSave: true, groupContainer: .automatic, cloudKitDatabase: .automatic) do{ return try ModelContainer(for: schema, configurations: [config]) }catch{ fatalError("An error has occured: \(error)") } }() var body: some Scene { WindowGroup { ContentView() } .modelContainer(appContainer) } } This works fine but the below after adding the problematic models crashes the app unless CloudKit is disabled @main struct Aje: App { var appContainer: ModelContainer = { let schema = Schema([UserModel.self, TaskModel.self, SubtaskModel.self, InventoryModel.self, SupplierModel.self, InvoiceModel.self, OrderModel.self, CustomerModel.self]) let config = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false, allowsSave: true, groupContainer: .automatic, cloudKitDatabase: .automatic) do{ return try ModelContainer(for: schema, configurations: [config]) }catch{ fatalError("An error has occured: \(error)") } }() var body: some Scene { WindowGroup { ContentView() } .modelContainer(appContainer) } }

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)'>">

I'm using Xcode cloud to create testflight builds, and I noticed that a few weeks ago these builds no longer contain any "What to Test" info. We include a TestFlight/WhatToTest.de-DE.txt file in our repo, and that file seems to be picked up correctly, at least the logs say Saving “What to test” notes Found notes for de-DE Any ideas of what I should be looking into or change?

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.

Just learnt today that personal development teams do not support the Push Notifications and iCloud capabilities, is there any workaround besides pay another 99 for an enterprise development account? Thanks in advance.

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally. So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly? You can find a detailed instruction how server is launched on a github page I provided.

Hi everyone, We're developing a mobile app with Flutter and I linked my GitHub with XCode Cloud. This is the first time we're using XCode Cloud and we are struggling with the build, they fail every time. A little context, we started by adding the ci_post_clone.sh script, then adding a few files in the versioning, etc... Now it looks like the build is going through be we are facing issues with the part: Scan dependencies of GeneratedPluginRegistrant.m It's throwing an error: Module 'cloud_firestore' not found, even though the module is installed before by performing a pod install. It's building locally on both Flutter with IntelliJ and XCode, we tried several times to flutter clean or pod deintegrate but nothing works! Any clue? Thanks,

Since yesterday, Xcode cloud no longer seems to be successful in building our workflows. We're relying on Xcode Cloud for our CI, and the downtime is hindering us greatly. I've seen there is an issue on https://developer.apple.com/system-status/. Any indication of progress on this issue would be appreciated.

There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.