Posts

Post not yet marked as solved
0 Replies
144 Views
Since I upgraded to macOS 13 beta. I was unable to use Xcode 13, and had to try Xcode Cloud. My project uses CocoaPods for dependency management. We have a lot of private dependencies hosted on GitHub. But in the process of using it, I found some problems: I found that AppStoreConnect has no way to manually add access to the "other repositories". I had to rely on Xcode Cloud to automatically detect the missing repositories each time a run failed, and then I had to manually click to add access, which was very annoying. Xcode Cloud does not pre-install CocoaPods. nor does it initialize Homebrew (it just installs it). This causes me to run brew install cocoapods every time, and wait for 10 minutes. Xcode Cloud has no way to specify a cache directory. Users may need to install some additional tools needed to compile, and they rarely change, so if the cache could be used, it would not have to be downloaded and installed every time, speeding up the execution process and not wasting valuable computing resources. Suggestions: pre-install CocoaPods. Many people use CocoaPods as their dependency management tool Provide the ability for users to manually add access to "other repositories" in the AppStoreConnect backend, instead of just relying on automatic detection. Add custom cache directories, which can save a lot of execution time
Posted Last updated
.