Command-line signing fails while signing from Xcode succeed

Question

Created Mar ’21

Replies 1

Boosts 0

Views 1k

Participants 2

Hi,

I'm currently trying to build my project from command line using Jenkins automation.

However, although both methods are using the same code sign parameters, the UI based signing (from Xcode) succeed and when running from xcodebuild it fails for the reason below :

Code Block     /usr/bin/codesign --force --sign <my_cert_id> --timestamp\=none /Users/bla/file.dylib

and the result is :

Code Block Warning: unable to build chain to self-signed root for signer "Apple Development: userBuilder (...)"
/Users/bla/file.dylib: errSecInternalComponent

But the same command runs successfully when being invoked from Xcode. My questions are

Do the certificate+private key are taken from the keychain in both cases ?
Are there are environment variables that may exist only in the Xcode mode ?

thanks

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’21

I'm currently trying to build my project from command line using
Jenkins automation.

My general recommendation here is:

Get things working in Xcode (which you’ve already done).
Then convert that to command-line signing in Terminal (specifically, on the same Mac, and with the same user account, as you’re using for Xcode).
Finally convert that to your CI system.

The advantage of doing step 2 is that it confirms that the problem you’re having is not with command-line signing per se but rather with your CI system. You can then escalate this via the support channel for your CI system.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0