Hello I gave access to a gitlab repository for my project. However, I had to move my project to another gitlab repository, and I can't seem to be able to grant access to this new gitlab repo... I had gitlab.XXXX.com and now have gitlab.YYYYY.com. But when I try to grant access, I get on the webpage of Xcode Cloud that tells me that it can't access to gitlab.XXXX.com

Hi. I'm using Xcode Version 13.3 (13E113). I have a project that builds a MacOS app successfully in the GUI and from the command line using xcodebuild. It builds a universal binary that targets x86_64 and Apple Silicon. When I try to build in Xcode Cloud I get four errors which all appear to be identical and which are: Run command: 'set -o pipefail && source /Volumes/Task/ci_build.env && source /Volumes/Task/ci_plan.env && xcodebuild -exportArchive -archivePath /tmp/e8493b09-68f3-4226-8f89-5c00de477670.xcarchive -exportPath /Volumes/workspace/appstoreexport -exportOptionsPlist /Volumes/workspace/ci/app-store-exportoptions.plist '-DVTPortalRequest.Endpoint=http://100.118.8.40:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/Task/logs/app-store-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 2>&1 | tee /Volumes/Task/logs/app-store-export-archive-logs/xcodebuild-export-archive.log' Run command: 'set -o pipefail && source /Volumes/Task/ci_build.env && source /Volumes/Task/ci_plan.env && xcodebuild -exportArchive -archivePath /tmp/e8493b09-68f3-4226-8f89-5c00de477670.xcarchive -exportPath /Volumes/workspace/appstoreexport -exportOptionsPlist /Volumes/workspace/ci/app-store-exportoptions.plist '-DVTPortalRequest.Endpoint=http://100.118.8.40:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/Task/logs/app-store-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 2>&1 | tee /Volumes/Task/logs/app-store-export-archive-logs/xcodebuild-export-archive.log' I am unclear as to what this command is trying to do or why its running four times. It reports Command exited with non-zero exit-code: 70. These commands appear in the build log under an item that says, Export archive for app-store distribution. Note that I don't intend to distribute the app via the App Store right now. In this case, I just want to use Xcode Cloud to run CI jobs for my app when code is checked in and make the builds available to me and other people at my company.

I can't use Xcode Cloud in the last days anymore. I've tried it in both Xcode 13.4.1 running on Monterey and Xcode 14 beta running on Ventura beta. All I get is a spinner with the message "Analysing Workspace" and after quite a while an error message saying "Could not load Xcode Cloud data". I've tried this on multiple projects on both apps/platforms. Anyone else having the same problem?

It seems I used the wrong Bitbucket account when setting up my project with Xcode Cloud. Now when I proceed with the "Grant Access" step, all I get is this error: Bitbucket Cloud installation was incomplete Repository was not found. Either the repository does not exist or you do not have permission to access it. Is there any way to reset this and start over?

Is there a way to execute code after the app has been uploaded successfully to Testflight? I am trying to post the patch notes of the update into Slack. I would be fine if there is a way to put the patch notes into the "What's New" section for the app in Testflight instead. The current Slack integration seems to show the Git title rather than the title/summary + the description. I would love to use either the last commit's description or a separate file in my repo to host all the changes.

Hi all, If I understand right Xcode Cloud run on real devices but does run on real macOS devices?For Xcode Cloud I need to have a github project done before I can use it?

Does Apple have Xcode Cloud sample code, or any sample code that contains tests?

I am unable to complete the Archive step for my iOS project. Looking at the logs, I see a number of messages that imply that Xcode Cloud is unable to fetch my dependencies for some reason. I have verified that I gave Xcode access to all my GitHub repositories, and it seems to be able to access my primary project repository without any problems. The type of logs I'm getting are as follows: Failed to clone repository git@github.com:myusername/MyRepositoryName.git:     Cloning into bare repository '/Volumes/workspace/DerivedData/SourcePackages/repositories/MyRepositoryName-b342b4d2'...     fatal: could not read Username for 'http://github.com': terminal prompts disabled One for each of my dependencies. Any thoughts?

All of my builds get stuck on Archive action - it keeps running forever (10+ hours where it took 30 minutes before for a clean build), and never finishes despite having all subtasks finished (green check). This started to happen on a workflow that has worked reliably for months, right after WWDC22 start - is there a problem with a new version of Xcode Cloud?

I'm just starting out with Xcode Cloud and trying to get a simple example running. I've got a basic 'Hello World' project with a couple of unit tests that I'm building for iPhone, iPad and Mac Catalyst. Running unit tests locally works fine on both iOS and Mac. My Xcode Cloud workflow has an action for iOS unit tests and Mac unit tests. The iOS tests run fine but the test bundle for Mac fails to load with this message: HelloWorldOCL (5739) encountered an error (Failed to load the test bundle. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult. (Underlying Error: The bundle “HelloWorldOCLTests” couldn’t be loaded. The bundle couldn’t be loaded. Try reinstalling the bundle. dlopen(/Volumes/workspace/TestProducts/Debug-maccatalyst/HelloWorldOCL.app/Contents/PlugIns/HelloWorldOCLTests.xctest/Contents/MacOS/HelloWorldOCLTests, 0x0109): tried: '/Volumes/workspace/TestProducts/Debug-maccatalyst/HelloWorldOCLTests' (no such file), '/System/iOSSupport/Volumes/workspace/TestProducts/Debug-maccatalyst/HelloWorldOCL.app/Contents/PlugIns/HelloWorldOCLTests.xctest/Contents/MacOS/HelloWorldOCLTests' (no such file), '/Volumes/workspace/TestProducts/Debug-maccatalyst/HelloWorldOCL.app/Contents/PlugIns/HelloWorldOCLTests.xctest/Contents/MacOS/HelloWorldOCLTests' (code signature in <9E48F794-E3BB-38B4-BFE5-3C5932331003> '/Volumes/workspace/TestProducts/Debug-maccatalyst/HelloWorldOCL.app/Contents/PlugIns/HelloWorldOCLTests.xctest/Contents/MacOS/HelloWorldOCLTests' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)), '/usr/lib/HelloWorldOCLTests' (no such file))) The project setup is pretty basic. Code signing is set to automatic with the team specified. It all works locally, so I'm not quite sure how to proceed. Any suggestions welcome. Thanks!

…and nothing more on the page. Not only on my account, but also on other teams I have access to. Is that expected? Will it be rolled out later for beta participants or is it just broken due to high demand?

not able to kick off any builds today getting error unable to connect to git repo. I have verified the git repo and its fine.

How to get Xcode Cloud?

Does Apple plan to introduce an XCode Cloud REST API in addition to its webhooks in the not too distant future?

I am trying to run macOS unit test on XCode Cloud, but failed with following message. It runs smoothly locally on my Mac. Tests macOS-Runner (29166) encountered an error (Failed to check for UI testing permission for the test runner process. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult. (Underlying Error: Unable to run UI Tests because Xcode Helper does not have permission to use Accessibility. To enable UI testing, go to the Security & Privacy pane in System Preferences, select the Privacy tab, then select Accessibility, and add Xcode Helper to the list of applications allowed to use Accessibility))

After building my app with Jenkins for 3 years without any problems, I'm now trying to build with Xcode Cloud and I'm getting the following error: ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.game-center I deleted the capability from the Xcode and the info.plist file, yet I'm still getting the error. Any ideas?

Hi there, We've been trying out Xcode Cloud for CI for a couple of months, and it has worked pretty well for the most part, but now we've stumbled on something we just can find the answer to, and I'm hoping for some help. We have a "PR checks" workflow that runs tests and analysis for pull-requests, and a "test and deploy" workflow that runs tests and submits uploads to TestFlight from the master branch. We use custom build scripts in all the right locations to perform additional work for our builds. The problem: Our ci_scripts/ci_post_xcodebuild.sh script cannot be found (and therefore does not execute) when running tests (test-without-building) as part of a test action, but bizarrely only on our "test and deploy" master-branch-workflow. However: The script it found just perfectly in the build-for-testing step of the exact same master-branch-workflow The script is also found perfectly when running test-without-building in our "PR checks" workflow According to the documentation I can find, the ci_scripts/ci_post_xcodebuild.sh should always be available for Test actions in the test-without-building step, regardless of branch. So I don't understand why it would be suddenly missing, and only some times. Here's a log from a fully-working "PR checks" workflow run: And here's an example from a "test and deploy" master-branch-run where the scripts are found in the "Build test"/build-for-testing step, but for some reason not in the "Run test"/test-without-building step: Any help would be appreciated :)

HI there, I just started using Xcode cloud. When building Xcode cloud, two archives are being generated: iOS and macOS. The macOS archive always errors out with: xcodebuild: error: Unable to find a destination matching the provided destination specifier: {generic:1, platform:macOS} I have no intention of my app running on macOS, but if I knew how to fix that, it might be kinda neat. But really, it's unnecessary, so how do I turn it off? Thanks, Kim