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?

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

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 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'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.

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?

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?

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?

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

I have a repo with hundreds of tags (we make a tag for every build and for every version, and it has a browser extension project pulled in as a subtree where all those commits can and do have version tags of their own). I am trying to create a simple tag-triggered workflow to release my app to the external users and the app store, so I want to trigger it every time I update and push an e.g. latest tag. I created a workflow and setup the tag trigger accordingly, but, in the workflow config, it says it can't find the tag. I saved the workflow anyway, however, when I try to manually trigger the workflow and browse the Tags tab, I only see a subset of the repo's tags. I suspect Xcode Cloud might be limiting the number of tags it pulls and consequently shows when searching tags. I think this is a bug/shortcoming of Xcode Cloud. Is there any way to work around this?

Xcode cloud builds were failing with the following error. It wasn't the problem before yesterday morning 26.Apr.2023 before 1:00 PM. Please let me know what the issue is or if there is anything I can do to solve this. Additional information: The app is a react-native app. error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected flush after ref listing info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. [in /Volumes/workspace/repository/ios] [!] Invalid Podfile file: cannot load such file -- /Volumes/workspace/repository/node_modules/react-native/scripts/react_native_pods. from /Volumes/workspace/repository/ios/Podfile:1 ------------------------------------------- require_relative '../node_modules/react-native/scripts/react_native_pods' require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules' ------------------------------------------- Error Command exited with non-zero exit-code: 1

After creating a new build and release with XCode Cloud, uploading a zip of the dSYMs to Firebase Crashlytics no longer gets processed. Despite uploading several times I'm still seeing errors like: This app has 15 unprocessed crashes. Upload 1 dSYM file to process them. Has something changed in the last 2-4 weeks in this process that I'm unaware of? TIA

Can we get a new feature? Ability to set the bundle ID via the API for Xcode Cloud? When we run multiple version - we want to set it to be the same as our Bitbucket bundle number. And we do a ton of builds that are not sent to Xcode Cloud. So if we could set the next build number (the UX already has this - but need it programmatically). https://developer.apple.com/documentation/appstoreconnectapi/xcode_cloud_workflows_and_builds

I am getting an error on Xcode Build The bundle version must be higher than the previously uploaded version. I am at a loss. My bundle version is set at 20. The latest version uploaded has bundle version 18. The project is clearly higher than the most recently uploaded version. What am I doing wrong? I tried setting the Bundle version in both the General tab for the target, in the Build Settings and in the Info.plist. Which takes precedence? Fastlane reports the current build version as 18 on TestFlight. Confusingly, throughout Xcode, Bundle Version is variously referred to as both 'Bundle Version' and 'Current Project Version', and is 'Build' on App Store Connect. App Store Version is variously referred to as 'Version', 'Bundle version string (Short)', and 'Marketing Version'.

Hi, In our current CI/CD environment, I can easily upload an IPA to Firebase so that we can distribute test versions of the app. Now we are trying to move the CI/CD to Apple Xcode Cloud and I am trying to figure out how to upload my app to the Firebase Distribution system. Please advise ;-) Kind regards, Wouter

Hi I'm piloting using Xcode Cloud for my builds. Recently, I inadvertently burned up all my compute hours for the month. I know I could move to a higher-level plan, but I really want to understand how I can avoid doing this in the future. I know I can view my usage in App Store Connect but I'm looking for ways to be alerted if my remaining compute hours go below a threshold that gives me time to react. Questions: I don't think I got any emails from Apple warning me that my compute hours were near to being used up - should I have received something? I don't see an options for this in the Settings or Usage pages. I have been using the App Store Connect API and have been going through the API docs trying to find an endpoint that returns the compute hours balance for my account but haven't found one - does one exist? Thanks, Dave

When Building with XCode Cloud I receive errors reading Cocoapods xcfilelist files. The errors are as follows: Unable to load contents of file list: '/Target Support Files/Pods-<Project Name>/Pods-Anytune-frameworks-Release-output-files.xcfilelist' Unable to load contents of file list: '/Target Support Files/Pods-Anytune/Pods-<Project Name>-resources-Release-output-files.xcfilelist' When building through Xcode (Product > Build) everything works, however this is not the case with Xcode Cloud. I have verified that the xcfilelist paths exist on my machine, however with Xcode Cloud they are unable to load. I have also tried cleaning, updating and rebuilding my Cocoapods to no avail. This issue exists on stackoverflow. Link is found here. The solutions here did not work for me. Any help would be appreciated.

Recently, I have trouble with my Xcode Cloud builds, where they seemingly complete, but the very final step does not happen. I am building from the same codebase for both macOS and iOS (I have two “Archive” steps in my workflow, one for iOS and one for macOS). The iOS one usually completes fast without problems. The macOS log ending looks like this, and remains stuck forever, with the macOS build in the “spinning progress” state and never completing. Is there something I can do on my end to make this work better? I would not want to go back to manual builds, Xcode Cloud is convenient and was working well for a while, but this is really annoying lately.

On our projects we have separate targets for staging and production (and also separate accounts). I was able to connect xcode cloud to staging account and builds were working ok, but when I made workflow for production (with same app on gitlab) I could not get access. I never got an option to make new app in gitlab so I went and delete all xcode cloud data and gitlab app. Now when It wants to connect to gitlab I get no option to authorize app or create a new one. I also cannot delete SCM