Suddenly, Xcode Cloud can not show any Git related info when trying to run any build. The repo is still connected because I still can select branch when configuring workflow.

When trying to build other branch than develop it says that my branch may only exist locally. All branches are published in the remote, so i don't know why is this happening... here is a screenshot of what i'm getting same goes for the scheme which is marked as shared and pushed to the repo...

The available environment variables have this: CI_BRANCH The name of the source branch that Xcode Cloud checked out for the current build, for example, main. However, this is only available for builds started by a branch change. I tried using it in a manual build, and it was just an empty string. Is there a way to get the branch name for manually started workflows? You have to choose a branch to start one, so I'd assume that info is available somewhere.

I am getting an error on Xcode Build The bundle version must be higher than the previously uploaded version. I am at a loss. My bundle version is set at 20. The latest version uploaded has bundle version 18. The project is clearly higher than the most recently uploaded version. What am I doing wrong? I tried setting the Bundle version in both the General tab for the target, in the Build Settings and in the Info.plist. Which takes precedence? Fastlane reports the current build version as 18 on TestFlight. Confusingly, throughout Xcode, Bundle Version is variously referred to as both 'Bundle Version' and 'Current Project Version', and is 'Build' on App Store Connect. App Store Version is variously referred to as 'Version', 'Bundle version string (Short)', and 'Marketing Version'.

If you have configured your workflows to use 'Latest Release', and there's a Release Candidate available, Xcode Cloud decides to use it. The problem is that the App Store rejects builds submitted with Release Candidate builds, at least that's what I'm encountering with Xcode 15.3 on the 27th of February, 2024: This is the 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'm not really sure if the issue is on Xcode Cloud or on the App Store, but something's up and they don't like each other right now!

Hello! Since Xcode 15 came out, I've been having this issue with UI tests where the test runner hangs for 60s when the keyboard is presented. In the test logs I get this kind of messages: 00:07.588 Wait for com.example.app to idle 01:07.642 App event loop idle notification not received, will attempt to continue. Interestingly, this only appears to be happening in CI environments (I've tried Xcode cloud and Circle CI). It works fine on my local machine. Everything is fine with Xcode 14, but I can't keep my CI environment stuck on Xcode 14 forever. I've tried disabling animations using UIView.setAnimationsEnabled(false), but it did not fix the problem. Here are the full logs of what it takes to fill out a text field: logs.txt

Hi , 'MobileRTCScreenShare/MobileRTCScreenShareService.h' file not found during xcode cloud build , but when i run on local its working fine , please suggest the right way to solve the problem

We added a unit test workflow to Xcode Cloud and the step to generate the test report takes a whopping 20 minutes. We have a few thousand tests but the entire run was 28 minutes—is this expected? Locally, running the test suite (on m1) runs in about 2 minutes.

I have a crash in my app that occurs during a test - but only when running on Xcode Cloud - locally tests always pass fine. I have a crash report that looks like the one below. I understand that abort is being called and includes an abort_message which I could normally see in the console if the debugger was attached, but as this is Xcode Cloud, is there any way where I can actually see this abort message? Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x10cb497a2 __pthread_kill + 10 1 libsystem_pthread.dylib 0x10cad4f30 pthread_kill + 262 2 libsystem_c.dylib 0x7ff80014cd30 abort + 133 3 libc++abi.dylib 0x7ff8002961b2 abort_message + 241 4 libc++abi.dylib 0x7ff80028838a demangling_terminate_handler() + 266 5 libobjc.A.dylib 0x7ff80004266e _objc_terminate() + 104 6 libc++abi.dylib 0x7ff80029560b std::__terminate(void (*)()) + 6 7 libc++abi.dylib 0x7ff800298024 __cxa_rethrow + 100 8 libobjc.A.dylib 0x7ff800063a71 objc_exception_rethrow + 37 9 CoreFoundation 0x7ff8003f1a32 CFRunLoopRunSpecific + 738 10 GraphicsServices 0x7ff80fe9d08f GSEventRunModal + 137 11 UIKitCore 0x7ff805bbb53d -[UIApplication _run] + 972 12 UIKitCore 0x7ff805bbffab UIApplicationMain + 123 13 SwiftUI 0x7ff84ab8aeda 0x7ff849b47000 + 17055450 14 SwiftUI 0x7ff84ab8ad93 0x7ff849b47000 + 17055123 15 SwiftUI 0x7ff84a82b0d7 0x7ff849b47000 + 13517015

here is my post clone scrip: #!/bin/zsh brew install swift-format And here is the errors im getting in the Xcode Cloud logs: Showing All Messages cd /Volumes/workspace/repository/ci_scripts && /bin/zsh /Volumes/workspace/repository/ci_scripts/ci_post_clone.sh ==> Downloading https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:02180ca8b8295422ae84921bcf034b7ee8ce5575488bd5e6a37a192e53cd5d34 #=#=# ##O#-# ### 5.5% ##################################################### 74.3% ######################################################################## 100.0% ==> Pouring portable-ruby-3.1.4.el_capitan.bottle.tar.gz Running `brew update --auto-update`... To restore the stashed changes to /Users/local/Homebrew, run: cd /Users/local/Homebrew && git stash pop ==> Homebrew collects anonymous analytics. Read the analytics documentation (and how to opt-out) here: https://docs.brew.sh/Analytics No analytics have been recorded yet (nor will be during this `brew` run). ==> Homebrew is run entirely by unpaid volunteers. Please consider donating: https://github.com/Homebrew/brew#donations Error: swift-format: the bottle needs the Apple Command Line Tools to be installed. You can install them, if desired, with: xcode-select --install If you're feeling brave, you can try to install from source with: brew install --build-from-source swift-format It is expected behaviour that most formulae will fail to build from source. It is expected behaviour that Homebrew will be buggy and slow when building from source. Do not create any issues about failures building from source on Homebrew's GitHub repositories. Do not create any issues building from source even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help building from source in Homebrew's discussions but are unlikely to receive a response. If building from source fails, try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it. Run command: 'cd /Volumes/workspace/repository/ci_scripts && /bin/zsh /Volumes/workspace/repository/ci_scripts/ci_post_clone.sh' ==> Downloading https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:02180ca8b8295422ae84921bcf034b7ee8ce5575488bd5e6a37a192e53cd5d34 #=#=# ##O#-# ### 5.5% ##################################################### 74.3% ######################################################################## 100.0% ==> Pouring portable-ruby-3.1.4.el_capitan.bottle.tar.gz Running `brew update --auto-update`... To restore the stashed changes to /Users/local/Homebrew, run: cd /Users/local/Homebrew && git stash pop ==> Homebrew collects anonymous analytics. Read the analytics documentation (and how to opt-out) here: https://docs.brew.sh/Analytics No analytics have been recorded yet (nor will be during this `brew` run). ==> Homebrew is run entirely by unpaid volunteers. Please consider donating: https://github.com/Homebrew/brew#donations Error: swift-format: the bottle needs the Apple Command Line Tools to be installed. You can install them, if desired, with: xcode-select --install If you're feeling brave, you can try to install from source with: brew install --build-from-source swift-format It is expected behaviour that most formulae will fail to build from source. It is expected behaviour that Homebrew will be buggy and slow when building from source. Do not create any issues about failures building from source on Homebrew's GitHub repositories. Do not create any issues building from source even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help building from source in Homebrew's discussions but are unlikely to receive a response. If building from source fails, try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it. Command exited with non-zero exit-code: 1 The ci_post_clone.sh is not executable and was run using zsh (default shell on macOS). To make sure your script runs correctly, make the file executable using `chmod +x` and add an appropriate shebang line. I feel like Xcode Cloud can't possibly be missing Xcode command line tools. I also can't imagine they forgot to run chmod +x on the default run script files Any Ideas here?

Hi! I was able to setup Xcode Cloud and build manually without problems. Also, GitHub integration with Xcode works, I can commit and push changes to my GitHub repo. Unfortunately, I am not able to trigger a Xcode Cloud build by pushing changes to my repo. Tried git push via Xcode 15.2 and via command line. The push itself always works. I was under the impression this should "just work", if the workflow includes a start condition set to Branch Changes, Any Branch, no custom conditions. I have one single branch. Fails silently, no visible activity, neither in Xcode nor in the App Connect portal. Any ideas? Am I missing something? Best regards

Yet another issue with Xcode Cloud which never happened before. I am losing my hope on Xcode Cloud and looking to change my CI options, since we are stumbling upon unexpected issues for the second time during last two weeks. This time, it is even worse. I can't start building from any workflow. Whenever I try to do so, just an alert pops up saying "This operation could not be completed". Build process doesn't even start, it doesn't even try to clone my repo, it just fails. Anyone faced such an issue before? How were you able to fix it?

After following the guides, I have Xcode Cloud hooked up to my Gitlab and it's all working nicely. However I want to also have the build artefacts stored on Gitlab also. I know it will involve a ci_post_xcodebuild.sh script but I can't find any information on what I actually need to do. I don't want to be manually downloading them for every release!

Getting these errors for most (but not all) builds: ERROR: Could not find a valid gem 'drb' (= 2.0.6), here is why: Unable to download data from https://rubygems.org/ - Errno::ECONNRESET: Failed to open TCP connection to rubygems.org:443 (Connection reset by peer - connect(2) for "rubygems.org" port 443) (https://rubygems.org/specs.4.8.gz) ERROR: Could not find a valid gem 'activesupport' (= 6.1.7.6), here is why: Unable to download data from https://rubygems.org/ - Errno::ECONNRESET: Failed to open TCP connection to rubygems.org:443 (Connection reset by peer - connect(2) for "rubygems.org" port 443) (https://rubygems.org/specs.4.8.gz) ERROR: Could not find a valid gem 'cocoapods' (= 1.14.3), here is why: Unable to download data from https://rubygems.org/ - Errno::ECONNRESET: Failed to open TCP connection to rubygems.org:443 (Connection reset by peer - connect(2) for "rubygems.org" port 443) (https://rubygems.org/specs.4.8.gz) from this code in ci_post_clone.sh: gem install drb -v2.0.6 gem install activesupport -v6.1.7.6 gem install cocoapods -v1.14.3 Xcode environment: XCODE VERSION: Xcode 15.2 (15C500b) MACOS VERSION: macOS Sonoma 14.3.1 (23D60) Any help would be greatly appreciated!

I'm investigating converting our pipeline that uses Gitlab runners and Fastlane to XCode Cloud. I think I got the basic workflow set up ok, but the problem comes in when trying to archive to a different version - we generally have the next release in our develop branch, the following release in a delta branch and/or feature branches, and sometimes switch to a far-future version to test things when we don't want a build on the current release to confuse our testing team. With our current setup, we have a Fastlane lane that checks the version in our project, checks the latest build number for that version, and increments it, like so: lane:checkAndIncrementBuildNumber do # Increment the build number localProjectVersion = get_version_number_from_plist( xcodeproj: PROJECT_NAME, target: TARGET_NAME, build_configuration_name: BUILD_CONFIGURATION, plist_build_setting_support: true) current_build_number = latest_testflight_build_number(api_key_path: API_KEY_PATH,version: localProjectVersion) increment_build_number( build_number: current_build_number + 1 ) incrementedBuildNumber = get_info_plist_value(path: INFO_PLIST_PATH, key: "CFBundleVersion") File.write(VERSION_NUMBER_FILE_NAME, localProjectVersion) File.write(BUILD_NUMBER_FILE_NAME, incrementedBuildNumber) File.write(VERSION_BUILD_FILE_NAME, localProjectVersion + " (#{incrementedBuildNumber})") File.write(IPA_FILE_NAME_FILE, IPA_FILE_NAME_START + localProjectVersion.tr(".","") + "b" + incrementedBuildNumber + ".ipa") end Can I just call this lane or something like it in the ci_pre_xcodebuild script? Or is there a way to replicate this functionality without having to set up new workflows every time we switch releases?

Hello everyone, good day. For months now, I have been trying to get the iOS 17 simulator on my MacBook Pro. Unfortunately, it failed during the installation process. When it reached 100%, it showed 'installing,' but, regrettably, it failed and displayed the following error: (-67061 invalid signature (code or signature have been modified) Domain: SimDiskImageErrorDomain Code: 5 User Info: { DVTErrorCreationDateKey = "2024-02-02 13:57:23 +0000"; unusableErrorDetail = ""; } Has anyone ever come across this error? I would appreciate it if anyone could shed light on what it means and provide guidance on how to bypass it before attempting the installation again.

We have multiple dev teams (let's say 10) and we would like to create a workflow for them to archive a build and push it out to their respective TestFlight team without letting them modify the workflow. Is this possible? Or would we have to create 10 nearly identical workflows, with the only difference being the Post-Action TestFlight group? In GitHub Actions, for example, some actions triggered manually allow you to pass in variables to your workflow when you kick them off.