Following this guide (Connecting Xcode Cloud to a self-managed GitLab instance) and this thread (AppstoreConnect not accepting the GitLab application secret) with a workaround to modify the following file
./embedded/service/gitlab-rails/lib/gitlab/doorkeeper_secret_storing/token/unique_application_token.rb to remove the prefix for secret generation, seems to me more like a bug in GitLab and the workaround a bit hacky!
- Shouldn’t GitLab remove its prefix for the request again here?
- Or have we made another mistake here? Whereas we are not the only ones with the problem, it seems…
This prefix feature was implemented recently Prefixes OAuth Application Secrets with gloat (c5d6a3f5) · Commits · GitLab.org / GitLab · GitLab @nmalcolm