Why electron-builder sign mas/mas-dev app by Developer ID Application?

• Version: 22.6.0

• Electron Version: 8.2.5
• Electron Type (current, beta, nightly): current

• Target: mas/mas-dev

Why electron-builder sign mas/mas-dev app by Developer ID Application certificate?

> app@1.0.0 dist /electron
> electron-builder "--mac" "mas-dev"

  • electron-builder  version=22.6.0 os=19.4.0
  • loaded configuration  file=package.json ("build" field)
  • writing effective config  file=dist/builder-effective-config.yaml
  • packaging       platform=mas arch=x64 electron=8.2.5 appOutDir=dist/mas-dev
  • signing         file=dist/mas-dev/App.app identityName=Developer ID Application: Org (12345) identityHash=ABC provisioningProfile=none
  • signing         file=dist/mas-dev/App.app identityName=Mac Developer: Name (54321) identityHash=ABC provisioningProfile=/certs/macOS_App_Development.provisionprofile

It seems the first signing is unnecessary.

[mahnunchik]

[mifi]

Update: the Code Signature Invalid crash when running app was not caused by this. It was because I was trying to run a mas build locally on my Mac, which I am 99% sure used to work fine last year, but now it doesnt. I’m guessing Apple changed something. Now to get it to run locally I have to use mas-dev and generate a development provisioning profile just for my computer and then make mas-dev use that instead. Then it starts, even though electron-builder signs it twice (first with «Developer ID Application», then 3rd party. So I guess it’s not a critical bug since it will just overwrite the first signature (thus taking more time to sign twice). I can also confirm same issue in 22.10.5