-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macos 10.12.6 MAS package crash on launch #1967
Comments
Please see #1196 |
@develar Is there anything else settings not set up?... |
Cc @sethlu could you please advise? |
Hi @fu122zh, the app is expected to crash at launch if code-signed for submission to iTunes Connect. (Ref: electron/osx-sign#130 (comment)) To test the app locally for development purposes, I would suggest signing with your CC: @develar |
@sethlu |
@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: https://developer.apple.com/library/content/qa/qa1884/_index.html 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. On electron/osx-sign#153, |
Well, I just tried with a fresh provisioning profile, and it now works. I'm chalking this up to the old profile having an old certificate associated with it. Sorry! |
Can that maybe be verified by the signing process? If the profile and certificate don't match show an error? |
@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 |
Sure thing, done :) electron/osx-sign#154. Even if this only works for development signing it would be a help. |
@jwheare Great, thanks for providing some references too! I will try to experiment a little bit with that. |
dmg work fine. but MAS pkg will crash on launch, i think may be something wrong with code sign...
crash report:
Process: EDITOR [10651]
Path: /Users/USER/Documents/*/EDITOR.app/Contents/MacOS/EDITOR
Identifier: im.EDITOR.pceditor
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: EDITOR [10651]
User ID: 501
Date/Time: 2017-08-20 02:45:15.599 +0800
OS Version: Mac OS X 10.12.6 (16G29)
Report Version: 12
Anonymous UUID: 3BA22CA9-FBEA-3969-F4DB-E86B8E15EED6
Sleep/Wake UUID: 908F1DE1-7255-44F9-8CC9-3C0FC0391E7A
Time Awake Since Boot: 32000 seconds
Time Since Wake: 9100 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2):
-->
__TEXT 000000010a1ba000-000000010a1bb000 [ 4K] r-x/rwx SM=COW
Thread 0 Crashed:
0 ??? 0x000000010c551000 _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff55a45c48
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010c551000 rfl: 0x0000000000000200 cr2: 0x0000000000000000
Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0
Binary Images:
0x10a1ba000 - 0x10a1baff7 +??? (0) <107BF4A4-1BF7-306B-944D-7DED190A60FE> (null)
0x10c550000 - 0x10c58ddc7 +??? (433.5) <322C06B7-8878-311D-888C-C8FD2CA96FF3> (null)
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 37022
thread_create: 0
thread_set_state: 0
AND BUILD LOGS:
OKAY take it away
electron-builder
electron-builder 19.23.0
No native production dependencies
Packaging for mas x64 using electron 1.7.6 to build/mas
electron-osx-sign electron-osx-sign@0.4.7 +0ms
Signing app (identity: 39773BF9CCB517E0457D54A4A6BC31618C776C46 3rd Party Mac Developer Application: Shenzhen Grameen Vision Cultural Communication Co., Ltd (HDGHJS34MK))
electron-osx-sign
identity
passed in arguments. +5mselectron-osx-sign Pre-sign operation enabled for provisioning profile:
pre-embed-previsioning-profile
tofalse
. +2mselectron-osx-sign Pre-sign operation enabled for entitlements automation with versions >=
1.1.1
:pre-auto-entitlements
tofalse
. +0mselectron-osx-sign No
provisioning-profile
passed in arguments, will find in current working directory and in user library... +2mselectron-osx-sign Executing... security cms -D -i /Users/LI/Documents/code/EDITOR-destop/embedded.provisionprofile +3ms
electron-osx-sign Provisioning profile:
The text was updated successfully, but these errors were encountered: