Could not create another certificate, reached the maximum number of available certificates about cert HOT 11 CLOSED

For distribution certificates, three is the maximum allowed it seems.

from cert.

ok thanks dfranzi! closing this.

from cert.

@neil477 the problem probably is that CircleCI will create a fresh machine for every run, so you run out of slots. You'll have to store the certificate + private key somewhere and import it, instead of running cert. If you have your own machine, you can use cert 👍

from cert.

Also, thanks @dfranzi for replying 👍

from cert.

@KrauseFx I tried doing as you suggested, but without success.
I'm using the import_certificates action but having problems with the keychain.
Would you mind explaining a little more or pointing the direction with a bit more details?

Thanks!

from cert.

Hooray! Succeeded after trying a few times.
I'll try to wrap up in a detailed blog post and link it here.

from cert.

@natanrolnik Oh cool, let me know once the blog article is live 👍

from cert.

There we go! My article that includes the Keychain/certificate handling in a Continuous Integration service. This may help people who reach this issue: http://natanrolnik.me/2015/10/21/introduction-to-fastlane-and-integrating-it-with-circleci-to-deploy-beta-with-crashlytics-fabric/

from cert.

Thank you, @natanrolnik! Used your hint for my Travis-CI builds. I've noticed that importing a private p12 keys (both development and distribution) in before_all allows using cert(without force:true of course) and sigh, without checking for is_ci.

@KrauseFx could this be added to the documentation?

from cert.

You're welcome @Sega-Zero ! Glad it helped you.

from cert.

This issue was migrated to fastlane/fastlane#3123. 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.