Thanks Greg. You said to delete them and re issue them right? Is there another way to do it? Do you know of anywhere this process is documented or where there are specific instructions?
Was I overlooking something then, when I clicked on Download having created a new Cert? As far as I can make out, that just gave me the public part - which leads to the issues one sees with KeyChain and having untrusted certificates.
1 Like
OK, so @jim_mckay was good enough to jump on a call with me and get the toothpaste back into the tube. The root causes, were, i think, a few things; some possibly expired certs, my copy files script in the wrong sequence (which never seemed to matter before but ok) and most hair ripping of all, was this ambiguity error during the build that stymied the build. Jim showed me how to use XCode to open my certs, delete the older ones and xcode magically repairs and installs them into the Keychain. Then, the final coup de gras was to use the full name of the signing cert rather than just the Developer ID in the Developer ID field of the build step. This blows my mind I must say and is not in any google, xojo or other documentation that I could see. Jim’s having had a hair ripper or two over code signing was what saved my sanity. Thanks to you guys for helping and giving a shoulder to cry on. Here i am a mere 20 hours (12 working) later, back building again. Thanks All!
I think thats true Tim. I did that too and even though one can double click them and choose “Always Trust” from the keychain, something was not right after that. I recommend to anyone, to use XCode to manage their certs as there seems to be some good things inside their process.