Hi Guys, I was wondering if anyone here experienced an error with XCode Cloud when running pipelines, specifically Error is: "An internal error was detected which caused this stage to error. The error has been logged, and you can re-run this build again." Upon checking the logs, there is no specific error other than the above and "The pipeline action could not complete due to an error. The error may not occur on rebuild." Note that in the pipeline, there is an obfuscation step using IXGuard. However, the IXGuard steps show successful on the logs.

Dear We try to generate IPA with Xcode Cloud but this task fail in Export archive phase (Export archive for app-store distribution). The error that appear in the archive logs is: error: exportArchive Provisioning profile "iOS Team Store Provisioning Profile: cl.app.myapp" doesn't include the com.apple.CommCenter.fine-grained entitlement. Any idea about to resolve this problem ? king regards

My team's Xcode Cloud build started timing out when we recently upgraded to Xcode 16.0.0. Specifically, the test build phase times out due to exceeding the 2 hour limit. The Test - iOS action could not complete due to an error. The error may not occur on rebuild. Build has exceeded the maximum allotted time. Each build can run for up to 120 minutes. If a build has not yet finished at this time, all incomplete actions will be cancelled. When running Xcode 15.4.0, the test build phase completed in roughly 45 minutes. It's also important to know that our test build completes in about 15 minutes when executing on one of our in-house Mac mini build machines (Apple Silicon). So the issue seems to be with Xcode Cloud + Xcode 16.0.0 and not our project. We have been burning through Xcode Cloud hours hoping that at some point Xcode Cloud will be fixed. The status page right now is all "green": https://developer.apple.com/system-status/ Is there a known issue with Xcode Cloud + running tests? We have combed through our project's Xcode Cloud logs and artifacts, but nothing jumps out as something on our end. Also, there is a large file named "Test Products for ", but we can't download it due to crashes/ errors: The Xcode IDE UI shows this file as 1.99GB Xcode crashes when attempting to download the file. The App Store Connect UI shows this file as ~1GB (possibly just omitting precision). An error response page is returned when attempting to download. Thanks in advance for any advice/ feedback.

When testing on Xcode Cloud I am unable to use any simulators between iOS 16.2 and 17.5. I'm glad that there are options for <= 16.1, but given how small those userbases must be at this point it feels rather odd. Similarly, iOS 18 is still very new so it also has a disproportionately small number of users on it. Does not seem to matter if explicitly selecting Xcode/macOS versions. Am I configuring something incorrectly? Picked something wrong on a dropdown, checked the wrong box when setting up the workflow? Xcode 15.4 allows building to iOS 17.5, but not iOS 18. 🙃

Error: 'Runningboard has returned error 5' I am able to run my unit tests locally just fine. When I run them to from xcode cloud It fails everytime. I did notice in app store connect that it gives me a warning 'Grant access to the following repositories to allow them to be used for this product.' as I am using google sign in iOS(https://github.com/google/googlesignin-ios.git). However I cannot grant this access as I do not have privileges to google code base. I have imported the google sign in via swift package manager and everything works fine. This is the report from xcode cloud if it helps. Happy to add any additional info that will help

Hi I am trying to integrate Xcode Cloud in our project but always getting This operation could not be completed error on Grant Access to Your Source Code screen. Upon send a feedback got to know that there is a API failure with status code 403. please help in resolving this Thanks

I have been investigating a recent breakage where apps being installed via Testflight are crashing on launch with no helpful crash reports, or even console-accessible logging. More detail: The app launches just fine on iPadOS 18 beta (ipad) but the same build doesn't work on iPadOS 17.6.1 At my wit's end, I checked the entire build environment - was I using XCode beta still somewhere? Well, in the XCode Cloud workflow, I had selected "Release" for the latest released version of XCode. And MUCH to my surprise, I see that XCode 16 RC is selected. Why? That's not released yet... Anyway, this is just a friendly PSA to check your XCode Cloud workflows if you choose "release" when new XCode releases are upcoming... or peg your XCode Cloud environment versions. And I still don't have an explanation why Testflight XCode 16 RC is producing builds that crash on iPadOS 17.6.1 (for us) but not the latest iPadOS 18 public beta...

Hello, I'm getting started for my project with Xcode Cloud since I upgraded to the macOS Sequioa Beta and Xcode 16 now refuses to archive builds for TestFlight. Somewhere very late in the build process I get the following error: realitytool requires Metal for this operation and it is not available in this build environment The log says this happens at: Compile Skybox urban.skybox My project uses RealityKit. How can I fix this issue? Thanks!

My workflow has been running tests on iOS 15, 16 and 17 for a long time now, but suddenly it started to fail for iOS 15 and 16. The error does not seem to be code related, since it is a Xcode Cloud failure saying: "Failed to download iOS 16.1 simulator runtime". The exact same issue is showing for iOS 15. It works as expected on iOS 17. I have also reported this in the Feedback Assistant: FB14855036 If someone knows a work-around for this issue, I'd be happy to hear about it!

Since August 27th 2024 Xcode Cloud fails to clone our Github repository. The reported error is LFS related: "smudge filter lfs failed" Nothing in our repository configuration has changed and the LFS files have been in place for a long time. Has anyone else encountered this issue and found a solution? Feedback: FB14975627

I have an inconsistent Xcode Cloud failure that I'm hoping to learn more about? Additional context is available in Apple Support case 102378073626 and Feedback Assistant FB13769150. Every 3 months, ~half of my project's Xcode Cloud builds will fail for a few days in a row. I usually file a support request with Apple, they fix something on their end, builds succeed, and then exhibit the same failures again in 3 months. I'm hoping to learn anything that y'all can share about: Why does this happen? Does it coincide with new macOS versions being deployed onto Xcode Cloud? What did Apple do to fix it each time? Is there anything I can change about my project to make the failure less likely? (Such as putting a delay between the clone, brew install, and pod install steps that all hammer GitHub?) Specific symptoms: Xcode Cloud builds will fail after receiving an HTTP 502 from GitHub. This usually happens when it attempts to clone a repo, brew install, or pod install. One example: [!] Error installing FirebaseSessions [!] /usr/bin/git clone https://github.com/firebase/firebase-ios-sdk.git /Volumes/workspace/tmp/d20240809-12044-znknw7 --template= --single-branch --depth 1 --branch CocoaPods-10.28.0 Cloning into '/Volumes/workspace/tmp/d20240809-12044-znknw7'... error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected flush after ref listing Error Command exited with non-zero exit-code: 1

Hi, I am using Xcode Cloud to build our app, and our app has the cocoapods dependency NMapsMap(Korean map library from Naver inc.). https://navermaps.github.io/ios-map-sdk/guide-en/ The library uses git-lfs to download its data for the map, however it keeps failing and retrying 3 times to download with this error(and finally fails) Showing All Messages [!] Error installing NMapsGeometry [!] /usr/bin/curl -f -L -o /Volumes/workspace/tmp/d20240826-7482-5cn94o/file.zip https://repository.map.naver.com/archive/pod/NMapsGeometry/1.0.2/NMapsGeometry.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.15.2 cocoapods-downloader/2.1' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com Warning: Problem : timeout. Will retry in 1 seconds. 2 retries left. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com Warning: Problem : timeout. Will retry in 2 seconds. 1 retries left. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: repository.map.naver.com My ci_post_clone.sh file is here, and doesn't seem to have something to be wrong. export HOMEBREW_NO_INSTALL_CLEANUP=1 brew install cocoapods pod install The issue could be DNS server issue between Apple Xcode Cloud servers and Naver repositories server, so I also posted to the Naver cloud forum. Please help for this issue, and hope the build can resolve the host soon. Nowadays I manually build and distribute the codes in manual...

We have a cross platform app that we build with Xcode Cloud and distribute via TestFlight. We want to test builds with the Xcode Beta. So we have the following build environment: Xcode version: Xcode 16 beta 6 (16A5230g) macOS Version: macOS Sonoma 14.5 (23F79) Everything builds and submits to TestFlight fine. The App runs fine on iOS 18 beta and macOS 15 beta. But when attempting to install via TestFlight and launch the App on macOS 14..6.1 it crashes immediately with what appears to be a missing Foundation symbol. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace DYLD, Code 4 Symbol missing Symbol not found: _$s10Foundation14NSDecimalRoundyySpySo0B0aG_SPyADGSiSo14NSRoundingModeVtF Referenced from: <CBEBC813-C7B6-3D8E-BE62-16F2EFFEB1FE> /Applications/MyApp.app/Contents/MacOS/MyApp Expected in: <2F87A303-430F-3EA5-9492-3033F4FEE64B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (terminated at launch; ignore backtrace) Thread 0 Crashed: 0 dyld 0x7ff8139f687a __abort_with_payload + 10 1 dyld 0x7ff813a0f7f7 abort_with_payload_wrapper_internal + 82 2 dyld 0x7ff813a0f829 abort_with_payload + 9 3 dyld 0x7ff81399c2b5 dyld4::halt(char const*, dyld4::StructuredError const*) + 335 4 dyld 0x7ff8139994bd dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 4099 5 dyld 0x7ff8139982e4 start + 1812 Is it expected that this should work? Is this a known issue? Is there any workaround for it? Should I file feedback or a DTS?

For the last hour or so, builds to TestFlight from our Xcode Cloud workflow are sitting in the "TestFlight Internal Testing - iOS" step with no log messages... Normally this step is pretty quick, but it's as if something is hanging there. This seems to affect multiple branches (we use GitHub). Is something hosed on the TestFlight side/anyone else experiencing this? Edit ah shortly after I posted this it finished :face-palm:. Perhaps this was related to the Xcode Cloud outage earlier

Since we integrated xcode cloud into our project, workflows fail randomly when resolving dependencies from cocoapods (specifically when fetching the repo from github). The error is a 502 so seems like server side, and if we rebuild is usually goes away but we have to be constantly rebuilding failing workflows, loosing minutes and dev time instead of having it automated as we wanted. Any ideas?

When I click "Register," this error appears. How can I allow Xcode Cloud to access a self-managed GitLab? Do I need to configure the GitLab server?

I am part of a personal team where I have admin credentials. The account holder created a workflow when initializing Xcode Cloud but I can't see it in my App Store Connect. So I tried to create another workflow but when I do, I get the error "User does not exist". This is very annoying for us.

Having an issue today where archives on Xcode Cloud are failing at the Code Signing step. The error reported by Xcode Cloud has been one of the 2 following: 502 error from developerservices2.apple.com Unexpected character 'u' (I assume this is in some way related to the HTTP failure above, but please correct me if I'm wrong) Sometimes they even appear together, with the HTTP error as a warning and the unexpected character as the error I assume this is some kind of Xcode Cloud / developer tools outage. I saw another post on the forum from 3 weeks ago that reported the same errors coming from Xcode Cloud. I also saw that there is a "Resolved Outage" with Xcode Cloud from 8/19 (maybe that is related)? Has anyone found a way around this? Any updates on when this will be resolved? It has been happening for us consistently since the first Xcode Cloud archive that we ran today (around 10AM EDT).

I am using Xcode Cloud to build my Mac Catalyst app for Developer ID Distribution as a DMG package that must be codesigned and notarized. I have a ci_post_xcodebuild.sh script that runs after the Archive action. This needs to perform the following tasks: Produce a DMG from the provided exported archive located at CI_DEVELOPER_ID_SIGNED_APP_PATH Codesign that DMG using the same certificate identity that Xcode Cloud used when automatic code signing the exported archive using cloud signing. Notarize that code signed dmg with the notary service Generate a Sparkle appcast.xml file Upload the DMG and appcast.xml file to s3 The issue I am having is that I do not have access to the cloud signing keychain identity that Xcode Cloud uses to automatically codesign the exported archive. I check for identities and none are found. Running: security find-identity -v -p codesigning There are no code signing identities available. Make sure you have a "Developer ID (Application)" certificate (with the private key) installed on your Mac with Keychain Access. How can I access the cloud signing identity in this script so I can sign my DMG file before notarizing it? I am currently experimenting with installing my own certificate in the build server keychain and run my own archive + export commands after the Build action completes. This is not ideal. Thanks, Andrew

I have registered a webhook URL but for every event triggered, my webhook URL does not receive any POST request. In my App Store Connect Xcode Cloud > Webhook Setting, I can see all the webhook failed to send, they all returned `Unexpected response code for CONNECT: 403 ` I tried testing my webhook URL from Postman, it works fine, but not from Xcode Cloud Webhook.