Muqriz 48f16bfc3e initail first | пре 4 месеци | |
---|---|---|
.. | ||
lib | пре 4 месеци | |
node_modules | пре 4 месеци | |
LICENSE | пре 4 месеци | |
README.md | пре 4 месеци | |
package.json | пре 4 месеци |
Notarize your Electron apps seamlessly for macOS
# npm
npm install @electron/notarize --save-dev
# yarn
yarn add @electron/notarize --dev
From Apple’s docs in XCode:
A notarized app is a macOS app that was uploaded to Apple for processing before it was distributed. When you export a notarized app from Xcode, it code signs the app with a Developer ID certificate and staples a ticket from Apple to the app. The ticket confirms that you previously uploaded the app to Apple.
On macOS 10.14 and later, the user can launch notarized apps when Gatekeeper is enabled. When the user first launches a notarized app, Gatekeeper looks for the app’s ticket online. If the user is offline, Gatekeeper looks for the ticket that was stapled to the app.
Apple has made this a hard requirement as of 10.15 (Catalina).
For notarization, you need the following things:
hardened-runtime
, including the following entitlement:
com.apple.security.cs.allow-jit
If you are using Electron 11 or below, you must add the com.apple.security.cs.allow-unsigned-executable-memory
entitlement too.
When using version 12+, this entitlement should not be applied as it increases your app’s attack surface.
notarize(opts): Promise<void>
options
Object
tool
String - The notarization tool to use, default is notarytool
. Previously, the value legacy
used altool
, which stopped working on November 1st 2023.appPath
String - The absolute path to your .app
fileappleId
String - The username of your Apple Developer accountappleIdPassword
String - The app-specific password (not your Apple ID password).teamId
String - The team ID you want to notarize under.appleApiKey
String - Absolute path to the .p8
file containing the key. Required for JWT authentication. See Note on JWT authentication below.appleApiKeyId
String - App Store Connect API key ID, for example, T9GPZ92M7K
. Required for JWT authentication. See Note on JWT authentication below.appleApiIssuer
String - Your App Store Connect API key issuer, for example, c055ca8c-e5a8-4836-b61d-aa5794eeb3f4
. Required if appleApiKey
is specified.keychain
String (optional) - The name of the keychain or path to the keychain you stored notarization credentials in. If omitted, iCloud keychain is used by default.keychainProfile
String - The name of the profile you provided when storing notarization credentials.appleIdPassword
const password = `@keychain:"Application Loader: ${appleId}"`;
Another option is that you can add a new keychain item using either the Keychain Access app or from the command line using the security
utility:
security add-generic-password -a "AC_USERNAME" -w <app_specific_password> -s "AC_PASSWORD"
where AC_USERNAME
should be replaced with your Apple ID, and then in your code you can use:
const password = `@keychain:AC_PASSWORD`;
You can obtain an API key from App Store Connect. Create a Team Key (not an Individual Key) with App Manager access. Note down the Issuer ID and download the .p8
file. This file is your API key and comes with the name of AuthKey_<appleApiKeyId>.p8
. Provide the path to this file as the appleApiKey
argument.
To get your teamId
value, go to your Apple Developer Account, then click on “Membership details”, and there you will find your Team ID.
debug
is used to display logs and messages. You can use export DEBUG=electron-notarize*
to log additional debug information from this module.
import { notarize } from '@electron/notarize';
async function packageTask () {
// Package your app here, and code sign with hardened runtime
await notarize({
appPath,
appleId,
appleIdPassword,
teamId,
});
}