I am using codesign with —deep option.
我使用的是codesign -deep选项。
/usr/bin/codesign --verbose --force --sign "Developer ID Application: myCompany” —deep myApp.app
on 10.8 its working fine
10.8它的工作状态良好。
$ codesign -vvv myApp.app
myApp.app: valid on disk
myApp.app: satisfies its Designated Requirement
But on 10.9 i am getting nested code is modified or invalid.
但是在10.9中，我得到的嵌套代码被修改或无效。
$ codesign -vvv myApp.app
myApp.app: nested code is modified or invalid
file modified: myApp.app/Contents/MacOS/SecondUtility
I have two executable in MacOS folder, one is from build phase(Destination: executables)
我在MacOS文件夹中有两个可执行文件，一个来自构建阶段(目标:可执行文件)
$codesign -vvv myApp.app/Contents/MacOS/SecondUtility
myApp.app/Contents/MacOS/SecondUtility: valid on disk
myApp.app/Contents/MacOS/SecondUtility: does not satisfy its designated Requirement
Run Script with the code sign shell command is also not working for me.
使用代码签名shell命令运行脚本也不适合我。
Can anyone please help me out?
有人能帮帮我吗?
1 个解决方案
#1
2
After creating build in Xcode 5, again code sign SecondUtility and myApp.app.
在Xcode 5中创建了构建之后，再一次代码签署了第二项功能和myApp.app。
sudo /usr/bin/codesign --verbose --force --sign "Developer ID Application: myCompany" myApp.app/Contents/MacOS/SecondUtility
sudo /usr/bin/codesign --verbose --force --sign "Developer ID Application: myCompany" myApp.app
Now its working fine.
现在它的工作好。
Run Script with the code sign shell command is not working for me.
使用代码符号shell命令运行脚本对我不起作用。
EDIT
编辑
Have a look at OS X Code Signing In Depth
深入了解OS X代码签名吗?
Beginning with OS X version 10.9.5, there will be changes in how OS X recognizes signed apps
从OS X版本10.9.5开始，OS X如何识别已签名的应用程序将会发生变化。
Structure your bundle according to the expectations for OS X version 10.9 or later:
根据对OS X version 10.9或更高版本的期望来构造您的包:
- Only include signed code in directories that should contain signed code.
- 只在应该包含有符号代码的目录中包含已签名的代码。
- Only include resources in directories that should contain
resources. - 只在应该包含资源的目录中包含资源。
- Do not use the --resource-rules flag or ResourceRules.plist. They have been obsoleted and will be rejected.
- 不要使用——资源规则标志或资源。他们已被淘汰，将被拒绝。
#1
2
After creating build in Xcode 5, again code sign SecondUtility and myApp.app.
在Xcode 5中创建了构建之后，再一次代码签署了第二项功能和myApp.app。
sudo /usr/bin/codesign --verbose --force --sign "Developer ID Application: myCompany" myApp.app/Contents/MacOS/SecondUtility
sudo /usr/bin/codesign --verbose --force --sign "Developer ID Application: myCompany" myApp.app
Now its working fine.
现在它的工作好。
Run Script with the code sign shell command is not working for me.
使用代码符号shell命令运行脚本对我不起作用。
EDIT
编辑
Have a look at OS X Code Signing In Depth
深入了解OS X代码签名吗?
Beginning with OS X version 10.9.5, there will be changes in how OS X recognizes signed apps
从OS X版本10.9.5开始，OS X如何识别已签名的应用程序将会发生变化。
Structure your bundle according to the expectations for OS X version 10.9 or later:
根据对OS X version 10.9或更高版本的期望来构造您的包:
- Only include signed code in directories that should contain signed code.
- 只在应该包含有符号代码的目录中包含已签名的代码。
- Only include resources in directories that should contain
resources. - 只在应该包含资源的目录中包含资源。
- Do not use the --resource-rules flag or ResourceRules.plist. They have been obsoleted and will be rejected.
- 不要使用——资源规则标志或资源。他们已被淘汰，将被拒绝。