“xcode github”

Same issue for me! To add insult to injury if you create a brand new Xcode project and try to add ANY package from Github the process hangs immediately on Preparing to validate Come on Apple! Are you for real?

And I thought I'm going crazy. Same story here, M4 Mac mini with Xcode 16.2, MacOS 15.3.2 (24D81). Using github pipelines and fastlane for iOS builds and distribution to TestFligh.

Had the exact same issue for In House (Enterprise) signed apps that was built using Xcode 12.4 on Appcenter / GitHub actions. I only updated the builds to use Xcode 12.5.1 and the apps are running now on iOS 15. Did not need to renew the provisioning profiles.

I'm encountering an issue while trying to build my iOS app in Xcode for the simulator. Issue: Xcode Version: 15.x macOS Version: 14.x (Sonoma) Simulator: iPhone 16 Pro Error Message: Command ClangStatCache failed with a nonzero exit code Steps Taken: Cleaned build folder (Shift + Cmd + K) Deleted DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData) Updated Xcode and checked iOS SDK updates Disabled Clang Static Analyzer Cache None of these steps resolved the issue. Any help would be appreciated! Thanks in advance.

I had the same thing today. Suddenly, randomly, after working for years, I got asked for my github password when trying to 'Push' to the github remote - even though I use SSH rather than passwords.And when I went to preferences/accounts, my github one was grayed out, and gave the same 'Account Unavailable message as you received.I fixed it by completely reinstalling XCode - following these steps I found on the Internet:Delete /Applications/XcodeDelete all files containing com.apple.dt in ~/Library/CachesDelete all files containing com.apple.dt in ~/Library/PreferencesOpen App Store.app, download and re-install Xcode.Create the Apple ID developer accountThat worked fine for me - though other people have reported varying results.I did try just deleing the caches and preferences first, before uninstalling/reinstalling XCode - but that didn't do the trick. I had to do the full re-install thing before it would work.

After further investigation, this problem appears to be happening in iOS26.0 and fixed in the next version iOS26.1 as seen in github ShareExtensions using SLComposeServiceViewController built with Xcode 26.1 would keep crashing on iOS26.0 ShareExtensions using SLComposeServiceViewController build with Xcode 26.0 seems to work on iOS26.1

For anyone who finds this in the future: What I had to do was to go my github email settings, and uncheck Block command line pushes that expose my email. Xcode won't give you that specific of an error message, but pushing via command line will

Just built my 2nd iOS app in Xcode12b4 using this intro to SwiftUI tutorial - this is such a game changer over my 1st app in Xcode 10 years ago! Thank you for checking in assets into GitHub!

Just googled around. Ran into this blog post:http://karp.id.au/post/xcode_7_linker_rules/if I have a file that has the supported architecture on it...and if I strip out the iOS ones because Apple doesn't want us using fat libraries, I'm still prevented from building...It seems pointless to prevent me from compiling because Xcode marked all the code as iOS...even though the code is the same. Guess there must be some reason why they are choosing to do this, though it feels a bit arbitrary to prevent a perfectly working library from running on a supported architecture.Edit:I just spent 75% of a day grabbing 5 popular open source, cross platform libraries an app i'm working on uses and created Xcode projects for each of them. Kind of a chore because they are all cross platform and require certain configurations in order to compile on OS X, and a lot of platform specific code for other platforms needed to be stripped out. There's like two billion lines of code

For us we were running a CI job on a self-hosted github runner and encountered this error, signing in to xcode on the runner resolved this issue for us. Interestingly it wasn't necessary for macOS builds, only iOS.

Not many people on this forum use SDL. You have a better chance of solving your problem by asking on SDL's forums: https://discourse.libsdl.org You may also want to search GitHub for SDL Xcode project templates. Using a project template can make working with SDL in Xcode easier.

Same warning happens to me for the app that uses SumUp SDK when using Xcode 16 beta 6. Same static framework shows no warnings in Xcode 15. Created an issue for SumUp on github, but can it be Xcode 16 beta issue? https://github.com/sumup/sumup-ios-sdk/issues/150

Last post ... I promise ... When I reinstalled Xcode 26.4 again after going through all of the above shenanigans, I chose to NOT install the 26.x line of simulators, nor the Predictive Code Completion Model. As before, Xcode downloaded and installed older simulators anyway, but left the 26.x options uninstalled with their Get buttons primed and ready. I closed down Xcode and did some other stuff. After an hour I launched Xcode to check on things, opened Settings and, lo and behold, the iOS 26.4 and watchOS 26.4 simulators were showing as installed under the Platform Support section of the Components. What is going on? It's as if Xcode is hallucinating.

Yes, I managed to resolve it too by updating the runner image. Was using macos-latest as well. However, I did not specify the version code to 15.2 in Fastlane, what I did was use https://github.com/marketplace/actions/setup-xcode-version to select the Xcode version in GitHub Actions.