question-mark
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.

Error when signing

See original GitHub issue

so i almost get there. here is the trace. I have replaced my email and id with MY_IDENTITY and the directory to the root of the app with APP_DIR.

Signing app (identity: Mac Developer: MY_IDENTITY)
Error: Command failed: codesign --sign Mac Developer: MY_IDENTITY --force /APP_DIR/dist/mac/Specless Sync.app/Contents/Resources/app.asar.unpacked/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework
/APP_DIR/dist/mac/Specless Sync.app/Contents/Resources/app.asar.unpacked/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework: bundle format unrecognized, invalid, or unsuitable

    at ChildProcess.exithandler (child_process.js:205:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
From previous event:
    at MacPackager.sign (/APP_DIR/node_modules/electron-builder/out/macPackager.js:282:11)
    at /APP_DIR/node_modules/electron-builder/src/macPackager.ts:85:26
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at /APP_DIR/node_modules/electron-builder/src/macPackager.ts:85:10
    at Generator.next (<anonymous>)
From previous event:
    at MacPackager.pack (/APP_DIR/node_modules/electron-builder/out/macPackager.js:182:11)
    at /APP_DIR/node_modules/electron-builder/src/packager.ts:257:24
    at Generator.next (<anonymous>)
    at xfs.stat (/APP_DIR/node_modules/fs-extra/lib/mkdirs/mkdirs.js:56:16)
    at /APP_DIR/node_modules/graceful-fs/polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:114:15)
From previous event:
    at Packager.doBuild (/APP_DIR/node_modules/electron-builder/out/packager.js:379:11)
    at /APP_DIR/node_modules/electron-builder/src/packager.ts:170:52
    at Generator.next (<anonymous>)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at Packager.build (/APP_DIR/node_modules/electron-builder/out/packager.js:274:11)
    at /APP_DIR/node_modules/electron-builder/src/builder.ts:198:33
    at Generator.next (<anonymous>)
From previous event:
    at build (/APP_DIR/node_modules/electron-builder/out/builder.js:70:21)
    at Object.<anonymous> (/APP_DIR/node_modules/electron-builder/out/cli/build-cli.js:71:41)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)
    at startup (bootstrap_node.js:151:9)
    at bootstrap_node.js:542:3

the weirdest part about this is that a few moments before creating this app version i was able to build it, though it somehow errored when it was deployed to the wild when it did and still does not just by starting electron.

I also downloaded RB App Checker Lite and got the following output


The application was signed by “Apple Root CA”, “Mac Developer: MY_IDENTITY”.
    The (unverified) signing-time is: Jun 13, 2017, 1:44:02 PM.
    The object code format is “app bundle with Mach-O thin (x86_64)”.
    The signature contains the Team ID “DHXT4KYZEE”.
    Both bundle and signing identifiers are “com.specless.sync”.
    The signature specifies implicit requirements. 
    The signature specifies resource rules (v1). 
    The signature specifies resource rules (v2). 
    ➤ Requirements and resources didn't pass static validation.  

The code signature has the UUID “8553772E-FB33-16A0-85DB-B65DF0278D14”.
    Executable code for x86_64 has the UUID “645381EB-354A-3740-8CDD-DF9F333944EE”.

A signing-time snapshot of the application’s Info.plist was found. 
    Version 0.0.30 (0.0.30) Copyright © 2017 Michael McLaughlin

The signature contains 3 certificates. 
    Certificate “Apple Root CA”: 
        Your keychain contains this trusted root certificate.
        Will expire on Feb 9, 2035.
    Certificate “Apple Worldwide Developer Relations Certification Authority”: 
        Will expire on Feb 7, 2023.
    Certificate “Mac Developer: MY_IDENTITY”: 
        Will expire on May 30, 2018.
        SHA1 fingerprint: “CE64BF093E8EDE4D31F029830999A8399E9F2FA1”.
        Team ID or Organizational Unit: “DHXT4KYZEE”.
            This matches the Team ID contained in the signature.

The application is not sandboxed.

There are 8 embedded frameworks. 

50 auxiliary executables have been found. 
    24 data files have executable permissions, but should not.  
    54 files are invisible in the Finder.  
    35 executables are unsigned.  
    15 executables are signed by  “Apple Root CA”, “Mac Developer: MY_IDENTITY”. 
    39 executables are in the Resources folder. 
    3 executable files have no executable permissions, but should.  
    Different executables are using the same signing identifier “com.github.electron.framework”. 
    Different executables are using the same bundle identifier “com.github.electron.framework”. 

as you can see the line Requirements and resources didn't pass static validation. comes up. I just don’t know why this would happen.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
maikelmclauflincommented, Jun 13, 2017

so it looks like you were half right. removing @types/electron from the dependencies did the trick

0reactions
kaansoralcommented, Dec 12, 2018

@sethlu I noticed that my issue is likely different, at the time I +1’d this issue, I was in a confused state with provisionprofile’s, entitlements, sandboxing and had 10’s of related tabs open, so it was a mistake, created https://github.com/electron-userland/electron-osx-sign/issues/181 instead

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error Message : "An error occurred while signing in"
When attempting to execute a conversion, the following message will be returned: "An error occurred while signing in." ...
Read more >
Windows error message: "We can't sign in to your account"
If you try to sign in to Windows 11 and receive the error message, "We can't sign in to your account" or you...
Read more >
Can't sign in from a third-party service - Google Account Help
You may be blocked from signing in to your Google Account with some services or programs ... An error saying that your password...
Read more >
Why do I get an error when signing into my Samsung account?
If you encounter an error message such as "An error occurred during an SSL connection" or "Sign in failed due to difference between...
Read more >
Netflix says 'There was a problem signing in.'
If you get the error message 'There was a problem signing in' on your iPhone, iPad, or iPod touch, use this article to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found