I've done the first step for connecting the Xcode cloud with GitLab, I've followed the instructions available on this link https://developer.apple.com/documentation/xcode/connecting-xcode-cloud-to-a-self-managed-gitlab-instance But I accidentally deleted the app created on GitLab ( step 8 on link above), then I can't restart the process in Xcode Cloud. Let me show the problem better... Every time that I clink on button "Grant Access" in Xcode tool, I'm redirect to this site: When I click on blue button, it happens on GitLab settings: Because I deleted the settings. Then, I need to go back to step 1 of 2 and set up again. How can I restart the process ?

Hi folks! I'm looking to see if anyone has had any luck adding their own private Cocoapods as Additional Repositories with granted access in Xcode Cloud? My understanding was that Xcode Cloud would be able to pick up on these additional requirements, and to an extent it has been able to capture the top level private Cocoapod repository specified has a source in my Podfile. However when it comes to the private Cococapods specified as dependencies, no dice. I have ensured that the private Cocoapods are in the same repo ecosystem as detailed by the documentation. Any insight anyone might have on the subject would be greatly appreciated!

We suddenly started seeing all our builds failing with the error: (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal abrt before starting test execution. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult)) We think this is something on Xcode Cloud’s end. It started happening on all builds. We tested on commits that had previously worked and got the same errors as we see now. Anyone else seeing this?

XcodeCloud builds are failing for the specific version v0.71.0 of react-native. When it was on v0.71.4. It was working seamlessly. I am using Xcode v14.2 on macos Ventura I am having the following error in the Xcode cloud logs. No such file or directory @ rb_sysopen - ../node_modules/react-native/package.json /Volumes/workspace/repository/node_modules/react-native/scripts/react_native_pods.rb:212:in `read' /Volumes/workspace/repository/node_modules/react-native/scripts/react_native_pods.rb:212:in `react_native_post_install'

In the "Resolve package dependencies" step I see this error occur: Scheme <scheme-name> is not currently configured for the build action. I cannot reproduce locally. When I run the command: xcodebuild -resolvePackageDependencies it finishes fine. I'm on Xcode 13.4.1 and MacOS 12.4.1 Other things I've tried: Verified scheme is in the workspace (not the project) Deleted all schemes and auto created schemes again Recreating the build action in the scheme Enabled all actions in the scheme

We are trying to get UI Tests working with Xcode Cloud. They run fine locally on the developer's machine, but they are failing when run on Xcode Cloud. We use Wiremock to mock the api calls, and this seems to be failing on Xcode Cloud as I see logs stating the server isn't found. I tried 2 approaches to run wiremock during the ui tests: Adding a Pre-action to the "Test" action of the UI Test Scheme to launch wiremock (this is what we use in local builds): #!/bin/sh exec > /tmp/preaction-log.txt 2>&1 if [[ -n $CI_XCODE_CLOUD ]]; then java -jar ./wiremock/wiremock-current.jar --port 8080 --https-port 8081 --verbose & else java -jar $SRCROOT/ci_scripts/wiremock/wiremock-current.jar --port 8080 --https-port 8081 --verbose & fi Launching wiremock in a custom xcode cloud script: ci_pre_xcodebuild. I know it is getting called because other items in that script executes. #!/bin/sh if [ $CI_XCODEBUILD_ACTION = 'test-without-building' ] then java -jar ./wiremock/wiremock-current.jar --port 8080 --https-port 8081 --verbose & fi Note that wiremock is in the ci_scripts directory which I understand should be accessible during testing. Any ideas how to run wiremock so it is accessible during ui testing? I hope I'm just missing something obvious here.

Hello, I've recently encountered a persistent warning related to Xcode Cloud in my Xcode project. The project was previously experimented with Xcode Cloud but not now. However, the warnings associated with it are still lingering in my project. Here's what I've attempted so far to rectify the situation: Removed Xcode Cloud Workflows: I navigated to the Product menu, selected Workflow, and ensured no remaining Xcode Cloud workflows were present. Remove from Source Control: I checked the Source Control navigator in Xcode for any leftover branches or configurations related to Xcode Cloud. Checked Project Settings: I went through my project settings in Xcode, looking for any remnants of Xcode Cloud configurations. Reviewed Xcode Preferences: I went into Xcode > Preferences > Accounts to verify there were no unexpected configurations linked to Xcode Cloud under my Apple ID. Checked for .xcscheme files: In my project directory, I inspected .xcodeproj and .xcworkspace package contents, especially within the xcshareddata/xcschemes directory, to ensure no Xcode Cloud-related schemes were left. Cleared Derived Data: As a last resort, I cleared the derived data associated with my project. Despite this, the warning persists. Has anyone else encountered such an issue? I'd appreciate any insights or solutions to permanently remove this warning. I believe the option to completely disconnect a project from Xcode Cloud should be more straightforward if it's indeed connected in some residual way. Thank you.

I'm new to Xcode cloud and I am having trouble granting my GitHub repository access to Xcode cloud on my corresponding iOS app project, and I discovered that the username specified in the grant access window is listed my old GitHub username. Therefore, when trying to grant access to the corresponding source code, it gives me an error. I already unlinked and relinked my GitHub account to Xcode and it doesn't resolve. How can I relink my GitHub account so that on Xcode it will show as my current GitHub username? Also my repository is private. Does it only work when it's public?

I have an Xcode project under git version control (github). I recently had changed the github user name. Xcode detects the name change and shows it correctly under Settings/accounts. Push and pull still work as expected. When I tried to configure Xcode Cloud I got an error message similar to '...Xcode Cloud could not connect with your source control provider...' during initial setup procedure. [1] The solution for me has been to edit the git config file, updating the URL for [remote "origin"] to the new path reflecting the new git user name. I would have expected that Xcode would have updated this config file when recognising the github user name change. [1] A exact German language error has been: "Die Verbindung von Xcode Cloud mit Ihrem Quellcodeverwaltungsanbieter konnte nicht erstellt werden. Versuchen Sie den Einrichtungsablauf erneut, um Xcode Cloud Zugriff auf Ihren Quellcode zu gewähren. Weiter in Xcode"

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 encountered this error 2023-01-24T22:14:41.500565325Z Installing ri documentation for cocoapods-catalyst-support-0.2.1 2023-01-24T22:14:41.500827390Z Done installing documentation for colored2, concurrent-ruby, i18n, tzinfo, zeitwerk, activesupport, nap, fuzzy_match, httpclient, algoliasearch, ffi, ethon, typhoeus, netrc, public_suffix, addressable, cocoapods-core, claide, cocoapods-deintegrate, cocoapods-downloader, cocoapods-plugins, cocoapods-search, cocoapods-trunk, cocoapods-try, molinillo, atomos, nanaimo, rexml, xcodeproj, escape, fourflusher, gh_inspector, ruby-macho, cocoapods, cocoapods-catalyst-support after 50 seconds 2023-01-24T22:14:41.500997230Z 35 gems installed 2023-01-24T22:14:42.023353910Z [in /Volumes/workspace/repository] 2023-01-24T22:14:42.023798292Z 2023-01-24T22:14:42.024448317Z [!] Invalid `Podfile` file: cannot load such file -- cocoapods-catalyst-support. 2023-01-24T22:14:42.024714192Z 2023-01-24T22:14:42.024976712Z # from /Volumes/workspace/repository/Podfile:1 2023-01-24T22:14:42.025200239Z # ------------------------------------------- 2023-01-24T22:14:42.025463448Z > require 'cocoapods-catalyst-support' 2023-01-24T22:14:42.025663811Z # 2023-01-24T22:14:42.025900158Z # ------------------------------------------- from my post-clone script, which is #!/bin/sh # ci_post_clone.sh export GEM_HOME="$HOME/.gem" gem install bundler brew install cocoapods gem install cocoapods-catalyst-support # Install dependencies managed with CocoaPods. pod install

I got the app building and running in simulator and in my iPhone without problems. I use the KingFisher framework and i can see it under Project -> Package Dependancies with Version Rules 7.0.0 - Next Major and Location its GitHub repo. After trying to build in XCode Cloud in order to see the app in the App Store Connect (and ultimately prepare it for TestFlight) I got : a resolved file is required when automatic dependency resolution is disabled and should be placed at /Volumes/workspace/repository/Explore Mars.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved. Running resolver because the following dependencies were added: 'kingfisher' (https://github.com/onevcat/Kingfisher.git)fatalError This Error appears twice under 'All Issues', in Configuration Issues and in Swift Package Dependancies. I have tried clean, rebuild, delete and re-install the KingFisher, ask ChatGPT - nothing works. Also worth noting that I checked in Finder and I dont have folder 'swiftpm' in the 'xcshareddata' neither ofcourse 'Package.resolved' (I also tried to mkdir swiftpm but I have no idea what the Package.resolved should include. PLS HELP :)

Over the past few months in Xcode Cloud I've have Environment Variables that have had the prefix "TEST_RUNNER_". In the Apple Documentation it was mentioned that this was correct - https://developer.apple.com/videos/play/wwdc2022/110361/. Environment variables can provide parameters to both the XCTest test runner app on your device and the test host running xcodebuild. In Xcode Cloud, environment variables prefixed with TEST_RUNNER_ get passed into the XCTest test runner. This prefix will be stripped prior to the variable being made available to your code. So, for example, a variable in your test code named BASE_URL would be passed in as the environment variable named TEST_RUNNER_BASE_URL. Test plans require the same format as test code. Namely, we do not add the TEST_RUNNER_ prefix. As of last week I'm now getting an error when I add "TEST_RUNNER_" in front of my environment variable in Xcode Cloud. Is this a bug on Apple's end or is there a way for me to fix this?

Currently, I'm developing the new SDK and unable to upload to test flight for external testing purposes, is this even possible? Or would anyone who wants to test my app need to manually do it from their own Xcode 14 beta.

I'm encountering an authorization issue while attempting to build my app project using Xcode Cloud. My project includes a Git submodule hosted on our self-hosted GitLab instance (the main repository is on the same instance). During the build process, I receive the following error message: "An additional repository requires authorization." The logs are are showing that there was an attempt to clone the submodule via ssh. When I created the workflow, It managed to establish the connection between App Store Connect and the Gitlab instance. For both the main repository and the submodule. The settings of my app shows the primary repository but no additional repositories. Adding the submodule to the primary repositories did not help. Changing the cloning configuration for the submodule from SSH to HTTPS is NOT an option. Are there any additional steps which need to be taken?

Is there a way to use the build number that appears in Xcode Project Target's build number when we're deploying to Testflight using Xcode Cloud? I'm using Xcode cloud for both PR workflows (which also increases the build number in every build for checking whether the build is success or not) and for releasing our app to the Testflight and App Store. When we try to release our app to the Testflight using Xcode Cloud, it uses the build number that we used for PRs but I want to seperate them. I need to use the project target's build number. I tried to change the build number using Xcode Cloud settings in App Store connect, but it gives an error "The number entered must be greater than the latest Xcode Cloud build number". I need Xcode Cloud workflow to increment the latest Testflight build number, not the other build numbers that we use only for PRs. For instance; in my Testflight; the latest build number for v1.0 is 282, I want this to increment by 1 and when I use Xcode Cloud, I want this number to be 283 as it appears in my Xcode project target's build number. But when I use Cloud workflow, it uses the latest PR workflow's build number which is 2866. I can do this by creating manual builds using Xcode archieve. It takes the correct build number but I couldn't be able to do this by using Xcode Cloud workflows.

Hello, I am inquiring about the custom build script of Xcode Cloud. I added ci_post_xcodebuild.sh to the Post-Xcodebuild step according to the guide in the official document. I have some questions while using environment variables in Custom script. Will the IPA files stored in the environment variables CI_AD_HOC_SIGNED_APP_PATH, CI_APP_STORE_SIGNED_APP_PATH, CI_DEVELOPMENT_SIGNED_APP_PATH be uploaded to the App Store? If not, I wonder how the IPA files uploaded to the AppStore are processed and saved in which path. Also, if number 1 is wrong, for what purpose are these environment variables provided? I'll be waiting for the reply. Thank you.

Hello. I'm using XCode Cloud to replace an existing fastlane workflow where the end result is to post an IPA to in internal Slack channel. I've written a ci_post_xcbuildscipt.sh and it runs: xcodebuild -exportArchive -archivePath ${CI_ARCHIVE_PATH} -exportPath ${EXPORT_PATH} -exportOptionsPlist ${EXPORT_OPTIONS} -authenticationKeyIssuerID ${AUTH_KEY_ISSUER_ID} -authenticationKeyID ${AUTH_KEY_ID} -authenticationKeyPath ${AUTH_KEY_PATH} -allowProvisioningUpdates My problem is resigning the IPA with the environment variables set as secrets. The autenticationKeyPath expects to be a file, but I'm only able to pass strings as environment variables. I tried passing the key as a string and in my script writing it to a file, but the result is always an empty file. I've tested locally and this idea works, so I think it's a consequence of how the environment variables are protected when marked as a secret. Any suggestions on how I could successfully export my archive but keep the key a secret?

Is there any option to access to archived IPA using env variables? Looking at docs we can access just to xcarchive, using: CI_AD_HOC_SIGNED_APP_PATH CI_APP_STORE_SIGNED_APP_PATH CI_ARCHIVE_PATH CI_DEVELOPMENT_SIGNED_APP_PATH

Hi I'm trying to automatically create a what's new file based on the commits since the last tag However I keep on getting an error message in the logs. It off course works when I run it locally Any ideas git pull git fetch origin --all lastTag=$(git describe --tags --abbrev=0) echo $lastTag log=$(git log --pretty=format:"%s" "$lastTag..HEAD") echo $log echo $log > "$CI_WORKSPACE/TestFlight/WhatToTest.en-US.txt" The error is: fatal: No tags can describe 'cdae20770802a7d6b7e290c21bc2580e62c56d92'. Try --always, or create some tags.