Re: Problem Authorizing accessibility in Yosemite-SOLVED
Re: Problem Authorizing accessibility in Yosemite-SOLVED
- Subject: Re: Problem Authorizing accessibility in Yosemite-SOLVED
- From: Bill Cheeseman <email@hidden>
- Date: Mon, 13 Oct 2014 13:35:40 -0400
On Oct 12, 2014, at 12:19 PM, Bill Cheeseman < email@hidden> wrote: 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.
I'm guessing from the wording of the code signing warning that Yosemite now disallows the use of accessibility calls made in a separate, shared framework. When I remove calls to my framework from UI Browser and call the AX... functions directly, they work without error. Is this the direction apple is moving in Yosemite?
Messing around with Xcode 6.1 build settings solved the problem. So, I am relieved to say that assistive applications apparently can use the accessibility API in Yosemite through an Objective-C wrapper framework installed in /Library/Frameworks as a shared framework.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden