Problem connecting Xcode Cloud with GitLab Self-Managed

I am having the same problem. Is there any way to reset everything and start from scratch?

I am facing the same problem. Is there a way I can reconfigure it?

i have the same problem with gitlab self-managed. Is there any way to reset everything and start from scratch?

still nothing new here?

Same situation with our instance. Did anyone has any progress ?

If you are experiencing this problem, you will need to un-register your self-hosted SCM by going to:

App Store Connect Users and Access Xcode Cloud Integrations

You should see your GitLab self-hosted installation listed there. Click the 'Deregister' button.

From there, you can re-register your SCM in a couple of ways:

1. On your builds page in App Store Connect, you should see an error banner with a button that says 'Reconnect'. That should take you through the process of re-installing the GitLab app onto your SCM. If you don't see the error banner, run another build, and the banner should then appear
2. If your app is not yet onboarded, you can go through the onboarding process, which will include the same registration process as in #1.

I am unable to deregister from Users and Access -> Xcode Cloud integration, since there is nothing there other than telling me to create a new workspace (PFB).

I was able to connect first time. Then I had to change my change my project with a separate self-hosted gitlab instance. That time I removed my xcode cloud data using this url, https://developer.apple.com/documentation/xcode/removing-your-project-from-xcode-cloud. Ever since I am keep getting the 2nd step of gitlab authorization only (PFB).

Please help. I cannot proceed with my CI/CD setup because of this issue. Also, I have multiple apple developers account linked to same email. Will Xcode Cloud integration work for all the accounts?

I'm facing the exact same issue here, any updates on this?

Any update?

Xcode Cloud seems to persist the application client ID created by Gitlab in the first step. But if the second step failed, the failed installation won't be listed in the Xcode Cloud page, and the application client ID will not expire, so we can't find a way to reset the installation.

Now Xcode 14.1 keeps promoting Xcode Cloud but I still can't create any workflow after my first attempt half year ago. Please help.

I had a very similar issue trying to change which account was used to authenticate gitlab to our existing app and workflows. There was no clear solution to the problem but I basically tried these steps over and over, while also trying to run a workflow.

• Remove the app from my personal gitlab profile
• Remove the integration to gitlab from Users & Access
• Add the integration from Users & Access with the new account (creating the app in gitlab)
• In one of the workflows I had already configured, adding a new primary repository, which is just the same link
• Make sure every workflow is using that "new" primary repository
• Delete the old primary repository from the xcode cloud settings for my app

Eventually it worked, not really sure which one of those steps did it

The solution above doesn't work for me because I don't have any integrations listed under Users & Access -> Xcode Cloud, I can only see the setup-your-first-workflow screen. So I am still being redirected to step 2 of the onboarding when I try to setup the first workflow from Xcode. I really would like to give Xcode Cloud a try but I am afraid I have to look into other CI/CD solutions.

I have exact same problem and there is still no solution? I mean, a company where I help on project is paying for xcode cloud and we cannot use it. This is dragging for more than one month already!

Please give us some information or something, I have to report to my client what is going on!!!

I have exact same problem and there is still no solution?

I had problems with created application on gitlab, Xcode was telling "you need admin permission to the repository" so I could not complete the integration. After deleting gitlab application I also have same issue.