I am doing brew install awscli with my ci_post_clone.sh. When doing so, I get the following error and awscli can no longer be installed. I remember that this error did not occur at the time of macOS Ventura 13.6.3, xcode 14.3.1 and only occurred after upgrading to macOS Sonoma 14, xcode 15.0.1, but I am now getting the same error after reverting back to macOS Ventura 13.6.3, xcode 14.3.1. Error: python@3.11: the bottle needs the Apple Command Line Tools to be installed. You can install them, if desired, with: xcode-select --install xcode-select --install If you're feeling brave, you can try to install from source with: brew install --build-from brew install --build-from-source python@3.11 I know that awscli depends on python 3.11, but I don't think it's an awscli problem because I was using awscli before the error appeared and was able to use it without any problems. I am wondering why the error suddenly appeared and whether the response to put brew install --build-from-source python@3.11 is correct. Thank you in advance for your response.

Since this morning, visionOS builds in XCode Cloud are failing. Did change anything in my configuration, the error on XCode cloud looks like visionOS is not installed: { platform:visionOS, id:dvtdevice-DVTiOSDevicePlaceholder-xros:placeholder, name:Any visionOS Device, error:visionOS is not installed. To use with Xcode, first download and install the platform } I attached a screenshot from the logs. Anyone know what is happening here and how to fix? Thanks, Patrick

I have a CI pipeline, which runs unit tests and exports the code coverage. I need to run the sonar-scanner tool to export the report to the sonarqube server running on a server that can only be accessed over a VPN only. How can I do this?

Five days ago everything was working as intended. Nothing has been changed on Workflows. All of a sudden, new builds are failing. The issue is with these two tasks during the Archiving: Export archive for ad-hoc distribution Export archive for app-store distribution I downloaded the Artifacts and checked the logs. If we look at the IDEDistribution.verbose.log then we see the following errors: "Error Domain=IDEProfileLocatorErrorDomain Code=1 \"No profiles for 'uz.uzum.avto' were found\" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=No profiles for 'uz.uzum.avto' were found, NSLocalizedRecoverySuggestion=Xcode couldn't find any iOS App Store provisioning profiles matching 'uz.uzum.avto'.}", "Error Domain=DeveloperAPIServiceErrorDomain Code=5 \"There is a problem with the request entity\" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=There is a problem with the request entity, NSLocalizedRecoverySuggestion=You already have a current Distribution Managed certificate or a pending certificate request.}", "Error Domain=IDECodesignResolverErrorDomain Code=1 \"No signing certificate \"iOS Distribution\" found\" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedRecoverySuggestion=No \"iOS Distribution\" signing certificate matching team ID \"x\" with a private key was found., IDEProvisioningError_UserInfoKey_IDEProvisioningErrorSpecifier=iOS Distribution, NSLocalizedDescription=No signing certificate \"iOS Distribution\" found, IDEProvisioningError_UserInfoKey_IDEProvisioningErrorPlatform=com.apple.platform.iphoneos, IDEProvisioningError_UserInfoKey_IDEProvisioningErrorAction=5, IDEProvisioningError_UserInfoKey_IDEProvisioningErrorTeam=<IDEProvisioningBasicTeam: 0x600001866280; teamID='x', teamName='(null)'>}" )} Issues seems to be related to certificates and etc. However, I checked the member center, and everything is fine with the certificates and profiles. Moreover, I can build, archive and distribute from my local machine with no issues at all. One particular thing that got my interest is the following: I opened the IDEDistribution.critical.log file, and saw the following issue: It seems Xcode Cloud is having a hard time to connect to App Store Connect. Please, help me to resolve the issue. I tried to change the Environment, to add new provisioning profile, but nothing works. FYI: I tried different environments to build, but the latest was: Xcode 15.0.1 macOS: Ventura 13.6.3 platform: iOS Deployment Preparation: Testflight (Internal Testing Only)

After months of the same script working properly, all of sudden, as of last night, our ci_post_clone.sh started failing with following error: 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. Here's what I've done: Re-applied: git update-index --chmod=+x ./ci_scripts/ci_post_clone.sh; still failed to execute returning same error I was using older flutter version so changed the flutter branch to stable - still same error. App code builds fine in local Xcode! APPRECIATE ANY HELP! Here is the script. #!/bin/sh # ci_post_clone.sh # Runner # # set -e echo "Running post clone script" # The default execution directory of this script is the ci_scripts directory. cd $CI_WORKSPACE # change working directory to the root of your cloned repo. # Install Flutter using git. git clone https://github.com/flutter/flutter.git --depth 1 -b stable $HOME/flutter export PATH="$PATH:$HOME/flutter/bin" # Install Flutter artifacts for iOS (--ios), or macOS (--macos) platforms. echo "Doing precache" flutter precache --ios echo "Installing cocoa pods" # Install CocoaPods using Homebrew. HOMEBREW_NO_AUTO_UPDATE=1 # disable homebrew's automatic updates. brew install cocoapods echo "calling pub get" # Install Flutter dependencies. flutter pub get echo "executing pod install" # Install CocoaPods dependencies. cd ios && pod install # run `pod install` in the `ios` directory. exit 0

Hello everyone! When I run UI Tests on Xcode Cloud, I often encounter unexpected failures. Checking the screen recording, I found that the iOS Simulator could go into a black screen with a white Apple logo and a progress bar for a period after the test starts. This behavior of the Simulator causes my app's UI Tests to fail randomly, which greatly affects the practical use of UI Tests. I suspect this phenomenon is unrelated to my app and test cases, so I'm asking if anyone else has encountered a similar issue. 🤔

Hello everyone! I've noticed that Xcode 15.2 is still not selectable as a build environment on Xcode Cloud, even though the official version of 15.2 has been out for several days. Is this part of the plan? Or is it a system bug? 🤔 I need 15.2 as the release environment, including support for building visionOS apps. I have already submitted FB13531029.

Hi there, In my custom script in ci-scripts, I had to call my git repository rest api to fetch registries (but also had to create tags, releases and more...) I added an ad-hoc secret environment variable to my workflow with a fresh access token as explained in this WWDC Video. But I wonder : Is there a way to get the git repository Access Token we provide to Xcode Cloud when we associate it to our git repository following the Source code management setup page as an Environment Variable of the project Workflows ? If I get it right, before I had the had-oc access token, I was able to clone the other git repositories of my project... So IMHO, the access token provided during the setup should be available somewhere (at least for the git commands).

Just a quick tip from what I discovered in the build times of our app in Xcode Cloud. Beware of selecting another simulator device instead of one of the recommended iPhones. Prepare Simulator Custom device: ~3m Recommended device: ~3s I assume Xcode Cloud comes preconfigured with the recommended iPhone. Any other device will take ~3m to setup in the testing step. (At least this is my assumption, please correct me if you have different findings.) You don't have to use all recommended iPhone. It will work if you just select one of them.

Xcode Cloud Builds seem flaky to me. Sometimes the test step fails (not necessarily the tests itself, but the step as a whole). Xcode Cloud seems to re-attempt this step. In my most extreme example, took 3 attempts to run them. For a build which usually takes 22m, it took 1h9m, but billed just 29m. Does anyone else experience this? PR-builds with a duration of >1h are not really acceptable. Here is the protocol. Testing usually takes <3 minutes.

Hi, Xcode Cloud just started failing with with this error. I can archive builds just fine locally in Xcode. Using Xcode 14.3.1. All my certs on my developer portal are current. 2024-01-02T16:26:44.707563433Z Error Domain=DeveloperAPIServiceErrorDomain Code=5 "There is a problem with the request entity" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=There is a problem with the request entity, NSLocalizedRecoverySuggestion=You already have a current Development Managed certificate or a pending certificate request.} 2024-01-02T16:26:44.707568258Z 2024-01-02T16:26:44.707575827Z error: exportArchive: No signing certificate "iOS Development" found The post at https://developer.apple.com/forums/thread/734179 is similar but without a resolution. Any help would be appreciated. Thank you.

I've created a test plan that includes the below configurations. {"configurations": [{ ... "options": { "defaultTestExecutionTimeAllowance" : 60, "maximumTestExecutionTimeAllowance" : 60, "testTimeoutsEnabled" : true }], "defaultOptions": { "defaultTestExecutionTimeAllowance" : 60, "maximumTestExecutionTimeAllowance" : 60, "testTimeoutsEnabled" : true, .... } ... } If I write a test that intentionally will take longer than 60 seconds, executing the test locally fails as expected with the error message Test exceeded execution time allowance of 1 minute let app = XCUIApplication() app.launch() let missingButton = app.buttons.firstMatch XCTAssertTrue(missingButton.waitForExistence(timeout: 120), "When a timeout is > 60 seconds, the default max setting of 60 seconds is still enforced") However, when this test is run using this test plan in XCode Cloud, it reports that it took 124 seconds to run and there is no message about exceeding execution time allowance. How can the test step be configured in XCode Cloud to ensure that the execution time allowances are respected?

when I download the sample backyard app from wwdc 23. The files for the Unit and Ui test are missing. Where do I find the? since I would like to see how they Apple implemented unit tests with SwiftData

Builds in the image had been submitted from yesterday to today, so that it does not been there for more than 1 day. But it expired and could not be downloaded from Testflight app. Image below is when I tried to update app to build number 17 in testflight. This happened few hours ago, and another app I was testing also has been expired and unable to download from testflight app. (I did not changed any settings on this app). What happened and what should I do?

Is there any way to view Code Coverage Report on Xcode Cloud? 🤔 Currently, I can see only the tests and their statuses - but no Code Coverage.

Hello guys I have just made an app and when I try to run it at my own iPhone even though I connected it physically but it says me build failed. How can I solved it, I made all the settings like: I set the developer users, I set the developer settings at my iPhone. What can I do for solving it?

I enrolled in the Apple Development Program by paying USD 99$ and got a confirmation email from Apple. But when I try to distribute the App in my Xcode, I still get the below error message: Team "Amit Gupta (Personal Team)" is not enrolled in the Apple Developer Program. Distribution requires enrollment in the Apple Developer Program. Visit https://developer.apple.com/account to enroll. Please help me to resolve this issue. I am trying hard but not able to resolve so far.

Hi, we're trying to reduce the Xcode Cloud usage in our project, and in the logs of the "Test" action I can see that there's a "Save artifacts" step that takes quite a while (more than 10 minutes), and it looks like a "fixed cost" that's impossible to reduce by improving the build and the tests themselves. In the "Artifacts" section of the Xcode Cloud build I can see that there a "Test Products" zip that's almost 5GB, which seems to be the cause of this slowness (I could verify that in other projects the same zip is smaller, and the "Save artifacts" step is much faster, as a result), but this seems a waste: we never need to download that "Test Products" zip, and its upload takes literally 10 fixed minutes from every single build with a "Test" action. Is it possible to either stop uploading the "Test Products" zip? Or maybe to skip the "Save artifacts" step entirely? Thanks

When building/archiving a mixed Obj-C/Swift app from an XCode Cloud Workflow, it seems that the GCC_PREPROCESSOR_DEFINITIONS (Preprocessor Macros) are not used. We use them for environment switching based on scheme and we'd like to send a test build to Testflight through XCode Cloud for internal testing. If this is the case, is the only option to rewrite code to use Swift Active Compilation Conditions?

I posted earlier about my problems seing my own build in the Testflight app, despite it being in "Testing" status for the internal tester group. I added more users and they are all receiving invitations and testing the build normally. I am the only one who doesn't see the build in my Testflight app in my iPhone. I tried sending myself a new invitation, I removed and re-added myself, nothing works. With other apps, no problems at all. I see my own builds and am able to install and run them as a member of the internal test group. The same app built with XCode installs and works normally on my phone. What is the problem with Testflight distribution ?