Couldn't creating a new certificate about cert HOT 13 CLOSED

I'm having the same problem. I managed to get it to work by executing:
cert -k ~/Library/Keychains/login.keychain
Alternatively it seems you could use the CERT_KEYCHAIN_PATH environment variable.
What would be the best fix for this, setting a default value in options.rb?

from cert.

@siemensikkema It works, but am I missing something so I need additional parameter?

from cert.

I'm not sure what's the reason. I'm also just figuring this stuff out as I go along! :)

from cert.

I can confirm this as well. It appears that it doesn't specify a proper default keychain directory when used vanilla. @siemensikkema's method worked.

Update: Looks like ruby -e "puts #{Dir.home}" prints nothing while ruby -e "puts 'e'" does print e. So maybe that line of code in the keychain_importer line 5 resolves to nil?

from cert.

Same problem here.

from cert.

The default value is "#{Dir.home}/Library/Keychains/login.keychain", do you run cert on some kind of CI which doesn't set the HOME environment variable?

from cert.

I have reverted my workaround (setting the "CERT_KEYCHAIN_PATH" in .env) and tested again. cert works fine now! I don't know what did the trick. I have updated fastlane and my shell (zsh) since. The HOME environment variable is set correctly.

from cert.

hey, i am running from a ci machine. what changes do i need to make?

from cert.

@shoshRose You have to set the environment variable CERT_KEYCHAIN_PATH

from cert.

@KrauseFx thnx

from cert.

started getting this again:
Certificate XXX (YYY, Inc.) can't be found on your local computer
i have the keychain path set

from cert.

shoshRose Can you please open a new issue with the details of your setup?

from cert.

This issue was migrated to fastlane/fastlane#3102. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from cert.