Sign and notarize for macOS
Set up an Apple Developer API key or a .p12 certificate, so cloud builds are signed and notarized for macOS.
You need the Apple Developer Program ($99/year), with an Apple ID that has two-factor authentication turned on. Creating the Developer ID certificate needs the team's Account Holder.
API Key (recommended)Link to this section
No Mac needed: everything happens in your browser. Freqlab makes the private key and a certificate request for you; you take the request to Apple and bring back the certificate.
1. Create an API keyLink to this section
In App Store Connect, open Users and Access, Integrations, App Store Connect API:
- Open the Team Keys tab (individual keys can't notarize), and click + next to Active.
- Name it, for example
Freqlab Signing, with the Developer role. - Download the
.p8file. Apple only lets you download it once. - Copy the Key ID (10 characters) and the Issuer ID (the long ID at the top of the page).
2. Add it to FreqlabLink to this section
In Signing credentials, click Set up under macOS, choose API Key, give it a Label, upload the .p8, and enter the Key ID and Issuer ID.
3. Download the certificate requestLink to this section
Freqlab shows Download CSR. Download the file.
4. Create the certificate at AppleLink to this section
As Account Holder, open Certificates, Identifiers & Profiles:
- Click +, choose Developer ID Application, and click Continue.
- Choose G2 Sub-CA (recommended) and click Continue, then Choose File and pick the CSR you downloaded.
- Click Continue, then Download the
.cerfile.
5. Upload the certificateLink to this section
Back in Freqlab, upload the .cer and click Upload certificate. If you chose I'll do this later, use Upload .cer on the credential when you're ready.
The credential is ready once it shows Valid until with a date. Until the .cer is uploaded it shows Pending certificate, and Studio and Express don't offer it for builds.
Certificate (.p12)Link to this section
For a Developer ID certificate you already have. You need the Mac it was created on, since the private key is in its keychain.
- In Keychain Access, find your Developer ID Application certificate, right-click it, and Export it as a
.p12with a password. - Create an API key for notarization (step 1 above).
- In Signing credentials, click Set up under macOS, choose Certificate (.p12), give it a Label, upload the
.p8and the.p12, and enter the Key ID, Issuer ID and .p12 Password.
After saving, check the credential shows an expiry date (Valid until or Expires in). If it doesn't, the file or password was wrong: Freqlab can't read the certificate, and builds will fail with a Signing Error. Click Update and upload it again.
Renew or replaceLink to this section
- The certificate is expiring: for an API Key credential, click Update. It asks for the
.p8, Key ID and Issuer ID again (if you didn't keep the.p8, create a new key first), and makes a new request, so your current certificate stops working and the credential can't sign until you repeat steps 3 to 5 with the new CSR. For a .p12, export the new certificate and Update. - The API key was revoked or lost: make a new one in App Store Connect, then Update the credential with the new
.p8, Key ID and Issuer ID.
If something goes wrongLink to this section
| Message | What to do |
|---|---|
| The App Store Connect API key (.p8) could not be read | Upload the .p8 exactly as downloaded from App Store Connect |
| Key ID must be alphanumeric uppercase | Copy the Key ID again from the API Keys page |
| Issuer ID must be a valid UUID | Copy the Issuer ID again from the top of the API Keys page |
| Invalid certificate file | Upload the .cer exactly as Apple gave it |
| Certificate must be a Developer ID certificate from Apple | You made a different certificate type. Create a Developer ID Application certificate |
| Certificate public key does not match the stored private key | The .cer was made from another CSR (often an old one after Update). Download this credential's CSR and create the certificate again |
| Your Apple Developer account has an agreement that needs accepting | The Account Holder accepts it at developer.apple.com/account |
| Apple rejected your App Store Connect API key (401 Unauthenticated) | The key was revoked or expired. Make a new one and Update |
| Apple rejected the notarization request with a 403 Forbidden | The key's role must be Developer or Admin, and your Apple Developer Program membership active |
| The App Store Connect key (.p8) in this build's signing credential can't be read | Update the credential with the .p8 again |