I am unable to complete the Archive step for my iOS project. Looking at the logs, I see a number of messages that imply that Xcode Cloud is unable to fetch my dependencies for some reason. I have verified that I gave Xcode access to all my GitHub repositories, and it seems to be able to access my primary project repository without any problems. The type of logs I'm getting are as follows: Failed to clone repository git@github.com:myusername/MyRepositoryName.git:     Cloning into bare repository '/Volumes/workspace/DerivedData/SourcePackages/repositories/MyRepositoryName-b342b4d2'...     fatal: could not read Username for 'http://github.com': terminal prompts disabled One for each of my dependencies. Any thoughts?

Hello! I have a Swift package (SPM) with a number of tests associated with it. These all work well locally, and I have created a GitHub repository for the package that can be used by any app. I would like to set it up where my package's tests are triggered automatically whenever I push a change to a branch in the repository. Unfortunately, per the documentation, Xcode Cloud is currently unable to build and test standalone Swift packages. I hope that this will be rectified some point soon as automated testing for them seems like it'd be a pretty common and understandable use case. My question: Is there a way to set an Xcode Cloud workflow up wherein a package's tests are triggered? Xcode Cloud clearly does support Swift packages that are used when building full apps, and there is plenty of documentation to that end. But it's not clear how to trigger those package's tests even through the use of a "dummy" app without moving a bunch of tests to the app itself. Is this possible? I'd really not like to duplicate all my tests in a dummy app if at all possible. Thanks!