Could not create another certificate, reached the maximum number of available certificates.

[AdamSwinden]

Running match development after cleaning everything up with match nuke development fails with the following error:

[11:46:02]: Could not create another certificate, reached the maximum number of available certificates.
[!] Could not create a new certificate as you reached the maximum number of certificates for this account. You can use the `match nuke` command to revoke your existing certificates. More information https://github.com/fastlane/match

As I have already run match nuke there are currently no development certificates in the developer portal. I am using an Enterprise account is that makes a difference.

[AdamSwinden]

Just tried the same thing on a regular developer account and it all worked as expected. Therefore I'm assuming that the Enterprise account is the issue here.

[wanewang]

+1 for the enterprise account,
although the website say
Enterprise Profiles Because of the potentially dangerous nature of In-House profiles we decided to not allow the use of match with enterprise accounts.
Well... the title is for Profiles, but the description says enterprise account, It seems that if the account is Enterprise, you can't ever never used it?

[AdamSwinden]

Ah. I hadn't read that far yet. I wish I had read it before running match nuke and binning all my existing certs and profiles. 😣

Perhaps support for Enterprise accounts should be an option with a warning rather than disabled completely.

[JaviSoto]

Hi @AdamSwinden! Sorry about that!

I think the decision about enterprise is perhaps something that we could potentially be open to reconsider. How do you feel about the security implications we mentioned in the README?

[AdamSwinden]

@JaviSoto I think they are completely valid reasons to be particularly cautious when dealing with Enterprise profiles. However, as match should be secure because of the OpenSSL encryption, I don't see it directly leading to Enterprise profiles getting into the wrong hands. These security implications should definitely be made clear to people using match with a strong warning, but the ultimate decision to use it or not should be down them. Perhaps by default match doesn't allow it, but an option could be added to the Matchfile to enable it.

[KrauseFx]

@AdamSwinden in general I wouldn't say the encryption is 100% secure. We'll think about how we will deal with enterprise profiles, we'll leave this issue open and update it once there are news 👍
Thanks @JaviSoto.

[adamstener]

This is happening to me with a regular dev account. I'm only able to create one, and running the second 'match development' or whichever one is run second, results in this error. I'm using a new dev account that was just made for this purpose, and just assigned to our team.

[nicolasbraun]

@adamstener Match will not revoke a certificate and you can only have one Development Cert per developer on your account. Are you sure the cert you generated during your first run was pushed to your repo? If yes it should be decrypted and used during the second run. It seems like Match is trying to recreate one letting me believe it could not find any on your repository.

This issue refers a specific issue with Enterprise accounts so maybe open a new one if the problem persists (feel free to ping me in it if you like)

PS 👍 for entreprise handling (and I confirm Match will only create Distribution certificate on a Entreprise account no matter which type parameter is passed)

[mfurtak]

I'm going to close this for now. Please let us know if you would like to continue the conversation 👍

[fastlanebot]

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