Implementing Find panel in WebView

[Graham Cox]

Hi,

I’m using WebView in my app, and I see it implements -performFindPanelAction: 
doc says “this operates similarly to NSTextView”. So I hook up a button to it, 
with tag set to 1, which should be the ‘showFindPanel’ action tag. But nothing 
happens. Since all this magic is internal to WebView, and the magic doesn’t 
happen, I’m not sure what I should do. I assume I’m missing the correct magic 
incantation, but what?

—Graham



___

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

Re: Codesign broken in 10.11.4

[Glenn L. Austin]

> 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 command line tool that says
> "Hello World".
> 
> 1) Build a command line tool on 10.11.3 and sign it with my Developer ID.
> Everything is fine.
> 
> 2) Test it on 10.11.4 and spctl gives me an "obsolete resource envelope"
> error.
> 
> This bug is preventing the release of a major new version of our product.

You did know that Apple updated codesigning in a way that was 
backwards-compatible, but not forwards compatible?


-- 
Glenn L. Austin, Computer Wizard and Race Car Driver <><



___

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

More detail on the iOS keyboard display bug

[Alex Zavatone]

I was just going through my project today and came across my comments in the 
code where this happens + the SO link that explains more about this issue.

It seems that this bug was first reported in 2012.  Someone claims it’s fixed 
on iOS 9.2.1.

Hope this helps

- (void)viewDidAppear:(BOOL)animated {
[super viewDidAppear:animated];

// AZ 12142015 - there is a significant delay here on the iPad for invoking 
and displaying the keyboard.
// ONLY HAPPENS WHEN THE IPAD IS PLUGGED IN and running from Xcode.  
// http://stackoverflow.com/a/27487885

dispatch_async(dispatch_get_main_queue(), ^{
[self.emailAddressField becomeFirstResponder];
});
}


___

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

Re: Alternatives to NSMatrix that uses bindings similar to NSMatrix's bindings

[Graham Cox]

> On 8 Apr 2016, at 5:36 AM, Nivek Research  wrote:
> 
> I have a number of NSMatrix instances that group radio buttons. Most bind the 
> selectedIndex or selectedTag bindings available on NSMatrix to a numeric 
> value in a model object. The others bind the contentObjects and 
> selectedObject binding available on NSMatrix. As NSMatrix is informally 
> deprecated in OS X 10.8 and later does anyone know a way to bind multiple 
> NSRadioButtons to a single numeric value as was once done with selectedIndex 
> or selectedTag such that the selected radio button follows the numeric value? 
> Similarly does anyone have a way to bind multiple buttons to a single object 
> value like NSMatrix’s selectedObject was used previously? Ideally any 
> solution should be backwards compatible to OS X 10.6 as I still need to 
> support that release. I have searched the internet though I have not seen a 
> solution that will work without major changes to my model code. Not that I am 
> not willing to make the changes. I just wonder if anyone has been enlightened 
> with a cooler solution.

If you have a bunch of “naked” radio buttons, all having the same target and 
selector (but presumably different tags, so you can distinguish them), they 
will automatically act as a group. This behaviour came in at some point in the 
mid OS X era, say 10.5/10.6, so isn’t universal, but it’s less bother than 
messing about with NSMatrix. If you need to set one programatically, just keep 
outlets to the individual buttons.

—Graham




___

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

Re: Alternatives to NSMatrix that uses bindings similar to NSMatrix's bindings

[Jeff Szuhay]

Last week, I filed a sample code bug #25499365 against the ButtonMadness sample 
code project.
I’m not sure if that will be enough.


> On Apr 7, 2016, at 1:26 PM, Sean McBride  wrote:
> 
> On Thu, 7 Apr 2016 15:36:51 -0400, Nivek Research said:
> 
>> I have a number of NSMatrix instances that group radio buttons. Most
>> bind the selectedIndex or selectedTag bindings available on NSMatrix to
>> a numeric value in a model object. The others bind the contentObjects
>> and selectedObject binding available on NSMatrix. As NSMatrix is
>> informally deprecated in OS X 10.8 and later does anyone know a way to
>> bind multiple NSRadioButtons to a single numeric value as was once done
>> with selectedIndex or selectedTag such that the selected radio button
>> follows the numeric value? Similarly does anyone have a way to bind
>> multiple buttons to a single object value like NSMatrix’s selectedObject
>> was used previously? Ideally any solution should be backwards compatible
>> to OS X 10.6 as I still need to support that release. I have searched
>> the internet though I have not seen a solution that will work without
>> major changes to my model code. Not that I am not willing to make the
>> changes. I just wonder if anyone has been enlightened with a cooler solution.
> 
> Kevin,
> 
> Yeah, I keep meaning to file a radar about this.  I didn't find any nice way 
> to do this, so I'm mostly still using NSMatrix for radio buttons.  Recently, 
> I wrote a little helper class, attached here, that makes it a little easier 
> to use bindings with non-NSMatrix radio buttons.  It's not as nice as 
> NSMatrix's built-in IB support, but maybe you'll find it helpful.
> 
> Cheers,
> 
> -- 
> 
> Sean McBride, B. Eng s...@rogue-research.com
> Rogue Researchwww.rogue-research.com 
> Mac Software Developer  Montréal, Québec, Canada
> ___
> 
> 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/jeff%40szuhay.org
> 
> This email sent to j...@szuhay.org

___

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

Re: Alternatives to NSMatrix that uses bindings similar to NSMatrix's bindings

[Sean McBride]

On Thu, 7 Apr 2016 15:36:51 -0400, Nivek Research said:

>I have a number of NSMatrix instances that group radio buttons. Most
>bind the selectedIndex or selectedTag bindings available on NSMatrix to
>a numeric value in a model object. The others bind the contentObjects
>and selectedObject binding available on NSMatrix. As NSMatrix is
>informally deprecated in OS X 10.8 and later does anyone know a way to
>bind multiple NSRadioButtons to a single numeric value as was once done
>with selectedIndex or selectedTag such that the selected radio button
>follows the numeric value? Similarly does anyone have a way to bind
>multiple buttons to a single object value like NSMatrix’s selectedObject
>was used previously? Ideally any solution should be backwards compatible
>to OS X 10.6 as I still need to support that release. I have searched
>the internet though I have not seen a solution that will work without
>major changes to my model code. Not that I am not willing to make the
>changes. I just wonder if anyone has been enlightened with a cooler solution.

Kevin,

Yeah, I keep meaning to file a radar about this.  I didn't find any nice way to 
do this, so I'm mostly still using NSMatrix for radio buttons.  Recently, I 
wrote a little helper class, attached here, that makes it a little easier to 
use bindings with non-NSMatrix radio buttons.  It's not as nice as NSMatrix's 
built-in IB support, but maybe you'll find it helpful.

Cheers,

-- 

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com 
Mac Software Developer  Montréal, Québec, Canada
//
// RRRadioBinder.h
//
// Created on 2016-01-08.
// Copyright Rogue Research 2016. All rights reserved.
//
// This file is encoded as UTF-8.
//
// $Id: RRRadioBinder.h 31325 2016-01-13 21:23:49Z sean $

/*! \class RRRadioBinder
 \brief Instances of this class can be used to bind together an integer and a 
group of radio buttons using Cocoa bindings. It's a replacement for the 
deprecated NSMatrix and its 'selectedTag' binding.  Should be instantiated in a 
nib file, with an outlet connecting it to controller to bind to and a 'user 
defined runtime attribute' named 'bindingKeyPath' set to a keypath of the 
controller. Observation is started in awakeFromNib and stopped in dealloc. */

#import 

NS_ASSUME_NONNULL_BEGIN

@interface RRRadioBinder : NSObject

/// The controller to bind to.
@property (readwrite, weak, nonatomic) IBOutlet NSController* bindingController;

/// The keypath of the controller to observe.
@property (readwrite, copy, nonatomic) NSString* bindingKeyPath;

/// The radio buttons to manage. At least 2 should be connected for non-trivial 
usage. They should all have the same action methed, namely handleRadioButton:.  
They should all have different tags.
@property (readwrite, weak, nonatomic, nullable) IBOutlet NSButton* 
radioButton0;
@property (readwrite, weak, nonatomic, nullable) IBOutlet NSButton* 
radioButton1;
@property (readwrite, weak, nonatomic, nullable) IBOutlet NSButton* 
radioButton2;
@property (readwrite, weak, nonatomic, nullable) IBOutlet NSButton* 
radioButton3;
@property (readwrite, weak, nonatomic, nullable) IBOutlet NSButton* 
radioButton4;

/// The action method that all radio buttons should be connected to.
- (IBAction)handleRadioButton:(id)inSender;

@end

NS_ASSUME_NONNULL_END


RRRadioBinder.m
Description: Binary data
___

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

Alternatives to NSMatrix that uses bindings similar to NSMatrix's bindings

[Nivek Research]

I have a number of NSMatrix instances that group radio buttons. Most bind the 
selectedIndex or selectedTag bindings available on NSMatrix to a numeric value 
in a model object. The others bind the contentObjects and selectedObject 
binding available on NSMatrix. As NSMatrix is informally deprecated in OS X 
10.8 and later does anyone know a way to bind multiple NSRadioButtons to a 
single numeric value as was once done with selectedIndex or selectedTag such 
that the selected radio button follows the numeric value? Similarly does anyone 
have a way to bind multiple buttons to a single object value like NSMatrix’s 
selectedObject was used previously? Ideally any solution should be backwards 
compatible to OS X 10.6 as I still need to support that release. I have 
searched the internet though I have not seen a solution that will work without 
major changes to my model code. Not that I am not willing to make the changes. 
I just wonder if anyone has been enlightened with a cooler solution.
—kevin
___

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

Re: Proper target for table cell view buttons

[Quincey Morris]

On Apr 7, 2016, at 10:45 , Fritz Anderson  wrote:
> 
> (2) Is your view controller not a table delegate already?

As you say.

I don’t actually know the answer to the original question, but I wonder if the 
problem is that (for a view-based table view) the cell view is archived in a 
separate NIB file that’s generated when the storyboard or XIB containing the 
table view is compiled. Then, there would be a difficulty that objects in the 
NIB have no way to connect to anything outside the NIB except via File’s Owner, 
and that’s set to something else.

Perhaps "it works as is” because there’s actually no target, so the action 
message passes up the responder chain to the view controller. In that case, 
there isn’t any need to find a way to specify the target explicitly.

___

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

Re: How to stop an Application being Activated

[Fritz Anderson]

On 7 Apr 2016, at 11:35 AM, Dave  wrote:
> 
> Is it possible to stop an application being activated, I mean, if an attempt 
> is made to make an application active it is somehow intercepted by another 
> application?

I gather you hope to write the second application — the one that wages a 
denial-of-service attack against the first.

You needn’t bother looking for the answer.

If this is in service to some kind of DRM (I refuse to debate the value), 
investigate the method iTunes uses to prevent debuggers from attaching. I 
believe it’s available to other applications as well.

Depending on what you’re trying to accomplish, you might make progress by 
having your application pose as an assistive input method.

By the way, what _are_ you trying to accomplish? I assume you are not an evil 
mastermind.

— F


___

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

Re: Proper target for table cell view buttons

[Fritz Anderson]

On 7 Apr 2016, at 11:04 AM, David Catmull  wrote:
> 
> I have some buttons in my table cell views, and I wanted to set my view 
> controller as their target, but Xcode warns that such objects “may only be 
> connected to the table view’s delegate”. The things is, it works as is. Why 
> does Xcode want me to do it that way?
> 
> I plan to try refactoring to satisfy the warning, but I’m still curious what 
> the reasoning is.

I’m curious about two things.

(1) Which platform?

(2) Is your view controller not a table delegate already?

— F


___

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

Re: Codesign broken in 10.11.4

[Jim Adams]

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 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 tool on 10.11.3 and sign it with my Developer ID.
> Everything is fine.
> 
> 2) Test it on 10.11.4 and spctl gives me an "obsolete resource envelope"
> error.
> 
> This bug is preventing the release of a major new version of our product.
> 
> :(
> 
> Trygve
> 
> 
> 
> ___
> 
> 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/jim.adams%40sas.com
> 
> This email sent to jim.ad...@sas.com


___

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

How to stop an Application being Activated

[Dave]

Hi All,

Is it possible to stop an application being activated, I mean, if an attempt is 
made to make an application active it is somehow intercepted by another 
application?

All the Best
Dave


___

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

Re: Codesign broken in 10.11.4

[Trygve Inda]

> 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 tool on 10.11.3 and sign it with my Developer ID.
Everything is fine.

2) Test it on 10.11.4 and spctl gives me an "obsolete resource envelope"
error.

This bug is preventing the release of a major new version of our product.

:(

Trygve



___

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

Proper target for table cell view buttons

[David Catmull]

I have some buttons in my table cell views, and I wanted to set my view 
controller as their target, but Xcode warns that such objects “may only be 
connected to the table view’s delegate”. The things is, it works as is. Why 
does Xcode want me to do it that way?

I plan to try refactoring to satisfy the warning, but I’m still curious what 
the reasoning is.
___

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

Re: [NSWorkspace openURL:] - any way to avoid a new tab?

[Jens Alfke]

-openURL is pretty generic, working with any type of URL that there's an app 
registered for, so it doesn't have a notion of specific UIs like tabs.

If you send an AppleEvent directly to Safari, there might be a param to control 
tab behavior. But that would annoy users who have a different default browser...

—Jens 

> On Apr 6, 2016, at 7:24 PM, Graham Cox  wrote:
> 
> Hi all,
> 
> My app uses [NSWorkspace openURL:] to display help pages in the user’s 
> default browser. Each new request creates a new tab (at least in Safari). Is 
> there a way to pass a hint that no new tab is created if there is an existing 
> tab for the same domain? I looked at NSWorkspace’s launch options but none of 
> those appear to apply.
> 
> If there’s no way we might need to consider a webview within the app instead, 
> but hoping that we can do it more easily.
> 
> —Graham
> 
> 
> 
> ___
> 
> 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/jens%40mooseyard.com
> 
> This email sent to j...@mooseyard.com


___

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

Re: Codesign broken in 10.11.4

[Kevin Meaney]

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 (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 the helper tools themselves and then the prefPane. So
> everything is signed from the inside-out.
> 
> In terminal (on two different machines running 10.11.3) I get:
> 
> spctl -a -t exec -vv My.prefPane
> 
>  /Volumes/Path/To//My.prefPane: accepted
>  source=Developer ID
>  origin=Developer ID Application: My Company, Inc.
> 
> codesign --verbose=4 --deep --strict My.prefPane
> 
>  /Volumes/Path/To//My.prefPane: valid on disk
>  /Volumes/Path/To//My.prefPane: satisfies its Designated Requirement
> 
> 
> In terminal (on two different machines running 10.11.4) I get:
> 
> spctl -a -t exec -vv My.prefPane
> 
>  /Volumes/Path/To//My.prefPane: rejected
>  source=obsolete resource envelope
>  origin=Developer ID Application: My Company, Inc.
> 
> codesign --verbose=4 --deep --strict My.prefPane
> 
>  /Volumes/Path/To//My.prefPane: valid on disk
>  /Volumes/Path/To//My.prefPane: satisfies its Designated Requirement
> 
> 
> The codesign command is taken directly from what Xcode uses:
> 
> codesign --force --sign "Developer ID Application: My Company, Inc."
> --requirements "=designated => anchor apple generic and identifier
> \"com.mycompany.myproduct.helper\" and ((cert
> leaf[field.1.2.840.113635.100.6.1.9] exists) or (certificate
> 1[field.1.2.840.113635.100.6.2.6] exists and certificate
> leaf[field.1.2.840.113635.100.6.1.13] exists and certificate
> leaf[subject.OU] = \"MYAPPLE123\"))" --timestamp=none
> "$BASEPATH/My.prefPane/Contents/Resources/MyHelper.app"
> 
> 
> When I run the above spctl terminal command on the helpers within the bundle
> on 10.11.4, the three helper app bundles are accepted but the command line
> tool is rejected with "obsolete resource envelope".
> 
> If I copy that command line tool to a 10.11.3 system and run spctl, it is
> accepted.
> 
> I have spent more than a day on this and am at a loss as to what is
> happening.
> 
> Any ideas?
> 
> 
> 
> 
> ___
> 
> 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/ktam%40yvs.eu.com
> 
> This email sent to k...@yvs.eu.com


___

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

Re: Codesign broken in 10.11.4

[John Pannell]

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 - hope this helps!

John

On Thu, Apr 7, 2016, at 08:13 AM, Trygve Inda wrote:
> 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 the helper tools themselves and then the prefPane. So
> everything is signed from the inside-out.
> 
> In terminal (on two different machines running 10.11.3) I get:
> 
> spctl -a -t exec -vv My.prefPane
> 
>/Volumes/Path/To//My.prefPane: accepted
>source=Developer ID
>origin=Developer ID Application: My Company, Inc.
> 
> codesign --verbose=4 --deep --strict My.prefPane
> 
>/Volumes/Path/To//My.prefPane: valid on disk
>/Volumes/Path/To//My.prefPane: satisfies its Designated Requirement
> 
> 
> In terminal (on two different machines running 10.11.4) I get:
> 
> spctl -a -t exec -vv My.prefPane
> 
>/Volumes/Path/To//My.prefPane: rejected
>source=obsolete resource envelope
>origin=Developer ID Application: My Company, Inc.
> 
> codesign --verbose=4 --deep --strict My.prefPane
> 
>/Volumes/Path/To//My.prefPane: valid on disk
>/Volumes/Path/To//My.prefPane: satisfies its Designated Requirement
> 
> 
> The codesign command is taken directly from what Xcode uses:
> 
> codesign --force --sign "Developer ID Application: My Company, Inc."
> --requirements "=designated => anchor apple generic and identifier
> \"com.mycompany.myproduct.helper\" and ((cert
> leaf[field.1.2.840.113635.100.6.1.9] exists) or (certificate
> 1[field.1.2.840.113635.100.6.2.6] exists and certificate
> leaf[field.1.2.840.113635.100.6.1.13] exists and certificate
> leaf[subject.OU] = \"MYAPPLE123\"))" --timestamp=none
> "$BASEPATH/My.prefPane/Contents/Resources/MyHelper.app"
> 
> 
> When I run the above spctl terminal command on the helpers within the
> bundle
> on 10.11.4, the three helper app bundles are accepted but the command
> line
> tool is rejected with "obsolete resource envelope".
> 
> If I copy that command line tool to a 10.11.3 system and run spctl, it is
> accepted.
> 
> I have spent more than a day on this and am at a loss as to what is
> happening.
> 
> Any ideas?
> 
> 
> 
> 
> ___
> 
> 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/johnp%2Blists%40peach.io
> 
> This email sent to johnp+li...@peach.io
___

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

Codesign broken in 10.11.4

[Trygve Inda]

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 the helper tools themselves and then the prefPane. So
everything is signed from the inside-out.

In terminal (on two different machines running 10.11.3) I get:

spctl -a -t exec -vv My.prefPane

   /Volumes/Path/To//My.prefPane: accepted
   source=Developer ID
   origin=Developer ID Application: My Company, Inc.

codesign --verbose=4 --deep --strict My.prefPane

   /Volumes/Path/To//My.prefPane: valid on disk
   /Volumes/Path/To//My.prefPane: satisfies its Designated Requirement


In terminal (on two different machines running 10.11.4) I get:

spctl -a -t exec -vv My.prefPane

   /Volumes/Path/To//My.prefPane: rejected
   source=obsolete resource envelope
   origin=Developer ID Application: My Company, Inc.

codesign --verbose=4 --deep --strict My.prefPane

   /Volumes/Path/To//My.prefPane: valid on disk
   /Volumes/Path/To//My.prefPane: satisfies its Designated Requirement


The codesign command is taken directly from what Xcode uses:

codesign --force --sign "Developer ID Application: My Company, Inc."
--requirements "=designated => anchor apple generic and identifier
\"com.mycompany.myproduct.helper\" and ((cert
leaf[field.1.2.840.113635.100.6.1.9] exists) or (certificate
1[field.1.2.840.113635.100.6.2.6] exists and certificate
leaf[field.1.2.840.113635.100.6.1.13] exists and certificate
leaf[subject.OU] = \"MYAPPLE123\"))" --timestamp=none
"$BASEPATH/My.prefPane/Contents/Resources/MyHelper.app"


When I run the above spctl terminal command on the helpers within the bundle
on 10.11.4, the three helper app bundles are accepted but the command line
tool is rejected with "obsolete resource envelope".

If I copy that command line tool to a 10.11.3 system and run spctl, it is
accepted.

I have spent more than a day on this and am at a loss as to what is
happening.

Any ideas?




___

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