-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
Signed applications are "invalid" on macOS #7
Comments
I think a better way is to use a packager hook (one that exists or make a new one) to run electron-compile, and then have Electron Packager run as normal. Is that feasible? |
@malept The issue is the ASAR file AFAIK. The problem is we must compile in the packaged folder (or we will generate a cache in the development directory). So if we need to generate a cache and the user has generated an ASAR then we can't generate a cache. So we remove the ASAR request and do it manually afterwords. |
Sorry if I'm being rather dense about this, but it's not clear to me why the electron-compile step can't work similarly to your proposed electron-rebuild hook. |
@malept Hahahahahaha, how did I miss that 😆 It can almost certainly be done there 👍 |
…r afterCopy hook ISSUES CLOSED: Fixes #7
…r afterCopy hook ISSUES CLOSED: Fixes #7
…r afterCopy hook ISSUES CLOSED: Fixes #7
Add TypeScript definitions for Electron
Traced this to be due to the packager signing and then we modify the ASAR file. Should extract the signing config and sign ourselves.
/cc @malept
The text was updated successfully, but these errors were encountered: