Automatic code signing still attempts to use a certificate uploaded to Bitrise

Question & Answer iOS
1

Hey guys, apologies if this has been asked before, but I’ve struck upon a strange problem in a couple of our projects.

I have an adhoc/development build workflow, where the “Xcode archive” step is set to “automatic signing” or “Xcode-managed signing”.

My understanding is that for this step I don’t need to upload a certificate (i.e generate a .p12, use the uploading tool or dragging and dropping the file to the portal, etc). Bitrise should use the service connection, and download/update certificate automatically

However the builds have been failing, firstly by attempting to use an expired certificate in Bitrise’s code signing store, — or by complaining that there’s no certificate found, after I deleted the expired cert (this sounds like a reasonable error, but as before, I’d expect Bitrise to handle this for me).

Would appreciate someone pointing me in the right direction, and if there’s anything changed that I wasn’t aware of.

2

Answering my own question here with a post that bubbled up from a few years ago:

TLDR:

  • should still upload a development certificate to Code Signing tab
  • without this (according to discussion in linked thread) a new dev certificate would be created for each new build, which is typically not what you want.
1 Like