Hello, Has anyone used Sentry with Xcode Cloud? How are you uploading dSYM files? One way is fastlane but Xcode Cloud doesn't come with Fastlane preinstalled, the other is sentry-cli but the same issue, it's not preinstalled.

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.

Hi, Overview I am using Xcode Cloud for my multi platform app. The macOS test case fails, however the iOS test case runs and succeeds. I don't have any UI test cases written, the test case are simple and have nothing platform (macOS) specific. Questions What can I do to fix this? Is there any user privileges needed to launch the macOS app for testing? I ask because when I ran the UI tests locally it launched the app and asked for my macOS user password. Just wondering if that is the reason it didn't launch in Xcode Cloud. Error: <Appname> encountered an error (Failed to install or launch the test runner. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult.(Underlying Error: Could not launch "AppnameTests. The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed) ))) × Could not launch "<Appname>" × Could not launch "AppnameTests" × AppnameUITests.testExample() Failed to get launch progress for <XCUIApplicationImpl: 0x600000564630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.app>: Could not launch "app name". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed)) AppnameUITests.swift:28 * AppnameUITests.testLaunchPerformance) Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/TestProducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed. (Underlying Error: Launch job spawn failed)) AppnameUITests.swift:37 g * AppnameUITestsLaunchTests.testLaunch) Failed to get launch progress for «XCUIApplicationimpl: 0x60000054630 <BundleID> at /Volumes/workspace/Testroducts/Debug-Dev/<Appname>.apps: Could not launch "<Appname>". The LaunchServices launcher has returned an error. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn't be completed. Launch failed.

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?

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally. So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly? You can find a detailed instruction how server is launched on a github page I provided.

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!

I'm running on xcode 16, the project archives just fine on the local machine. However, with xcodecloud. It's running into exist code 70 on the following command xcodebuild -exportArchive -archivePath ..... #output Showing All Errors Only Build Archive Export archive for ad-hoc distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for development distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70 Export archive for app-store distribution Command exited with non-zero exit-code: 70 Command exited with non-zero exit-code: 70

Hi, Our team uses Xcode Cloud to run unit tests, and since around November, we’ve been frequently experiencing timeouts with the following type of process: @Test func hogeTest() async { // do something hoge.do() // wait until done await wait(condition: { hoge.isDone }) // test result #expect(hoge.isSucceeded) } private func wait(condition: () async -> Bool, timeout: TimeInterval = 0.5, pollingInterval: TimeInterval = 0.01) async throws { let deadline = Date().addingTimeInterval(timeout) while Date() < deadline { if await condition() { return } try await Task.sleep(nanoseconds: UInt64(round(pollingInterval * TimeInterval(NSEC_PER_SEC)))) } Issue.record("timeout") } Although sleep is supposed to wait for only a few milliseconds, there are cases where it takes more than 10 seconds, leading to a timeout. What could be causing this instability in the sleep duration? Additionally, if there are other recommended ways to implement polling and waiting in Swift Testing, I would appreciate it if you could share them. A feedback report (FB15899163) has already been submitted. Best regards,

There was an updated tonight I assume to something and now I am getting this for all firebase modules when I push to App Store connect "Invalid sdk value. The value provided for the sdk portion of LC_BUILD_VERSION in proxie2.app/Frameworks/GoogleAppMeasurementIdentitySupport.framework/GoogleAppMeasurementIdentitySupport is 18.2 which is greater than the maximum allowed value of 18.1." now even when I revert back to suer old firebase packages I get the same errors no matter what please fix this asap...

My builds failed today with this error: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The thing is, I have Xcode Cloud configured to use the latest release. There is a separate configuration for "Latest beta or release", so why is it using the Xcode 16.2 Beta 3 build? This is clearly a beta. If you're going to give me an option to use the latest release, then it should do what it says.

I am experiencing a lot of problems with Xcode Cloud in last days. I can't hardly login, refresh time is so high, showing blank pages or not found all the time. Anyone else is experiencing the same?

The build status has a green check in Xcode Cloud, but TestFlight see no builds and suggest that I submit one. Then it provides a link to an incredibly unhelpful list of upload tools, at least one of which suggests creating a developer account!!!

Hello everyone! I found that the Xcode Cloud workflows under my project are completely stuck. The tasks that are already running cannot be completed. Newly started tasks remain in the queued state forever and cannot be canceled. They are consuming my usage quota 😢. Has anyone else encountered the same issue?

All our builds getting stuck on the que. https://developer.apple.com/system-status/ is not showing xcode cloud as down.

Hello, when I open the "Cloud" tab in the Report navigator, it shows "Failed to analyze workspace" and I cannot do anything. I can't start a build, nor can I manage or create workflows. All options are greyed out. When loading the project, in Console I see the following errors from Xcode: fault 11:07:19.805349+0100 Xcode ❌❌❌ Assertion failure #0 in <private> error 11:07:19.816641+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48 1 XcodeCloudKit 0x00000001192583c4 $s13XcodeCloudKit26ShellBasedProjectDescriberPAAE17describePublishery7Combine03AnyI0Vy6OutputQzs5Error_pG5InputQzFAKs5Int32V_10Foundation4DataVARtcfU_AA021AllArchivableProductsdG0V_Tg5 + 2012 2 XcodeCloudKit 0x000000011925ec90 $ss5Int32V10Foundation4DataVAE7Combine12AnyPublisherVy6Output13XcodeCloudKit26ShellBasedProjectDescriberPQzs5Error_pGIegyggo_AB8exitCode_AE6stdoutAE6stderrtAOIegnr_AjKRzlTRAJ021AllArchivableProductskN0V_TG5TA + 40 3 Combine 0x00000001a072351c $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2009FAF507AE039LLC7receiveyAA11SubscribersO6DemandV6OutputQy_F + 300 4 Combine 0x00000001a0725128 $s7Combine10PublishersO7FlatMapV5Outer33_E91C3F00A6DFAAFEA2<…> << fault 11:07:19.822299+0100 Xcode ❌❌❌ Assertion failure #0 in <private> fault 11:07:19.822405+0100 Xcode ❌❌❌ Assertion failure #0 in <private> error 11:07:19.824577+0100 Xcode ❌❌❌ Assertion backtrace: >><private>0 XcodeCloudKit 0x00000001195309d8 $s13XcodeCloudKit17AssertionHandlingPAAE16logFullBacktraceyyFAA0D0O7HandlerV_Tg5Tf4d_n + 48 1 XcodeCloudKit 0x00000001195e088c $s13XcodeCloudKit17DiscoveredProductO16DescriptorsCacheC13updatePlanner11environmentyAA21DeploymentEnvironmentO_tFys6ResultOySayAC0E10DescriptorVGs5Error_pGcfU_ + 740 2 XcodeCloudKit 0x0000000119289fa8 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7SchemasO13BuildArtifactVGsAQ_pG_Tg5Tm + 68 3 XcodeCloudKit 0x00000001192a1ef4 $s7Combine9PublisherP13XcodeCloudKitE18sinkAtMostOneValue4file4line6resultAA14AnyCancellableCs12StaticStringV_Suys6ResultOy6OutputQzs5Error_pGctFyAA11SubscribersO10CompletionOy_sAQ_pGcfU0_AA0nB0VySay0cD3API10ComponentsO7Sc<…> << Obtained by filtering by xcode-cloud-assertion category. Is there anything I can do to fix this? Thanks!

Issue Description I'm have Local Swift Package which contains binary target to private github releases url is formed like below: https://api.github.com/repo/{owner}/{repo}/releases/assets/{asset_id}.zip I register the private repo to the xcodecloud, but still xcodecloud does not recognize "api.github.com" domain. So build keeps fails at downloading binary artifact. https://github.com/{owner}/{repo}/releases/download/{tag}/Myframework.xcframework.zip is not a valid choice since this kind of url, is not supported for private repository. Proposed Solution Please add authorization to the "api.github.com" like normal "github.com".

Build's are queued for 1 hour+ and System Status page is not showing any issues: https://developer.apple.com/system-status/

Hello, im trying to configure my Gitlab Community Edition Instance for Xcode Cloud, but it always fails that Xcode Cloud is not able to find the repository. I have tried different things. Also tried with the admin user. The rights are also matching (Scopes: api, read_user, , read_repository). And I’m also the owner of the repository. Then I have looked into the logs of the GitLab instance and noticed something weird: 127.0.0.1 - - [11/Dec/2024:22:19:58 +0100] "GET /api/v4/projects HTTP/1.1" 200 1590 "" "Xcode Cloud" 7.56 127.0.0.1 - - [11/Dec/2024:22:19:58 +0100] "GET /api/v3/meta HTTP/1.1" 410 62 "" "Xcode Cloud" - 127.0.0.1 - - [11/Dec/2024:22:19:58 +0100] "GET /api/v4/projects HTTP/1.1" 200 1590 "" "Xcode Cloud" 7.56 Like the first and third api call makes sense. Trying to fetch the projects and is also successful (status code 200). But then I see Xcode Cloud is trying to access another API, which seems to be from GitHub. At some other location in the log I have seen a API call from Bitbucket. So why does Xcode cloud tries to call APIs from other providers, when I have selected the GitLab one at the configuration? Is this a bug or is this intended? Have tried now many things and I have absolutely no idea what the problem is, because Xcode cloud is also not giving really detailed logs about the errors.

Hi folks, I've been having this issue for the last few months, where Xcode Cloud fails to resolve Swift package dependencies while compiling my builds, seemingly at random. Some of my Xcode Cloud builds will fail after several minutes, with an error log looking like that : xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://dl.google.com/firebase/ios/bin/grpc/1.62.2/rc0/grpcpp.zip' which is required by binary target 'grpcpp': downloadError("The request timed out.") Whenever this happens, I have to manually restart an Xcode Cloud build process (or several builds, since the error can happen multiple times in a row), to the point it's becoming increasingly painful to rely on Xcode Cloud for my workflow. The failing packages are mostly random (meaning, it's not always the same one that Xcode fails to resolve), but they are always publicly accessible, even though I have an environment variable set in my Xcode workflows to retrieve a single Github private dependency (maybe this has some kind of importance). Could anyone tell me if this is an isolated issue, or if I could do anything on my end to resolve this ? Thank you !