Notarize | CLI to easily notarize a Mac app | Command Line Interface library

Duplicate of your own post : Where can I find electron forge config js file where package.json is parsed?

You should rather extract the electron forge configuration in a separate JS file : ElectronForge configuration and load your environment variables using process.env.YOUR_VARIABLE_NAME

the solution is to use the entitlements.plist when signing the code:

I have been able to solve my notarization issues. I don't know if this is "the right way" but it worked, so here is what I did – maybe it will save someone the time and frustration I went through.

Context: I am a contractor with "Admin" privileges on my client's Apple Developer account, along with my having a personal ADC account. As noted in my question, the Electron Builder docs state that an "app-specific password" is needed and links to an Apple doc about how to generate one. However, that link is or seems to be about generating a specific password to use with a 3rd party app like "Twitter" – so that one's personal Apple ID password is protected. At least that is the way I read it. There is no place within my personal ADC account or the Team account where such a password can be generated. So I generated a password in my personal ADC account.

This post from Electron Builder issues introduced an additional property to pass to notarize: the "ProviderShortname". As noted in the post, this can be accessed through:

The solution to fix this is put all dylibs (except under "/usr/lib" or "/System/Library/Frameworks") under the folder which is in under control of electron.

Something like this in my project: https://github.com/code4history/MaplatEditor/tree/master/assets/mac/canvas/build/Release

But just putting dylib is not working, because each dylib has information about link to other libraries.

You can check which libraries are linked from each dylib by using "otool" command, and youcan overwrite it by using "install_name_tool" command.

https://github.com/code4history/MaplatEditor/blob/master/mac_canvas_dylib

In this URL, you can find what I did for my project.

You need to install Xcode - the command line tools do not include altool, but Xcode does.

Assuming you install Xcode to /Applications you will find altool at /Applications/Xcode.app/Contents/Developer/usr/bin/altool

No. This cannot be removed. It is a security feature to inform the user.

Instead of using a plug-in, you may be able to do what you want with Installer JS scripts.

The problem was some remnants of old a bundle identifier. I had migrated to a sandboxed distribution of the app, and at some point in the process, I had built the sandboxed version with the same bundle identifier. macOS had registered the bundle identifier to belong to a sandboxed app and, probably due to security reasons, no longer wanted to allow it to run non-sandboxed.

I created a fresh Info.plist, and changed the bundle identifier and the errors were gone.

I downgraded the sqlite3 package to v5.0.0 and it rebuilt correctly. Hope this helps anyone else with the same issue.

Source: nodejs electronjs sqlite3 - use of undeclared identifier 'napi_is_detached_arraybuffer'

I don't know if the reason I ran into this is the same as yours, but here's what I discovered, in case this helps anyone else.

Before manually notarizing your app (using electron-notarize), make sure the certificate type you're signing your app with is correct. You specifically need a Developer ID Application certificate (the last one):

I had been using Apple Distribution before, and notarization failed because of it. The list of files you're seeing are probably the first few files Apple checked, and they were signed with an incorrect type of certificate (don't quote me on this), and so it failed.

Either way, once I generated an Developer ID Application certificate, defined my entitlements this way: