Problem after signing/notarizing

Hello,

We have an app developed in Electron, which was working correctly on macOS, before signing/notarizing it.

After successfully signing and notarizing the app, it works correctly on a test computer we have, but crashes on other 2 devices during the verification process, with the following exceptions:

Exception Type:    EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes:   (removed because the system would not let me post it :/
Exception Note:    EXC_CORPSE_NOTIFY
Termination Reason:  Namespace CODESIGNING, Code 0x2

and

Exception Type:    EXC_CRASH (Code Signature Invalid)
Exception Codes:   (removed because the system would not let me post it :/
Exception Note:    EXC_CORPSE_NOTIFY
Termination Reason:  Namespace CODESIGNING, Code 0x1

Searching online didn't provide any clear insight.

  • The MAC used for the build is a macOS Mojave 10.14.6
  • The app works on the same computer it was built on
  • The app works on a test computer macOS Monterey 12.6
  • The app crashes on a test computer macOS Mojave 10.14.2 (the non-signed app was working fine on this same computer)
  • The app crashes on a test computer macOS Big Sur 11.6.7

I can provide the full crash reports, in case they are useful.

Thank you.

Answered by yurigiu in 732465022

removed

Accepted Answer

removed

removed

Does that mean you’ve resolved your issue?

Share and Enjoy

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

Does that mean you’ve resolved your issue?

No, it means this forum doesn't let me delete the comment, so I had to edit it out.

I had to make some attempts to see what kind of information was blocking my post: turns out it was the exception codes :/ ??

Now I can't even edit it anymore? Oh no, anyway...

With regards your DevForums issues:

  • DevForums gives you a short window to fix a post. After that, it’s read only.

  • The issue with posting the Exception Codes is likely a result of an on going spam mitigation effort.

Coming back to your technical issue, you can find my general guidelines on this topic in Resolving Trusted Execution Problems. Based on the OS releases on which you’re having problems, my first guess is that you’re hitting one of the issues described in the Normalise the Entitlements Property List section of Resolving Code Signing Crashes on Launch.

Share and Enjoy

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

Hello Eskimo,

Thank you for your help: normalising the entitlements plist file solved the problem.

Specifically, run this command on the plist file:

% plutil -convert xml1 entitlements.plist

Thank you again.

Problem after signing/notarizing
 
 
Q