Electron app sigin in

Command failed: codesign --sign 142DA07B8371F5C9BCE0FFEC6B23CDEB84F48E52 --force --timestamp --options runtime --entitlements /Users/mymac/Desktop/ElectronApp/node_modules/app-builder-lib/node_modules/@electron/osx-sign/entitlements/default.darwin.plist /Users/mymac/Desktop/ElectronApp/dist/mas-arm64/electron.app/Contents/Library/LoginItems/electron Login Helper.app/Contents/MacOS/electron Login Helper

/Users/mymac/Desktop/ElectronApp/dist/mas-arm64/electron.app/Contents/Library/LoginItems/electron Login Helper.app/Contents/MacOS/electron Login Helper: replacing existing signature

/Users/mymac/Desktop/ElectronApp/dist/mas-arm64/electron.app/Contents/Library/LoginItems/electron Login Helper.app/Contents/MacOS/electron Login Helper: resource fork, Finder information, or similar detritus not allowed

failedTask=build stackTrace=Error: Command failed: codesign --sign 142DA07B8371F5C9BCE0FFEC6B23CDEB84F48E52 --force --timestamp --options runtime --entitlements /Users/mymac/Desktop/ElectronApp/node_modules/app-builder-lib/node_modules/@electron/osx-sign/entitlements/default.darwin.plist /Users/mymac/Desktop/ElectronApp/dist/mas-arm64/electron.app/

I'm not entirely sure what's causing this issue. Has anyone else encountered this error while signing their macOS app? I’d really appreciate any guidance or solutions you can share.

Answered by DTS Engineer in 845418022

I presume you’re concerned about the resource fork, Finder information, or similar detritus not allowed error. If so, that error occurs when the program you’re trying to sign contains extended attributes that can’t be sealed over by the code signature.

This is a pretty common error. In this thread I show one example of how to reproduce this, and in this thread we tracked down a specific example of how this can happen.

Hmmmm, you’re using the desktop as your build products location, which is never a good idea. I recommend you switch to a directory that’s neither covered by MAC nor susceptible to iCloud Drive syncing. I generally recommend that you use a custom directory in ~ for this sort of thing.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I presume you’re concerned about the resource fork, Finder information, or similar detritus not allowed error. If so, that error occurs when the program you’re trying to sign contains extended attributes that can’t be sealed over by the code signature.

This is a pretty common error. In this thread I show one example of how to reproduce this, and in this thread we tracked down a specific example of how this can happen.

Hmmmm, you’re using the desktop as your build products location, which is never a good idea. I recommend you switch to a directory that’s neither covered by MAC nor susceptible to iCloud Drive syncing. I generally recommend that you use a custom directory in ~ for this sort of thing.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Electron app sigin in
 
 
Q