I have an existing project, that's hosted in a self-hosted gitlab instance. Git works through terminal just fine (and has for years!) and the Source Control Navigator pane in Xcode shows the remote repository. However when I try to setup Xcode cloud I get a warning that there's the project does not hav a remote repository. I've tried clearing derived data, cleaning the build folder, restarting to no avail. I even tried creating a new project in Xcode, and having Xcode create the remote repository (which it did successfully). But no matter what I try it will not recognize the remote repository. I've also tried adding another remote origin, and I can see it just fine in the Xcode Source Control pane, but the Xcode cloud setup does not recognize it. Any suggestions?

Hi, I'm trying to register the application with Xcode Cloud. For that, I click on the "cloud" button in Xcode. First steps goes OK, but it fails at "create App on App Store Connect" The error is Cannot register the product Usually, I change the bundle name, but this time it gets weird, as Xcode managed to create the Identifier, as it is not taken. So the identifier is created in the developer portal but it fails anyway. I also tried to create the app directly in the portal, and it works, therefore the app name is not the problem. Then I delete the app and try again with Xcode and it fails... Any solution for this issue please?

Hi there, it seems like the "Latest Release" option for Xcode Cloud's environment settings has rev'd to 16.2 (16C5032) (since yesterday?) but is causing Mac Catalyst archives to fail with the error "This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode." iOS and tvOS builds are archiving as expected, but this is blocking my deployment. I would have expected "Latest Release" to always result in a version that is accepted for deployment - am I doing something wrong? My settings for my deployment workflow are below:

I have set the deployment target to iOS17.0 on all targets. Archiving and test works fine, but External testing fails?

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 !

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.

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

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

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!

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

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?

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

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?

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.

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

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,

I just discovered that I can no longer download any artifacts from Xcode Cloud, whether from newly built workflows or previous ones. When I try to download in Xcode, it crashes immediately. When downloading from App Store Connect, it redirects to an HTML page with the following content. {"message":"You are not authorized to access this team’s resources."} I've already tried re-logging into my Apple account. Is anyone else experiencing the same issue?

Xcode cloud download archive file . the browser show "You are not authorized to access this team’s resources." All of my team can not download that. I tried downloading the files from the previous build archive, but couldn't download either

Lost access to all the build artifacts in Xcode Cloud. When I try downloading any build artifact from the web page I'm getting: {"message":"You are not authorized to access this team’s resources."} Same attempt from Xcode just crashes the app. Started to happen today or some time yesterday, after 12am EST.

In the code below, the check for the toggle value passed in my xcode. However, it failed in cloud, i.e., that value was still "0" after being tapped. func testToggle() throws { let app = XCUIApplication() app.launch() let fieldName = "MyToggle" let field = app.switches[fieldName] XCTAssertTrue(field.exists, "Field '\(fieldName)' should exist|debug = \(app.debugDescription)") let firstMatch = field.switches.firstMatch firstMatch.tap() #if FAILED_XCODE_CLOUD // Verify the toggle/switch is in the desired state XCTAssertEqual(firstMatch.value as? String, "1", "Field '\(fieldName)' should be ON|debug = \(app.debugDescription)") // "1" is On, "0" is Off #endif } In addition, I'd also like to ask why a traverse to firstMatch is needed?