On 2013 Nov 05, at 03:39, Jakob Egger wrote:
> In my app I just specified --deep and it seems to work!
No, Seth is correct. It might “seem" like it works, but when a user downloads
your app, it will be quarantined and Gatekeeper will block it. To properly
test, use the command-line tool spc
When you use —deep, "all signing options you specify [on the app bundle] will
apply, in turn, to such nested content [as embedded frameworks, helpers,
resources, etc]” which is not the correct thing that should happen.
https://devforums.apple.com/thread/203126?start=0&tstart=0
--
Seth Willits
Does anybody know why just specifying "--deep" in "Other Code Signing Flags" is
wrong? Is it only a problem with Sparkle, or is there a general problem?
In my app I just specified --deep and it seems to work!
On 29 Oct 2013, at 10:37 pm, Shazron wrote:
> See http://furbo.org/2013/10/17/code-si
On 29 Oct 2013, at 10:37 pm, Shazron wrote:
> See http://furbo.org/2013/10/17/code-signing-and-mavericks/ he specifically
> deals with your Sparkle.framework problem
Brilliant
You have saved my life (this week at any rate).
—Graham
___
Coc
See http://furbo.org/2013/10/17/code-signing-and-mavericks/ he specifically
deals with your Sparkle.framework problem
On Tue, Oct 29, 2013 at 5:30 PM, Graham Cox wrote:
> Having just updated to Xcode 5.0.1, I can’t build one of our apps because
> it uses the Sparkle framework, which isn’t codes
On Tue, 29 Oct 2013 22:30:47 +0100, Graham Cox said:
>Having just updated to Xcode 5.0.1, I can’t build one of our apps
>because it uses the Sparkle framework, which isn’t codesigned.
>Previously this wasn’t an issue but it seems Xcode is being a bit
>stricter than before.
>
>Is there a way I can
Having just updated to Xcode 5.0.1, I can’t build one of our apps because it
uses the Sparkle framework, which isn’t codesigned. Previously this wasn’t an
issue but it seems Xcode is being a bit stricter than before.
Is there a way I can codesign this module using my own credentials? I have
lit
