Since I started using XCode Cloud, my builds regularly failed due to networking issues, which is really just embarrassing. How can a company like Apple, which praises itself with a high-quality standard, ***** this up so badly? However, since two months ago literally every single build started failing for "connection reset by peer" My ci_post_clone.sh runs this code and surprisingly enough that step succeeds most of the time. #!/usr/bin/env bash set -e brew install cocoapods curl -s "https://get.sdkman.io" | bash source "$HOME/.sdkman/bin/sdkman-init.sh" sdk install java 20.0.1-tem # cd into actual project root cd ../../../ ./gradlew app:ios:podinstall However in the archive task the errors start rolling in 2023-08-30T22:27:24.108163427Z Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11. 2023-08-30T22:27:24.108168428Z > Could not get resource 'https://repo.maven.apache.org/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108173676Z > Could not GET 'https://repo.maven.apache.org/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108181057Z > Got socket exception during request. It might be caused by SSL misconfiguration 2023-08-30T22:27:24.108186894Z > Connection reset by peer 2023-08-30T22:27:24.108206745Z Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11. 2023-08-30T22:27:24.108213605Z > 2023-08-30T22:27:24.108219500Z Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108234940Z > 2023-08-30T22:27:24.108239423Z Could not GET 'https://dl.google.com/dl/android/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108662595Z Got socket exception during request. It might be caused by SSL misconfiguration 2023-08-30T22:27:24.108669328Z 2023-08-30T22:27:24.108716268Z 2023-08-30T22:27:24.108725059Z > 2023-08-30T22:27:24.108732903Z Connection reset by peer 2023-08-30T22:27:24.108740596Z 2023-08-30T22:27:24.108748688Z > 2023-08-30T22:27:24.108759002Z Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11. 2023-08-30T22:27:24.108820147Z > 2023-08-30T22:27:24.108829571Z Could not get resource 'https://maven.pkg.jetbrains.space/public/p/compose/dev/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108837310Z > 2023-08-30T22:27:24.108844471Z Could not GET 'https://maven.pkg.jetbrains.space/public/p/compose/dev/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'. 2023-08-30T22:27:24.108860417Z 2023-08-30T22:27:24.108866956Z > Got socket exception during request. It might be caused by SSL misconfiguration So because it is highly unlikely or actually statistically impossible that repo.maven.apache.org, dl.google.com and maven.pkg.jetbrains.space all always decide to crash simultaneously whenever I run an XCode build for the past 3 months, this has to be an issue on their part. Did they suddenly stop allowing internet connections in the archive step? Apple Support was just useless and aksed for irrelevant and impossible information like: my browser my ipa file (of a failing build?!) Does anyone have any idea what causes this or has contacts to someone at apple which can fix this?

Hi I'm using flutter and integrated the repository to xcode cloud to compile the app and in my machine compiles and uploads fine to testflight but using xcode cloud it throws an error could not find included file 'Generated.xcconfig' in search paths it does not make sense to me if I'm honest, but I'm running out of options The other thing I like to confirm is if xcode cloud works at all with flutter, I'm getting the feeling that is the case

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

Hi, I'm trying out Xcode Cloud but can't get it to build in my scenario. The use case is the following: My project has multiple swift packages that depend on each other. "App" has a local package dependency called "SPMKit". "SPMKit" has a local package dependency called "SPMKit2". The issue I run into is if "SPMKit2" has any dependencies, it doesn't resolve in Xcode Cloud. Are local dependencies like this not supported in Xcode Cloud? All the packages are in the same directory as my app. I'd like to not have to put each package in it's own git..

We want to upgrade our tier, but the only option we've found is via Apple Pay through the Developer app. We can't do that because it is impossible to add a business card to apple pay in Croatia. What are our options? Thank you in advance.

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.

I have two steps in my Xcode Cloud workflow. The first one builds the app, the second runs all the tests. The issue I am seeing is that the second step fails with a timeout. However, all the tests in the step are green. I think this might be a bug in Xcode Cloud and would like to get assistance. The error message I get is: The step invocation hit a user timeout. The xcodebuild test-without-building invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 35 minutes. MyApp (3333) encountered an error (Test operation was canceled. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult) In the logs, I was able to find the step that fails: Run command: xcodebuild test-without-building -destination platform=iOS Command exited with non-zero exit-code: 75 The error code is 75, which, after some googling, I was able to identify to be: temp failure; user is invited to retry. However, this does not bring me closer to fixing the issue. I turned on the Execution Time Allowance feature to get a spin dump (metadata + stack traces). However, since it's not a single test that times out, we do not get a spin dump. Xcode Cloud setup: Xcode 14.3.1 (14E300c) macOS Ventura 13.5.1 (22G90) I'm looking for help, hints, ideas. What could be the reason for the timeout?

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 have created a Swift package build tool plugin for colour generation. The plugin takes two input files from a project or swift package and from them generates a new Swift file containing references to all of the generated UIColors. When building locally and when using Github Actions the plugin is able to generate the required file within the pluginWorkDirectory and the project that references it can then access it as an input file during its build process. However, when building my project using Xcode Cloud, the plugin appears to be unable to create the file, it fails with the following error: Error while generating colours Files encountered an error at '/Volumes/workspace/DerivedData/SourcePackages/plugins/GLA.output/GLA/ColorGeneratorPlugin/GeneratedColors/Colors.swift'. 2022-11-22T15:46:11.344345498Z Reason: fileCreationFailed 2022-11-22T15:46:11.344390826Z LLVM Profile Error: Failed to write file "default.profraw": Operation not permitted` This then means that the build of the project fails with this error: Error opening input file '/Volumes/workspace/DerivedData/SourcePackages/plugins/GLA.output/GLA/ColorGeneratorPlugin/GeneratedColors/Colors.swift' (No such file or directory) It appears that Xcode Cloud is blocking the creation of files in the pluginWorkDirectory, even though locally it can. Has anyone faced a similar issue? Is there anything I can do to make it work in Xcode Cloud?

Hello Apple team, We're having a problem submitting one of our apps to TestFlight via Xcode Cloud. We have over 10 apps with the same codebase and all of them build successfully. However, one application fails to build in Xcode Cloud, although there is no problem with manual build. We would appreciate your help in resolving this situation. Can you please help us resolve this issue? We are ready to provide additional information or logs to clarify the causes of the error. Sincerely, Anton Babich Xcode Cloud Archive - iOS encountered a failure that caused the build to fail. Prepare Build for App Store Connect Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “moBiel Live.app/Frameworks/grpcpp.framework/grpcpp” 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. Prepare Build for App Store Connect Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “moBiel Live.app/Frameworks/Braintree.framework/Braintree” 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.

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

Hello, I'm trying to upload my code coverage to an external service. I've created a workflow on Xcode Cloud that build and run my test + a ci_post_xcodebuild script that uploads my Project.xcresult to an external service My problem here is that I need the repository source code the moment I upload my coverage file. I have two steps in my workflow: Build tests (Which contain the sources but not the coverage results) Run tests (Which contain the coverage result but not the sources) I found this in the Apple documentation: Lastly, it should be noted that in a test action, multiple environments are used to build and run your tests. Only the environment that is used for building your tests will have your source code cloned into it by default. The environments that run your tests won't have source code cloned into them. They'll only have the ci_scripts folder made available on them. As a result, the post-clone script won't run in these environments and your custom scripts and any of their dependencies, such as other shell scripts and small tools, must be entirely contained within the ci_scripts folder. Source: https://developer.apple.com/videos/play/wwdc2021/10269/ I feel a bit stuck here maybe Xcode cloud is not the way to go for this but I was wondering if by any way I could still check out my project sources after the test execution.