> On Apr 7, 2016, at 9:25 AM, Trygve Inda wrote:
>
>> This may be relevant, though it does talk about issues with pref panes as
>> well.
>>
>> http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/
>
> Yup. That sums it up.
>
> The short story: tested with a default Xcode comma
Could this be relevant to the changes in Xcode for iOS library development
where you have to us archive instead of build to get the correct architectures
in your bundle?
> On Apr 7, 2016, at 12:25 PM, Trygve Inda wrote:
>
>> This may be relevant, though it does talk about issues with pref pane
> This may be relevant, though it does talk about issues with pref panes as
> well.
>
> http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/
Yup. That sums it up.
The short story: tested with a default Xcode command line tool that says
"Hello World".
1) Build a command line to
This may be relevant, though it does talk about issues with pref panes as well.
http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/
> On 7 Apr 2016, at 15:13, Trygve Inda wrote:
>
> My app is built on 10.11.3. It is a prefPane with one command line tool and
> three app bundles
I've seen quite a bit on my newsfeed regarding this...
http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/
https://www.noodlesoft.com/blog/2016/04/05/hazel-3-3-8-getting-past-the-gates/
https://forums.developer.apple.com/message/81349#81349
Haven't seen any workarounds yet - hop
My app is built on 10.11.3. It is a prefPane with one command line tool and
three app bundles (four helper tools) in it's bundle. I am getting
GateKeeper warnings on 10.11.4 systems, but not on anything else.
It is manually codesigned with my Developer ID... first the helper tool
frameworks, then
