-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS Code Signing and Notarization require two different certificates? #6094
Comments
The problem seems to be that the
Thoughts? |
…ng when not mas (electron-userland#6094) fix(mac): Removing 3rd Party Mac Developer Application certificate selector (electron-userland#6101)
Nice find! Glad to hear that you were able to get it working as well. I thought DMG installers weren't supposed to be signed though? |
@mmaietta The installer itself is not signed but the application must be signed and notarized prior to building the installer. As long as you set sign to false in the dmg section of the electron builder config file, electron builder does the right thing. |
I am trying to sign my Electron-based application using the process documented in the electron-builder code signing guide. Since my developer machine has multiple identities, I am using the
CSC_NAME
environment variable to specify the certificate to use. If I try to use myDeveloper ID Application
certificate, the code signing process fails with the following warning:If I switch
CSC_NAME
to point at myMac Developer
certificate, the code signing portion of the process completes successfully but Apple notarization fails with errors coming back from the Apple notarization server saying that the binaries were not signed with a validDeveloper ID
certificate.According to Apple's Notarization Process FAQ, the binaries should be signed with the
Developer ID Application
certificate.Is this really a bug or am I just doing something wrong?
The text was updated successfully, but these errors were encountered: