Code signature invalid on Mac OS X 10.10.x

Question

Balin Ebergy OP

Created Nov ’16

Replies 5

Boosts 0

Views 13k

Participants 3

Hello everyone,

I have a program signed in Sierra(10.12.1) with XCode(8.1)

It was running fine on Sierra and El Capitan, however, when running on Yosemite, the app program crashed and showed the following error message:

I had searched online for solutions yet however most of them all suggested to reinstall OS to solve this problem

However, it may not be good that the users who have Yosemite installed need to reinstall their OS to use my app...

Do I really have to reinstall OS or I can do something to my program to fix it?

All ideas are appreciated, thanksThe message contains invalid characters.

Due to annoying "The message contains invalid characters." I cannot post the pull error message here...

Boost

Answer 1

Balin Ebergy OP

Nov ’16

Process: testclient [758] Path: /Volumes/VOLUME/testclient.app/Contents/MacOS/testclient Identifier: com.yourcompany.testclient Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: testclient [758] User ID: 501 Date/Time: 2016-11-25 13:56:58.509 +0800 OS Version: Mac OS X 10.10.5 (14F2009) Report Version: 11 Anonymous UUID: 5B74A312-5939-B401-D26A-EC4780978F9F Time Awake Since Boot: 640 seconds Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: @executable_path/../Frameworks/libxapian.15.dylib Referenced from: /Volumes/VOLUME/testclient.app/Contents/MacOS/testclient Reason: no suitable image found. Did find: /Volumes/test.dmg/testclient.app/Contents/MacOS/../Frameworks/libxapian.15.dylib: code signature invalid for '/Volumes/test.dmg/testclient.app/Contents/MacOS/../Frameworks/libxapian.15.dylib'

0

Answer 2

arcin1 OP

Dec ’16

I'm having the same issue with my app, did you find out why this is happening only on 10.10?

0

Answer 3

Balin Ebergy OP

Jan ’17

Sorry, after several days of searching solutions, I just temporarily (maybe forever) give up the support of Yosemite.

0

Answer 4

GregC OP

Feb ’17

I've had the same problem with my apps too. Updates I released November and December still run on Yosemite, but new updates since then crash with a similar error message.

0

Answer 5

GregC OP

Feb ’17

Cause and solution: http://stackoverflow.com/questions/41865537/how-does-apples-codesign-utility-decide-which-sha-algorithms-to-sign-a-shared

0