Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
- Subject: Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
- From: Markus Spoettl <email@hidden>
- Date: Tue, 27 Sep 2016 22:54:51 +0200
On 27/09/16 22:39, Chris Hanson wrote:
How are you getting the URL that you pass to represent your application?
Could it be that you’re constructing the URL from a relative path when run
from the command line, rather than the full path? (You can’t depend on being
run from any particular working directory.)
Not sure what you mean by URL, I'm merely executing the app's executable from
the command line. Assuming the My.app bundle is located in
"~/Projects/My/Debug", I cd into "~/Projects/My" and execute
"./Debug/My.App/Contents/MacOS/My".
I'm starting the app from the command line in cases when I want to test a
certain localization using the -AppleLanguages '(xx)' command line option, which
is quite handy.
As I said this used to work fine, but now the code signing signature is being
rejected. However, using the "open" command works fine for me.
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden