This Action imports an iOS or macOS signing certificate into a keychain. By default it creates a new temporary keychain that allows the Xcode tools to access the certificates.

This Action has mostly been tested on macOS products. Although it probably just works, the goal is to support iOS and watchOS officially with the next release of this Action.

For simple projects where there is one scheme, invoking xcode-archive can be as simple as this:

- name: "Import Certificate: Development"
  uses: devbotsxyz/xcode-import-certificate@master
  with:
    certificate-data: ${{ secrets.DEVELOPMENT_CERTIFICATE_DATA }}
    certificate-passphrase: ${{ secrets.DEVELOPMENT_CERTIFICATE_PASSPHRASE }}
    keychain-password: ${{ secrets.KEYCHAIN_PASSWORD }

The certificate data should be a Base64 encoded .p12 file, which is the default certificate export format of Keychain Access.app. The keychain-password input should be a (hard to guess) random password to be used for the temporary keychain.

The devbotsxyz/example-macos-rings project is an example macOS project with a release.yml workflow that shows all the steps needed to go from creating a release in GitHub to ending up with a .zip file that contains a signed and notarized application.

• Carthage Bootstrap - Bootstrap your Carthage Dependencies.
• Xcode Archive - Build and Archive Xcode projects.
• Xcode Notarize - Notarize a macOS product.
• Xcode Staple - Staple a Notarization Ticket to your product.

This Action is licensed under the MIT license. Contributions are very much welcome and encouraged but we would like to ask to file an issue before submitting pull requests.