-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build issue beginning in v3.4.0 potentially related to added build target #241
Comments
Deleting the |
This looks a lot like #231. Do you mind reading through it? |
It does look like it's the same issue. In my case, I'm using GitHub Actions to build and deploy to TestFlight, using a provisioning profile stored as a GitHub Actions variable. Adding a privacy manifest file to my app, as described here, had no effect. Adding
Trying to set the provisioning profile to "Automatic" wasn't successful. I haven't been very successful at trying to pin to v3.3.0 as a workaround; the Thanks in advance for any help & suggestions! |
I'm going to suggest that you take this to the Apple Developer Forums. This appears to be an issue with the way Xcode handles packages with resources, but we do require them here. |
No luck tracking down the root of the problem. But for posterity, in case someone runs into this or a similar issue in the future, the issue seems to be in using GitHub Actions to build, archive, sign, and push to TestFlight. The previous setup followed the documented GitHub Actions Xcode setup: https://docs.github.com/en/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development Eliminating GitHub Actions in favor of Xcode Cloud allowed Xcode to be set to |
New Issue Checklist
main
branch)Expected behavior
I am using a library that has a dependency on
swift-crypto
.xcodebuild
started failing in CI/CD after an automatic dependency update toswift-crypto v3.4.0
. Expected behavior: the build should succeed. 😃 This looks like it may be the same issue as #235 but I'm not sure.Actual behavior
The app builds locally. In CI/CD with GitHub Actions publishing to TestFlight, there is a build error:
error: Signing for "swift-crypto_Crypto" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'swift-crypto_Crypto' from project 'swift-crypto')
Steps to reproduce
In a brand-new Xcode project, add
swift-crypto
as a dependency, specifyingv3.3.0
. Then, runxcodebuild build
.Using `swift-crypto v3.3.0:
Using
swift-crypto v3.4.0
:Details
Terminal output from
xcodebuild build
usingswift-crypto v3.3.0
:Terminal output from
xcodebuild build
usingswift-crypto v3.4.0
:The text was updated successfully, but these errors were encountered: