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 ?

Hi community: I found that after Xcode update from 14.3.1 to 15.0.1, my UITests fail only on the CI (Apple Xcode Cloud) because the use of boundElementsByIndex. Seems that the use of this property stale the main thread: Failed to resolve query: Unable to perform work on main run loop, process main thread busy for 30.0s Is it a known issue? Thanks

Hi guys, I already use Transporter to upload the IPA file to the App Store Connect. However, a blank space appears in the TestFlight (App Store Connect), and it will disappear if we refresh the webpage. Does anyone know how to solve this as I can't submit my new version of apps.

Hi there, I'm trying to find this information but I don't see it anywhere. What happens when I reach the maximum of 1000 hours/month used on Xcode Cloud? Can I buy additional hours or can I get them reset if I pay again? I'm not near close to using that but I think we should have a public answer for this scenario. Thanks!

Hello everyone, we are moving to Xcode Cloud and we are facing the following problem on the release workflows based on tag changes. We were previously tagging versions with semantic versioning, for example v1.0.0-beta.1 for beta builds and just v1.0.0 for release builds. These tags archive different targets, with Fastlane we got the tag from the environment and one or another was built based on it. The problem is that Xcode Cloud doesn’t seem to support regular expressions so we don’t know how to make an specific workflow for beta and another for release based on the tag. I just see the option “Tags beginning with…” which doesn’t fill our needs.

All the steps within our Archive action complete as expected with green checkmarks (including all Prepare Build for App Store Connect steps), but the Archive action itself never completes. It keeps spinning and never passes it off to the post-action to release the build to TestFlight. The system status page says Xcode Cloud had issue for multiple days this week, but they resolved 14 hours ago. I've re-run our build several times today and keep running into this problem. Is this something server-side?

Yesterday builds worked fine, today they do not, even building the exact same source (same tag), with no changes to the Xcode Cloud workflow or anything else. Code Signing IDEDistributionIssueSeverity=3, NSLocalizedDescription=Automatic signing cannot update bundle identifier "x.y.z"., NSLocalizedRecoverySuggestion=Automatic signing cannot update your registered bundle identifier to enable . Update your bundle identifier on https://developer.apple.com/account and then try again. The logs show this: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/5655f7e3-ccb2-4556-b4cb-70a3a0e6bae8.xcarchive -exportPath /Volumes/workspace/appstoreexport -exportOptionsPlist /Volumes/workspace/ci/app-store-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.62.130:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/app-store-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70 Is anyone else having this problem? Suggestions for fixing it?