Re: 3rd party framework crashes with invalid code sign
Re: 3rd party framework crashes with invalid code sign
- Subject: Re: 3rd party framework crashes with invalid code sign
- From: Mike Abdullah <email@hidden>
- Date: Mon, 07 Sep 2015 17:40:11 +0100
> On 19 Aug 2015, at 06:09, Nava Carmon <email@hidden> wrote:
>
>
> We have a weird problem after upgrading to Yosamite:
>
> We use a 3rd party framework and codesign it on copying in Build Phases.
> When we run the application (which is LSUIElement - agent application) sometimes after it crashes with the following crash report and the user cannot run it again anymore :
>
> 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/TspSdk.framework/Versions/A/TspSdk
> Referenced from: /Users/USER/Desktop/Test1.app/Contents/MacOS/Test
> Reason: no suitable image found. Did find:
> /Users/myuser/Desktop/Test1.app/Contents/MacOS/../Frameworks/TspSdk.framework/Versions/A/TspSdk: code signature invalid for '/Users/myuser/Desktop/Test1.app/Contents/MacOS/../Frameworks/TspSdk.framework/Versions/A/TspSdk'
>
> /Users/myuser/Desktop/Test1.app/Contents/MacOS/../Frameworks/TspSdk.framework/Versions/A/TspSdk: code signature invalid for '/Users/myuser/Desktop/Test1.app/Contents/MacOS/../Frameworks/TspSdk.framework/Versions/A/TspSdk'
>
> Invoking codesign from terminal on this framework returns valid results, but nevertheless we get this crash on trying to run the application... Once it crashes, the only way to make it run again - re install the application.
>
> Also we see some alert, that asks us to check whether we try to run this application on a proper version of OS X, which doesn't happen on first run.
> The deployment target of this application 10.6
> Can someboby help us to understand what might be the problem?
We've had a similar report from a customer after updating from 10.10.4 -> 10.10.5 and were unable to reproduce here. Downloading a fresh copy of the app made no difference. Oh, and they tried both App Store and regular versions of the app.
Eventually they re-installed the OS, and that worked fine. So my rubbishy guess so far is that something in Gatekeeper’s validation rules was corrupted somehow.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden