macos 10.12.6 MAS package crash on launch #1967
dmg work fine. but MAS pkg will crash on launch, i think may be something wrong with code sign...
Date/Time: 2017-08-20 02:45:15.599 +0800
Sleep/Wake UUID: 908F1DE1-7255-44F9-8CC9-3C0FC0391E7A
Time Awake Since Boot: 32000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Termination Reason: Namespace CODESIGNING, Code 0x1
VM Regions Near 0 (cr2):
Thread 0 Crashed:
Thread 0 crashed with X86 Thread State (64-bit):
Logical CPU: 0
External Modification Summary:
AND BUILD LOGS:
com.apple.security.app-sandbox com.apple.security.application-groups HDGHJS34MK.im.EDITOR.pceditor com.apple.application-identifier HDGHJS34MK.im.EDITOR.pceditor com.apple.developer.team-identifier HDGHJS34MK +47ms electron-osx-sign Application signed. +0ms Done in 55.50s.
The text was updated successfully, but these errors were encountered:
Is there anything else settings not set up？...
Hi @fu122zh, the app is expected to crash at launch if code-signed for submission to iTunes Connect. (Ref: electron/electron-osx-sign#130 (comment)) To test the app locally for development purposes, I would suggest signing with your
@fu122zh so the one already signed with distribution certificate and the distributional provisioning profile is fine for submission to the Mac App Store. The catch is that... this signed version cannot be launched locally... and that's what caused your app to crash.
And to test it locally you may re-sign it with a development certificate and a development provisioning profile.
@sethlu I'm still seeing this
Apple's advice is to use the "archive" build flow:
Does electron-builder need to package the app in a specific way to make this work?
Here's my debug log
@jwheare from the debug log I cannot think of an obvious solution. Can you provide a screenshot from the Console at the time your app's trying to launch? It should provide more details about the exception.
@jwheare That sounds like a nice enhancement! Actually I encountered exactly the same issue last week with a dated provisioning profile and it took me some time to figure out the problem. Currently I am not sure how such misplacement can be verified and the code signing for production cannot be checked easily. Would you like to open an issue on