Stop creating new certificates.

[krischik]

Please do not try to create new certificates without asking the user first. I now have hundreds of certificates and get the following error message:

[17:01:32]: Could not create another Distribution certificate, reached the maximum number of available Distribution certificates.

It will take me hours to delete all again. Creating certificates is never something which should be done unattended.

Same for provisioning profiles: readonly and fail_on_name_taken should both be set to true by default.

[fastlane-bot]

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[aaronraimist]

This is still an issue

[bekroz]

Any way to solve this? It's still an issue. Or should I have to revoke my certificates and add them again?

[ghost]

+1 I see this issue as well

[vin-fandemand]

• 1

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[bekroz]

It's still a problem.

[marcellodesales]

STILLLLLLLLL

[syao-arthrex]

NOT WORKING!

[krischik]

Hint for everybody who also has this problem: Using the following parameter is a workaround:

    get_provisioning_profile(
…
      readonly:		    true,
      fail_on_name_taken:   true,
…)

Hint for the developer: Changing the default of those two parameter is the easiest way to solve the problem.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[norrismcl]

Still a problem

[Crylion]

I'm also pretty puzzled by this. This tool claims to make ios signing "just work" without me having to manage my certificates all the time.

[henderson2350]

why does it attempt to replace/ create new distribution certs when I already have existing ones that should work? could this have to do with them being created by API key?

[henderson2350]

The fix for me was using only one certificate and branch per app (my issue was stemming from having multiple apps under the same developer account, all trying to use different certificates)

I use github for my certificate branches, and I replaced the content of all my branches with the content of one that was working

steps:

1. delete broken branches from github repo
2. git push origin [WORKING BRANCH]: [NAME OF BRANCH JUST DELETED]

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[sonic555gr]

Working with match s3 mode. Added "s3_object_prefix" and even though it pulls the certificates from the bucket successfully it fails to match them and tries to recreate them every time. Is match broken?