“xcode github”

For those that may see this in the future, I found a great open-source iOS lockdown browser SEB/Safe Exam Browser. I have used the macOS version of SEB in the past and this GitHub URL has the SEB unified macOS/iOS/iPadOS code. This has the ingredients of being a great working example to learn from. (https://github.com/SafeExamBrowser/seb-mac) Also for SEB I ended up utilizing the below agent string for the site I was locking down: Mozilla/5.0 (iPad; CPU OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/17.0 Mobile/11D257 Safari/9537.53

One of the root causes of the issue is missing files in runtime which were used in the build. Description: I ran into this issue when I was running the app via XCode on Mac but the code was accessing files from GitHub. Solution: I pulled the entire package on the local Mac repository and re-ran the app, It worked. Root Cause: As the execution engine was fetching the files from Github in real-time, perhaps that is why the simulator was timed out

Create a new playground (menu New in Xcode) and give the name you want.you should see Hello world in the code part as well as on the right.now type below a statement, likelet x = 10print(I entered , x)you should see 10 on the right, in front of the lineand I entered 10 in the log part at bottom.Now, you’re up and running.good luck

The exact problem rookuuu has happens when I attempt to build in my CI pipeline with the exact same provisioning profile and key. Specifically GitHub Actions + GitHub-Hosted Runners using GitHub instructions for installing profiles. Sounds like we're in the same boat. However, I think I've found the solution. When you run xcodebuild, if it picks up a provisioning profile with the extension .mobileprovision, even though the target is macOS it runs the provisioning profile validation steps as if it was iOS. Raising the iOS specific errors about App Groups. I followed the same document which similarly mislead me into changing the file extension away from .provisionprofile, simply renaming them back in the example workflow did the trick for me. Hopefully it does for you also. I've had the GitHub docs updated to include a note that reflects this, but this is probably also an Xcode bug that it's trusting the extension of the profile over the build target?

I was able to resolve this issue by navigating to the Xcode Cloud Settings in AppStoreConnect and manually re-granting permission for the repo connected through Github. You can do this through Xcode by going to Product -> Xcode Cloud -> -> Manage Repositories. Make sure that you are also signed into the account you originally setup Xcode Could with. There should be a button next to the repositories connected that says grant . Clicking this should hopefully resolve your issue.

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.

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

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.

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.

I was taking a look at the Crustacean.playground today in Xcode 9, and it needed some updates for Swift 4.0.I've uploaded my changes to github for anyone who needs them:https://github.com/Krishna/Crustacean---Protocol-Oriented-Programming-in-Swift

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.

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

Same experience. Github account in place in preferences. When add packages invoked Apple Swift Packages shows up under collections and GitHub shows up under Source Control Accounts. Swift Packages are visible but nothing when GitHub clicked and nothing when known GitHub package is searched for.