The enforced requirement to use Fastlane’s
match tool to provide code-signing certificates for my iOS deployment is something that was an unexpected interruption to my workflow.
I prefer using
sigh, as they allow more fine-grained control over the entire process, and have them configured to perform to my requirements when run locally.
Are there any particular reasons that the decision to force users of 2.0, and from August 31 all CircleCI users, to use the tool that takes away much of the control over code-signing?
Is it possible to reintroduce the 1.0 method of using the WebUI to install code-signing certificates, as raised here in November 2017?