Re: Code signing problem using shared framework in Yosemite
Re: Code signing problem using shared framework in Yosemite
- Subject: Re: Code signing problem using shared framework in Yosemite
- From: Kyle Sluder <email@hidden>
- Date: Sun, 12 Oct 2014 09:32:39 -0700
On Oct 12, 2014, at 9:24 AM, Bill Cheeseman <email@hidden> wrote:
>
> I'm updating my UI Browser application and my related PFAssistive framework <http://pfiddlesoft.com> for Yosemite, and I've run into a specific problem related to code signing. I'm wondering if anyone can shed light on this.
>
> Specifically, UI Browser calls my framework's Objective-C wrapper methods for accessibility functions like AXIsProcessTrustedWithOptions(). These calls have begun to fail in recent GM releases of Yosemite. Console.app reports things like this:
>
> 2014-10-12 11:04:01.213 AM tccd[223]: Unable to verify code signing identity of com.pfiddlesoft.uibrowser: the code on disk does not match what is running
Curious: have you tried scouring your machine for all copies of the app and deleting them? Since it’s generally not possible to associate a running executable with a file on disk, the OS might be trying to look up your app via bundle identifier and finding an old, stale copy whose code really doesn’t match what’s running.
>
> Is code signing now making it impossible to use shared frameworks at all, going forward? That would be a huge change to spring on the developer community without advance warning.
What do you mean “shared frameworks”? As in, frameworks that live outside of your app wrapper? Because frameworks in and of themselves are certainly still usable.
--Kyle Sluder
_______________________________________________
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