Search results for

xcode github

94,706 results found

Post

Replies

Boosts

Views

Activity

Reply to Cannot register the product
I've been getting this exact same problem, I'm enrolled, have used xcode cloud on other projects I setup fine with no problems. I have created a new project in Xcode, connected it to my GIT account, verified that it exists on GitHub, pushed updates to it via Xcode, and setup an App Store Connect entry for it. The project is define in Aoo Store Connect. When I try to add Xcode Cloud from Xcode, I get to the step to grant access, it launched App Store Connect, but says it can't find the repository - Repository was not found. Either the repository does not exist or you do not have permission to access it. Learn More. I have the correct git account setup in Xcode, and it shows up fine when I get to teh gran access screen in Xcode for setting up a new xcode cloud workflow, but I still get the above error. As the owner of the GitRepo, what permission do I need to manually add in GitHub if I do NOT want to make my repo public?
Dec ’24
Reply to Dictionary Wrapper for Custom Types
How are you testing this? I copied your code into a new test project (created from the OS X > Command Line Tool template) and it worked just fine.k: 2, v: Green k: 3, v: Blue k: 1, v: Red Program ended with exit code: 0This is with Xcode 7.0 on OS X 10.10.5.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Programming Languages SubTopic: Swift Tags:
Oct ’15
Xcodebuild Archive fails to errSecInternalComponent in GitHub Action
Hi! I have an issue to build Archive when using xcodebuild in GitHub Action workflow. The project s quite basic iOS project. Archiving works fine locally using command xcodebuild -quiet -workspace MyProject.xcworkspace -scheme MyProject Release clean archive -configuration release -destination=generic/platform=iOS -archivePath MyProject.xcarchive Same command via SSH gives an error errSecInternalComponent. Command CodeSign failed with a nonzero exit code IF I run a command security unlock-keychain beforehand, then creating .xcarchive passes. In Keychain Access, I have necessary certificates. Those are located in login.keychain and every certificate seems to be valid. Also, based on this answer, I have tried to put 6 different Apple Worldwide Developer Relations Certification Authority -certs in System.keychain and removed same stuff from login.keychain. This didn't bring solution either. Our GitHub (Enterprise) Action workflow is quite simple (here is an extract): name: Build_Tests on: push:
4
0
3.3k
Oct ’22
🤔 GitHub tensorflow macOS alpha had better performance on M1?
Hello, I noticed a substantial decrease in performance compared to previous releases of tensorflow for M1 Macs. I previously installed the alpha release of tensorflow for M1 from GitHub, found here: https://github.com/apple/tensorflow_macos and was very impressed by the performance. I used the following script to benchmark my M1 Mac and other systems: https://gist.github.com/tampapath/662aca8cd0ef6790ade1bf3c23fe611a#file-fashin_mnist-py Running the alpha release from GitHub, my M1 Mac handsomely outperformed both google colab's random GPU offerings and an RTX 2070 windows computer. Recently, I went back to the GitHub repository, looking for new updates on tensorflow support for the M1 and was redirected here to the tensorflow-metal PluggableDevices installation guide: https://developer.apple.com/metal/tensorflow-plugin/ After installing the conda environment and running the same benchmark script, I realized my M1 systems's was running much slower. Additionally, the following error
7
0
4.1k
Aug ’21
Reply to Xcode 9: Symbol not found: _utimensat
Apparently you have to have the XCode command-line tools installed to get this running. I found a Github Issue with some comments. First I deleted rbenv (I'm running brew) and then I ran xcode-select --install to install the command-line tools. Once done I reinstalled rbenv and was able to rbenv install 2.3.0 fine after that.
Sep ’17