Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

electron-builder not signing .pkg. Application .app is signed properly.

See original GitHub issue

“electron-builder”: “^22.3.2” … (22.3.2) macOS

electron-builder is not signing my .pkg. Application .app is signed properly.

electron-builder  version=22.3.2 os=18.7.0
  • artifacts will be published if draft release exists  reason=CI detected
  • loaded configuration  file=package.json ("build" field)
  • loaded parent configuration  preset=react-cra
  • rebuilding native dependencies  dependencies=... platform=darwin arch=x64
  • packaging       platform=darwin arch=x64 electron=8.0.1 appOutDir=Artifacts/mac
  • signing         file=Artifacts/mac/My App.app identityName=Developer ID Application: X-Y-Z (BLAHBLAH) identityHash=XXXXXXXXXXXXXXXXXXX provisioningProfile=none
  • building        target=pkg arch=x64 file=Artifacts/My App-0.1.0-osx.pkg

Signing was working fine earlier so is there now an additional step or configuration option?

Issue Analytics

State:
Created 4 years ago
Comments:13

Top GitHub Comments

2reactions

marckohlbruggecommented, May 21, 2021

@andrew-mclachlan would you mind re-opening this issue as multiple people still seem to have this problem

2reactions

marckohlbruggecommented, May 21, 2021

I’m running into this same issue. For Mac App Store (MAS) it builds an .app and .pkg. The .app gets signed properly (verifiable with codesign -d -vvv app-name.app), but the .pkg installer that needs to be uploaded to App Store Connect does not get signed. (code object is not signed at all via codesign).

I’ve been unable to get my MAS builds accepted. A fix would be very welcome, because as it stands MAS builds seem broken.

Using all the latest packages as of writing. electron-builder 2.11.5 and electron-builder-notarize 1.20

Top Results From Across the Web

Code Signing

Codesigning via Electron Builder's configuration (via package.json) is not the only way to sign an application. Some people find it easier to codesign...

Code Signing

Properly preparing macOS applications for release requires two steps. First, the app needs to be code signed. Then, the app needs to be...

Signing electron-builder generated package on windows ...

I want to sign windows package with self signed certificate. My build machine is Windows Server 2019 64 bit. Node version 12.18.2 I...

code signature in [app] not valid

When I build the app and try to open it I immediately get an error that says appName ... A) Packaging Electron apps:...

Code Signing | Electron

If you are building an Electron app that you intend to package and distribute, it should be code signed. The Mac and Windows...