i also have the same error in Xcode Version 16.0 (16A242d).
Post
Replies
Boosts
Views
Activity
Managed to finally solve this issue with adding one "dummy" repository from github and then access the settings in "User and access" section.
The only question now remains is how to use one git source for 2 projects (one is on different company, one is for staging builds, the other one is for production)?
I still have a problem with connecting back to our Gitlab, is there any update on this?
On appstore connect on xcode cloud tab I cannot select new SCM and I cannot create new application in Gitlab as I do not have redirect URI.
Still a problem for me, I get
Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method. in our gitlab. We also tried this [https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/3947#note_155251805) workaround, but nothing works.
Looks like the fault is in AppDelegate where we added some delay on app startup so local DB can finish up deleting obsolete data. With no delay in AppDelegate previews are working ok.
A bit strange that AppDelegate affects SwiftUI previews.
Now this is getting funny... I cannot remove old SCM and I cannot register new one.
I was searching a bit on internet and found this: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/3947#note_155251805
I do not have admin access to our gitlab, but can anyone with same problem try and confirm solution?
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'm currently on 13.2.1 release Xcode version and getting needs -Onone Swift optimization level to use previews. On many SwifUI views with previews canvas doesn't even open. This makes my work on any SwiftUI project right now a big pain. :(
I solved my issues in imported pods to raise iOS version for each target and pod to min 13.0 and also removed arm64 from excluded architecture. This is important on new M1 macs as you cannot run on simulator if you do not have arm64 architecture in build.
Ok I think I have found a problem inside my project:
some of the targets had excluded arm64 architecture so I removed that. Also update any cocoapods you have, we had some before that has set arm64 as excluded architecture, but now there is none that has that setting, so coverage is working.
Same issue on M1 mini, Xcode 12.5 release version. :(
I have similar problem on new mac mini M1, when I tap onto textField and software keyboard should come up, but it doesn't. Funny thing is that same test is working on Intel mac with no problem and I also have disabled hardware keyboard in simulator.
To add more funny things, if I erase simulator first of tests will always work, but next one or on repeated run it is a lottery.
Should we make bug ticket for Apple? I think this is something wrong on simulator on M1 macs.
Well I have same problem in new Xcode 12 beta3.
I cannot debug ui tests now and it seems I will have to revert back to beta2?