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 Can't Login into my testflight because I don’t have the invitation code, Please I need an urgent solution to access my testfight

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.

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?

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'

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 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"

I have recently moved our CI/CD pipeline to using xcode cloud. Everything has been going great until we tried to test our VoIP pushes in our test environment. In our old system, our entitlements file set the apns-environment to develop, so when we distributed an archived build to our QA team, it would generate sandbox APNS device tokens for testing. But since I have switched to xcode cloud, it looks to be generate production apns device tokens now, so all of our sandbox pushes are failing to send. Is there a way I can make sure xcode cloud send builds that have the apns-environment set to development?

I got the app building and running in simulator and in my iPhone without problems. I use the KingFisher framework and i can see it under Project -> Package Dependancies with Version Rules 7.0.0 - Next Major and Location its GitHub repo. After trying to build in XCode Cloud in order to see the app in the App Store Connect (and ultimately prepare it for TestFlight) I got : a resolved file is required when automatic dependency resolution is disabled and should be placed at /Volumes/workspace/repository/Explore Mars.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved. Running resolver because the following dependencies were added: 'kingfisher' (https://github.com/onevcat/Kingfisher.git)fatalError This Error appears twice under 'All Issues', in Configuration Issues and in Swift Package Dependancies. I have tried clean, rebuild, delete and re-install the KingFisher, ask ChatGPT - nothing works. Also worth noting that I checked in Finder and I dont have folder 'swiftpm' in the 'xcshareddata' neither ofcourse 'Package.resolved' (I also tried to mkdir swiftpm but I have no idea what the Package.resolved should include. PLS HELP :)

Xcode Cloud always exports archive using ad-hoc, development and app-store profiles. This uses up 5-6 more minutes always for my app. How to disable and allow export only in single distribution profile

Over the past few months in Xcode Cloud I've have Environment Variables that have had the prefix "TEST_RUNNER_". In the Apple Documentation it was mentioned that this was correct - https://developer.apple.com/videos/play/wwdc2022/110361/. Environment variables can provide parameters to both the XCTest test runner app on your device and the test host running xcodebuild. In Xcode Cloud, environment variables prefixed with TEST_RUNNER_ get passed into the XCTest test runner. This prefix will be stripped prior to the variable being made available to your code. So, for example, a variable in your test code named BASE_URL would be passed in as the environment variable named TEST_RUNNER_BASE_URL. Test plans require the same format as test code. Namely, we do not add the TEST_RUNNER_ prefix. As of last week I'm now getting an error when I add "TEST_RUNNER_" in front of my environment variable in Xcode Cloud. Is this a bug on Apple's end or is there a way for me to fix this?

Currently, I'm developing the new SDK and unable to upload to test flight for external testing purposes, is this even possible? Or would anyone who wants to test my app need to manually do it from their own Xcode 14 beta.

Is there a way to use the build number that appears in Xcode Project Target's build number when we're deploying to Testflight using Xcode Cloud? I'm using Xcode cloud for both PR workflows (which also increases the build number in every build for checking whether the build is success or not) and for releasing our app to the Testflight and App Store. When we try to release our app to the Testflight using Xcode Cloud, it uses the build number that we used for PRs but I want to seperate them. I need to use the project target's build number. I tried to change the build number using Xcode Cloud settings in App Store connect, but it gives an error "The number entered must be greater than the latest Xcode Cloud build number". I need Xcode Cloud workflow to increment the latest Testflight build number, not the other build numbers that we use only for PRs. For instance; in my Testflight; the latest build number for v1.0 is 282, I want this to increment by 1 and when I use Xcode Cloud, I want this number to be 283 as it appears in my Xcode project target's build number. But when I use Cloud workflow, it uses the latest PR workflow's build number which is 2866. I can do this by creating manual builds using Xcode archieve. It takes the correct build number but I couldn't be able to do this by using Xcode Cloud workflows.

I have checked that my scheme is shared and I do in fact have the scheme in my xcode project. But whenever I try to run Xcode cloud, it fails with the message that "A scheme named 'MyAppScheme' does not exist in MyAppProject.xcodeproj" Any tips on what I could be doing wrong?

Hi I'm trying to automatically create a what's new file based on the commits since the last tag However I keep on getting an error message in the logs. It off course works when I run it locally Any ideas git pull git fetch origin --all lastTag=$(git describe --tags --abbrev=0) echo $lastTag log=$(git log --pretty=format:"%s" "$lastTag..HEAD") echo $log echo $log > "$CI_WORKSPACE/TestFlight/WhatToTest.en-US.txt" The error is: fatal: No tags can describe 'cdae20770802a7d6b7e290c21bc2580e62c56d92'. Try --always, or create some tags.

Hi! I have a big problem about crash feedback. In my app, "Open in Xcode" is not showing when user devices are more than iOS 16.4(maybe 16.5). There are screenshots. I archive my app by Xcode Cloud. iOS16.6 iPhone13 iOS 16.3.1 iPhone SE iOS 16.5 iPhone SE