At the current site, circleCI moves at the timing when it is committed to the develop branch, Fastlane moves, and it is uploaded to deployGate. When I renewed the certificate, for some reason fastlane crashed with ʻExit status: 65`.
When I sshed to CircleCI and looked at the log, it seemed that the codesign was down with a ʻerrsec internal component` error.
Double-click the target private key in the keychain app → Access control → Add / usr / bin / codesign and xcode to the always allowed list.
Reference: https://qiita.com/sekitaka_1214/items/61d68d603ee1c1b7adf1
Connect to CircleCI with ssh and hit the ↓ command.
security unlock-keychain login.keychain
See also: https://stackoverflow.com/questions/24023639/xcode-command-usr-bin-codesign-failed-with-exit-code-1-errsecinternalcomponen
These two did not solve the problem. ..
As a result of various thoughts, it seems that the new certificate has changed from the old certificate and the intermediate certificate (Apple Worldwide Developer Relations Certification), and the problem was that CircleCI could not read the new intermediate certificate.
base64 -i (intermediate certificate) | pbcopy
(This time, I set it as APPLE_RELATION_CERT.)yml:.circleci/config.yml
- run:
name: Decode releation certificates
command: base64 -D -o AppleWWDRCAG3.cer \<<< $APPLE_RELATION_CERT
fastlane/Fastlane
import_certificate(
keychain_name: ENV["MATCH_KEYCHAIN_NAME"],
keychain_password: ENV["MATCH_KEYCHAIN_PASSWORD"],
certificate_path: 'AppleWWDRCAG3.cer',
certificate_password: ''
)
This worked!
I got stuck in this bug for a whole day. .. If anyone knows how CircleCI or fastlane can read the new intermediate certificate, please let me know (> _ <)
I did my best to deal with this, so please LGTM if you like ᕦ (ò_óˇ) ᕤ
Recommended Posts