search

SamusAranX / MinimalMIDIPlayer

A MIDI player for macOS with SF2/DLS soundfont support
143 stars 3 forks source link

Crash on start on macOS Mojave (Code Signature Invalid) #2

Closed outadoc closed 6 years ago

outadoc commented 6 years ago

App won't start on macOS Mojave 10.14 (18A389). Crashes, mentioning an invalid code signature.
I'm using release v1.6.1, downloaded from Github.

Full crash dump:

Process:               MinimalMIDIPlayer [15053]
Path:                  /Applications/MinimalMIDIPlayer.app/Contents/MacOS/MinimalMIDIPlayer
Identifier:            com.peterwunder.MinimalMIDIPlayer
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           MinimalMIDIPlayer [15053]
User ID:               501

Date/Time:             2018-10-03 23:49:24.313 +0200
OS Version:            Mac OS X 10.14 (18A389)
Report Version:        12
Anonymous UUID:        68A7BFF7-4F20-D1B7-839E-11A1EE5D1940

Sleep/Wake UUID:       9103F94E-9BA1-4E79-A0AB-C08978514CDC

Time Awake Since Boot: 75000 seconds
Time Since Wake:       11000 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                 000000010f678000-000000010f69c000 [  144K] r-x/rwx SM=COW  

Thread 0 Crashed:
0                                   0x0000000112b07000 _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: 0x00007ffee0587b28
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x0000000112b07000  rfl: 0x0000000000000200  cr2: 0x0000000000000000

Logical CPU:     0
Error Code:      0x00000000
Trap Number:     0

Binary Images:
       0x10f678000 -        0x10f69bfff + (0) <86CA6346-08EC-3574-8DE1-6C3175FD46DD> 
       0x112b06000 -        0x112b846a7 + (625.13) <D6387150-2FB8-3066-868D-72E1B1C43982> 

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: 74096
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=868K resident=0K(0%) swapped_out_or_unallocated=868K(100%)
Writable regions: Total=8404K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8404K(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
STACK GUARD                       56.0M        2 
Stack                             8192K        2 
__DATA                             256K        5 
__LINKEDIT                         216K        3 
__TEXT                             652K        3 
shared memory                        8K        3 
===========                     =======  ======= 
TOTAL                             65.1M       12
SamusAranX commented 6 years ago

Please try the latest release, v1.7.1.

The last few builds were done with a beta version of Xcode 10, which may not have been the best idea. 😅

outadoc commented 6 years ago

Ah yup, that fixed it. 👏 Betas are tricky!

SamusAranX commented 6 years ago

Alright, there might be more to this than just beta Xcode versions. Does the app still work for you or has it started crashing again?

outadoc commented 6 years ago

It started crashing again indeed. Same error. :/

SamusAranX commented 6 years ago

Yeah, looks like you can't actually sign apps without paying Apple. Nice.

I'll upload a new, unsigned build tomorrow. That should finally get rid of that crash.

SamusAranX commented 6 years ago

I've uploaded a new release (v1.7.2) that should finally fix these issues. Turns out that Ad-Hoc certificates are not suited for app deployment. Not that Xcode would tell you that. 🙄

Anyway, the app is now signed and notarized. It should continue working until at least 2023.