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?

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.

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'

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?

Not sure if this reaches Apple's relevant/concerned teams. If we can have date column of the app upload here, it would help immensely. Or, a popover of dates of upload, ready to submit etc.

I Can't Login into my testflight because I don’t have the invitation code, Please I need an urgent solution to access my testfight

I've configured a workflow to run through tests when a PR is changed. https://developer.apple.com/documentation/xcode/configuring-start-conditions Is it possible to configure it so that the tests don't run while it's a draft PR and to only run it once it's moved to ready for review?

I followed Apple's instructions. When i come to the step where one should copy the auto-generated secret from the newly created GitLab Application - i can't proceed without an error. The auto-generated secret from the GitLab application is 64 characters long + a prefix: "gloas-". So it is actually 70 characters long. The AppstoreConnect website form that wants this secret doesn't accept it, saying, it is too long and also in the wrong format. If i enter the secret without the prefix, the form accepts the value - but the authentication attempt that follows afterwards fails. I tried the whole process with a fresh Xcode project. It still failed - so i'm pretty sure that the project is fine and the problem is most likely the GitLab Application secret. I also read the Xcode Cloud requirements page and everything seems to be correct. The only thing that doesn't work - which should, according to the above linked manual - is AppstoreConnect not accepting the complete GitLab application secret. So how can i get this to work?

I just added my first Xcode 15, Swift 5.9 macro from an open source package that I'm referencing via Swift Package Manager. The first time I compiled locally, I had to trust the macro's package via a dialog box, which is fine for a local build. However, now my app doesn't build on Xcode Cloud, with the error "Target must be enabled before it can be used." How do I tell Xcode Cloud to trust the macro's target?

Hi everybody! I have a Test Action step where I generate a .json file with the results, and I need to retrieve this file. The way I'm trying to do is: Generate the file in ci_post_xcodebuild.sh, check if file exist If file exists, copy into $CI_ARCHIVE_PATH But looks like this $CI_ARCHIVE_PATH is not the correct way to copy file inside Archive. Do we have a way to retrieve a file easily?

it seems that there were some suggestions of using DerivedData folder as a caching mechanism for at least the same branch building, but after trying it out it does not seem like this is a viable option. Is there any caching capabilities? If there is does the cache expire? Is there size limit perhaps?

I've been really happy with Xcode Cloud, but as a single developer with a very simple app, I cannot justify the upcoming paid service. I have two apps with minimal amount of work going on for the one that I used to test Xcode Cloud. Two questions: What do I need to do with my Xcode project to successfully disable Xcode cloud? What is the correct approach to disable the upcoming billing for Xcode cloud? Thanks for any pointers.

I have Xcode Cloud setup to run my unit tests a couple of times a day so I can be informed of any API issues. Quite often, my tests will fail with "A server with the specified hostname could not be found." even though the server is fine. I re-run the tests locally in Xcode and they all pass. I'm wondering if there's something Xcode Cloud might be doing to the request to make the connection fail? Is it possible to maybe setup a proxy for the tests from Xcode Cloud?

I have been trying for a couple of days now to get Xcode cloud running. But after some struggle with cocoapods the ci_post_clone.sh is working. But now it fails at the archive section with no real explenation what went worng. I have my profisioning profile connected to the right bundle-id. Run command: 'xcodebuild archive -workspace /Volumes/workspace/repository/wevize/ios/Runner.xcworkspace -scheme Runner -destination generic/platform=iOS -archivePath /Volumes/workspace/build.xcarchive -derivedDataPath /Volumes/workspace/DerivedData -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStream34ff2ba9-cd2a-4e3b-befb-3243d688c7f5.json -IDEPostProgressNotifications=YES CODE_SIGN_IDENTITY=- AD_HOC_CODE_SIGNING_ALLOWED=YES CODE_SIGN_STYLE=Automatic DEVELOPMENT_TEAM=KTJT289M8K COMPILER_INDEX_STORE_ENABLE=NO -hideShellScriptEnvironment'

I just renewed my developer subscription, and created a new app.

For the past few days we've been observing a degraded performance on Xcode Cloud. Some builds get queued for hours and never start. I just cancelled one that's been queued for an hour and a half: Is this a known issue?

Hi, My customer wants to be able to modify the Xcode Cloud subscription plan on a PC - he has no iOS device and no Mac available. How can my customer do that? So far I was only able to do that in Apple's Developer.app or on iOS Devices. Is there a webservice where I can change the subscription plan? Is there an official PC version for Apple's Developer.app? Are there any other alternatives? Thanks, Juergen

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?

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?

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.