-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat(cli): support manual signing on build command #7769
base: main
Are you sure you want to change the base?
Conversation
Im open to any suggestions for better names for the new CLI flags as well. |
<key>${config.app.appId}</key> | ||
<string>${buildOptions.xcodeProvisioningProfile ?? ''}</string> | ||
</dict> | ||
<key>signingCertificate</key> | ||
<string>${buildOptions.xcodeSigningCertificate ?? ''}</string>`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will these be OK as empty strings, or would it fail the build?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that block is only added if signing style is manual, and if that's chosen, presumably, the developer would be supplying a provisioning profile and/or signing certificate. If what they supply is wrong (or if it's empty), then it won't work.
I believe the signing certificate can be optional, so I may push up a change to remove that key and string if the value is empty.
Honestly, they look great to me. |
closes: #7625