I struggling in getting Xcode Cloud to work with a stand alone watch app. This app has the following three targets and each bundle identifier is set up in the Identifiers section of the developer portal. iphone container target called Unleashed abc.xyz.Unleashed watch target called Unleashed Watch App abc.xyz.Unleashed.watchkitapp watch target called Unleashed WidgetExtension abc.xyz.Unleashed.watchkitapp.Unleashed-Widget I have a App Store provisioning set up for abc.xyz.Unleashed.watchkitapp The app runs fine in the watch simulator, but fails with the following when I do an Xcode Cloud build Export archive for ad-hoc distribution Export archive for development distribution Export archive for app-store distribution When I expand each one of these errors it reports: Command exited with non-zero exit-code: 70 I also tried archiving the project in Xcode then selected the Archive but it won't let me validate because that button is disabled. Very confused I have successfully used Xcode Cloud for a phone app but am having a problem with this watch app that has a widget

The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I have Admin role but whenever I select the tab "Xcode Cloud" on any app, the page is not loaded. I am developer from Russia, its banned for russian users??? Please help, i cant update app

Can anyone help me resolve this lookup issue? This has been breaking builds for months. We make no changes and after a couple hours it works. It seems like Apple resolvers are getting a failure and then negatively caching the failure. Immediate subsequent runs extend the failure duration this is one of our installs from a pod install installing onnxruntime-c (1.21.0) [!] Error installing onnxruntime-c [!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20250730-29606-1v7ovh/file.zip https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.21.0.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 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: download.onnxruntime.ai

We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?

We just changed the repository from Bitbucket > Github. While all connected successfully, none of the branches are appearing. I understand usually it takes time (cache etc) but its been a good few hours. Also tried to remove the integration and re-setup but to no avail.

I am experiencing an issue where Xcode Cloud is not available in my Apple Developer Program account on App Store Connect. Despite having an active developer membership, I cannot access or enable Xcode Cloud for my apps. Could you please assist me in understanding why this feature is not available for my account and what steps I need to take to enable it?

We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?

We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?

Hello, We are building a web extension that is running on all browsers. For Safari, i have used the "XCode Cloud Safari Extension Packager" tool. We have no Mac or anything to work with. For the first upload, there was no problem, and the app is currently published on Safari. Recently, we did on update on this web extension. So i thought i'd reuse the "XCode Cloud Safari Extension Packager" to upload my new version of the web extension. But there is always the following error for each build : Invalid Pre-Release Train. The train version '1.0' is closed for new build submissions This bundle is invalid. The value for key CFBundleShortVersionString [1.0] in the Info.plist file must contain a higher version than that of the previously approved version [1.0]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring Of course, the web extension manifest.json version is set to something else than "1.0". And i have created a new app version from the "Distrubution" pane in AppStoreConnect. But nothing helped. So my questions are the following : How do i set the version of the Safari Web Extension from AppStoreConnect when uploading a new ZIP ? How do Safari Extension Packager determine the version of the app if it is not from the manifest.json version ? Is it a bug from Safari Extension Packager or is there something i am missing ?

Hi everyone, we're experiencing problems with our unit test builds on Xcode cloud. Without having changed anything in our build configuration, we're getting failed builds (that also take a loooong time) withour any of the build / test steps showing any sign of failures. Maybe related: the "Save artifacts" step of the build appears to have taken almost an hour, but its individual sub-steps only took seconds. Is anyone else having those problems as well? -Gereon

I've noticed that when using the Test action in an Xcode Cloud workflow, the xcodebuild command includes COMPILER_INDEX_STORE_ENABLE=NO while performing build-for-testing. This disables the index store, which is required by tools like Periphery to analyze unused code. Without indexing, Periphery triggers a fresh build internally, resulting in a significant increase in CI build time. Is there any way to enable indexing (COMPILER_INDEX_STORE_ENABLE=YES) on Xcode Cloud? Or alternatively, is there a recommended workaround to generate and access the index store? Any help is appreciated.

Dear all, For an important client, we are currently experiencing issues related to performance IOS build using Xcode Cloud. More in detail, their build process is taking approximately 30 minutes to complete at the moment, whereas the same build executed locally on a Mac machine takes around 7 minutes. This significant difference in build times is causing concerns and slowing down the development work. We would appreciate your support in identifying possible causes and exploring different ways to improve the actual situation (ex if it is possible to increase the Cloud machine calculation power). Could you please advise us on how we might proceed to analyze and potentially optimize the build times on Xcode Cloud? What kind of processors are used? Any guidance, best practices, or diagnostic steps you can suggest would be greatly appreciated. Looking forward to your support.

Since first beta of iOS 26 I've created a workflow where I can deploy to TestFlight the builds compiled using the iOS 26 SDK, and it has worked fine until yesterday when I started receiving 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. I haven't changed anything in the workflow so I suspect it's a bug on Apple side? Or am I missing something? It is set to use "Latest Beta or Release" for both Xcode and macOS, archive and deploy to TestFlight Internal Testing. Thank you!

I'm setting up a first workflow in Xcode Cloud and when I go through the flow and reach the 'Grant Access to your source code' pane, my projects repo is listed as primary and has a green checkmark next to it, but one of my SPM dependencies does not. When I press the 'Grant Access' it launches AppStoreConnect which complains the repo can't be found or I don't have the correct admin permissions. I'm using BitBucket Cloud and both repos are mine and I am the admin for both. Xcode itself will build the dependency locally correctly. I did see that the dependent SPM package needs a Package.resolved checked in, which I've now done, but I can still no longer get past the Grant Access step. When I try to add myself as admin to the dependent repo, BitBucket says I can't be added because I'm already an admin. This is the same for the projects primary repo as well. But Xcode still thinks I only have read access. How do I get passed this? Xcode isn't even telling me what repo is troublesome: { "category" : "xcode-cloud-data", "column" : "23", "subsystem" : "com.apple.dt.XcodeCloudKit", "details" : "Error alert: You must have Admin or Write access to your repository. Your current permission level is read.: ModelErrorResponseError(error: XcodeCloudAPI.Components.Schemas.ErrorResponse(message: \"You must have Admin or Write access to your repository. Your current permission level is read.\", errorKey: nil, helpUrl: nil, details: [], body: nil, actions: []), httpStatus: XcodeCloudCombineAPI.LegacyHttpStatus.badRequest, traceId: Optional(\"ee71bf64b8cf2c27\"), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/69a6de89-4b61-47e3-e053-5b8c7c11a4d1\/products-v2\/A80C7CA9-25F0-4DCA-B7CC-D789A5022B88))\nError Description: Optional(\"You must have Admin or Write access to your repository. Your current permission level is read.\")\nRecovery Suggestion: nil\nHelp Anchor: nil", "createdAt" : "2025-06-28T18:49:15Z", "level" : "info", "filename" : "Logger+Additions.swift", "funcName" : "logError(_:)", "line" : "36" },

I'm getting this error, don't really understand why... Showing All Errors Only Build Archive Export archive for ad-hoc distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for development distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for app-store distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Activity Log Complete 6/26/25, 10:06 PM 0.4 seconds

Hello, When archiving a binary with Xcode, I've always kept my archives in the Organizer so I can symbolicate crash logs using the dSYM files. I've been thinking about moving to Xcode Cloud for archiving. Will crash logs still be symbolicated and readable in the Xcode Organizer? Thank you, Axel

Am I doing something wrong? FB18269317

Trying to submit a build to TF from Xcode 26 via Xcode Cloud (both for iOS and macOS). The operation fails with this message: Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG for the 'Any Appearance' image well in the asset catalog of apps built for iOS or iPadOS. Without this icon, apps can't be submitted for review. For details, visit: https://developer.apple.com/documentation/xcode/configuring-your-app-icon. If you’ve added an icon made with Icon Composer, visit https://developer.apple.com/app-store-connect/release-notes/ for details about known issues. I thought it's because Icon Composer icons may not be supported yet, but then that last sentence is confusing me. Does this mean that TF just won't support Xcode 26 uploads yet, or does it accept them and I need to provide legacy icons for my build?

When building xcode project of an application with login item included/embedded (another target), locally it works without problems. But when building on xcode cloud, we are getting the error: ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “XXX.***.***” value for the com.apple.application-identifier key in “Path_to_login_Item” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID. If there are no capabilities added to the login item's target (only com.apple.security.inherit and App Sandbox), the project builds without errors. But our login item needs to access a database in app group container and sync its data with iCloud, so after adding iCloud and App Group entitlements, building on xcode cloud fails with the error written above. Locally it builds and runs without problems. So, what should be done to fix this issue when building on xcode cloud?

I have an XCode Cloud CI/CD process that's been in place for over a year now, hooked up to the project's GitLab repository. Yesterday it lost connection to the repo, and I can't get it to reconnect. Here's the error I see when I click on the "reconnect" button: The repo still exists, obviously, and I still have maintainer access. I did notice that my private key that I use to connect XCode to GitLab had expired, so I created a new one, but that didn't resolve the issue. Another thing I noticed is that when I try to look at my builds in the console, it tells me to link my gitlab account with my Apple account: But when I click the Link Accounts button, nothing happens. Is there a different way to link the accounts? Is it possible that's what the issue is?