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 2014-10-12 11:04:01.216 AM universalAccessAuthWarn[1793]: AccessibilityAPI: pid 21235, is not allowed to access the accessibility API. Path: /Users/cheeseb/Desktop/UI Browser/Applications/UI Browser.app/Contents/MacOS/UI Browser The code signing warning is surprising, because both the UI Browser application and the framework pass all of the codesign tests for proper signatures on disk. 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. -- Bill Cheeseman - b...@cheeseman.name _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
