Issue with "Mine" Branch Not Displaying After Switching GitHub Accounts in XcodeCloud I have been using XcodeCloud for a while. Recently, in one of my projects, I switched from using my personal GitHub account to a separate GitHub account for work purposes. Since then, when I manually start a workflow, nothing is displayed under the "Mine" section on the branch selection screen. I suspect that Xcode is attempting to list branches from the previously used account, causing branches from my new account not to appear. Where are these old account settings stored, and how can I reset them? For reference: In Xcode's Accounts settings, only the new GitHub account is present—the old account is no longer listed. The git user in the local repository has also been updated to the new one. Any assistance on how to resolve this issue would be greatly appreciated!

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?

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?

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.

Currently Im trying to save few files in it but on every run this folder is empty. I have the following script in ci_post_clone.sh mkdir ${CI_DERIVED_DATA_PATH} cd ${CI_DERIVED_DATA_PATH} ls -als touch test return 1 My expectation is that on the second run it would show test file in DerivedData or fail at creating the directory, but the issue is that this file is not created. does it need a successful build for this folder to be saved? in Xcode Cloud, in workflow environment I have unchecked Clean build Xcode Cloud will not restore derived data or caches for your builds, which may take significantly longer as a result.. One more question here would be what is meant by caches? are there other folders being saved? Also a bit of context. Im trying to build a Kotlin Multiplatform project but it fails with Showing All Issues > Could not resolve all files for configuration ':composeApp:iosArm64CompileKlibraries'. > Could not download lifecycle-viewmodel.klib (androidx.lifecycle:lifecycle-viewmodel-iosarm64:2.9.0-alpha03) > Could not get resource 'https://dl.google.com/dl/android/maven2/androidx/lifecycle/lifecycle-viewmodel-iosarm64/2.9.0-alpha03/lifecycle-viewmodel-iosarm64-2.9.0-alpha03.klib'. > Could not GET 'https://dl.google.com/dl/android/maven2/androidx/lifecycle/lifecycle-viewmodel-iosarm64/2.9.0-alpha03/lifecycle-viewmodel-iosarm64-2.9.0-alpha03.klib'. > Got socket exception during request. It might be caused by SSL misconfiguration > Connection reset by peer my guess is that Xcode Cloud or Google servers probably has some limitation. So if I cache those libraries my project will hopefuly compile once again.