Code signing

Enable code signing for your iOS app

When you first add your iOS application to Nevercode, it will be built without code signing. To enable installing your application on real devices, you must provide the signing certificate and the provisioning profile(s) by selecting one of the methods listed below.

Manual upload

With this option, you can manually upload your signing certificate and provisioning profile(s) for code signing. To do so, you will first need to export the signing certificate and the provisioning profile(s).

To use manual upload:

  1. In your app settings, click Code signing on the left.
  2. Select Manual upload as the certificates and profiles management method.
  3. Upload both the provisioning profile(s) and the signing certificate. Note that if your app contains app extensions, you will need to upload an additional provisioning profile for each extension. Click Add another to add new fields for uploading.
Uploading signing files manually.

Uploading signing files manually.

  1. If your certificate requires a password, enter the password you provided during export in the Certificate password field. If no password is required, this step is omitted.
  2. Click Save to save this configuration for future builds.

Exporting signing certificate and provisioning profile

To export the signing certificate:

  1. Open Keychain Access by searching for it in Spotlight.
  2. Select My certificates in the Categories submenu on the left sidebar. The name of the certificate should start with iPhone Developer or iPhone Distribution.
Adding a signing certificate.

Adding a signing certificate.

  1. Select File > Export Items from the OSX menu bar.
Exporting signing certificate.

Exporting signing certificate.

  1. Sign the certificate when prompted. Be sure to leave the file format filled as Personal Information Exchange (.p12) because saving the certificate with the .cer extension will not include your private key.
Saving signing certificates.

Saving signing certificates.

  1. Enter the certificate export password when prompted (optional).

To download the provisioning profile:

  1. Select the appropriate provisioning profile from Apple Developer portal.
  2. Download and save it to have it ready.

Automatic file collection

This option enables you to automatically collect the signing files stored on your computer by running the provided collection script and use them for code signing.

To collect the signing files automatically:

  1. In your app settings, click Code signing on the left.
  2. Select Automatic file collection as the certificates and profiles management method.
  3. Run the script provided below in your terminal to collect the signing files. The Development team and Archive method fields will be populated automatically and your provisioning profiles and code signing identities will be listed below. If you have more than one development team and archive method option available, make sure to select the appropriate one.
Signing files have been collected by the script.

Signing files have been collected by the script.

Note that Nevercode will select the appropriate provisioning profile and certificate to be used for signing automatically during the build process. However, you can manually disable provisioning profiles collected by the script by expanding the profile and clicking Disable.

You can disable a particular provisioning profile.

You can disable a particular provisioning profile.

  1. Finally, click Save to save this configuration for future builds.

Using Fastlane Match

Fastlane match is a tool for iOS signing files management. With match, you can share a single code signing identity with your team for simpler code signing. The signing certificates and provisioning profiles will be stored in your private Git repository that Nevercode can access during the build process and use for signing your app.

Match setup

To use match for code signing, you first need to set it up for your iOS project by following the instructions here.

To enable code signing using match:

  1. In your app settings, click Code signing on the left.
  2. Select Using Fastlane Match as the certificates and profiles management method.
Enabling code signing using Fastlane match.

Enabling code signing using Fastlane match.

  1. Select the profile type to be used for signing.
  2. Provide the bundle identifier(s). If you have multiple targets with different bundle identifiers, add them as a comma-separated list.
  3. Supply your match passphrase for profile decryption.
  4. Upload the SSH key file for accessing the credentials in your private Git repository. This step is not required if the repository can be accessed with the project's SSH key.
  5. Click Save to save this configuration for future builds.