You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/packaging/signing.mdx
+7
Original file line number
Diff line number
Diff line change
@@ -118,6 +118,13 @@ vpk pack \
118
118
When these parameters are specified and valid, Velopack will automatically code sign and notarize your application and installer packages.
119
119
120
120
:::tip
121
+
Velopack will use `codesign` and `xcrun notarytool` to sign and notarize your application. By default they will use the default keychain on your device to discover certificates and the notary profile.
122
+
If you would like to use a different keychain, you must install your certificates and create your notary profile on that keychain and use the Velopack `--keychain {path}`
123
+
argument to specify that Velopack should discover certificates from a non-default keychain.
124
+
<hr />
125
+
If you do not provide an entitlements file for hardened runtime, one suitable for most dotnet apps will be provided for you automatically. If your app requires
126
+
special entitlements and the defaults are not suitable, you should supply your own signing entitlements using `--signEntitlements {path}`
127
+
<hr />
121
128
Even though your certificate may appear as `Developer ID Application: Your Name (TeamName)` in Keychain Access, you should not specify the team name as a part of
122
129
your `--signAppIdentity` or `--signInstallIdentity` arguments. Your certificate should just be `Developer ID Application: Your Name` with no team.
0 commit comments