“codesign”

I also had this same problem. In my KeyChain I had 1700+ in the 'My Certificates' section, I delete all but the current Apple certs that I needed and it took my codesigning time down from 4mins to 3secs!

Answered #2 myself -- No because there is an ID appended which seems to be based on your cert/codesigning. Reference information here and here Still wondering about #1 though

This worked for my enterprise app: 0) downloaded latest xCode Created new provisioning profile, last one was 11/2020, so it was due anyway, reused the same certificate, just to make it easy. Re-signed the app using the new provisioning profile and Matt’s information, codesign -s “certificate in keychain” etc, including the generate-entitlement-der flag codesign-dvvvvv still shows version 20400, but the -7 and -6 are there now. re-package and redeploy app.

[quote='781889021, perdrix52, /thread/781889, /profile/perdrix52'] I want to add /usr/bin/codesign to the list but the gui window that pops up when I click on + doesn't seem to allow me to do that [/quote] That works for me (testing on macOS 15.4). Within the file sheet, press command-shift-G and enter /usr into the path. You can then navigate to /usr/bin and select codesign. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi, I still have the same error. Here is my procedure in detail Script editor: main.scpt save as application. I sign my code: codesign -s Developer ID Application -f --timestamp -o runtime /contents/Resources/Scripts/Main.scpt Error: Main.scpt: resource fork, Finder information, or similar detritus not allowed -xattr -cr Main.scpt I resign my code: codesign -s Developer ID Application -f --timestamp -o runtime /contents/Resources/Scripts/Main.scpt=OK CodeSign Main.scpt -vvvvvv = Main.scpt: valid on disk, Main.scpt: satisfies its Designated Requirement. Then I create the package with the tool : the macOS installer builder: https://medium.com/swlh/the-easiest-way-to-build-macos-installer-for-your-application-34a11dd08744 When the package is built, to execute it, I have to right click on it and open. The error message is displayed but I can execute package. I'd like no to display the error message :)

Are you using the Xcode provided switft toolchain or one from swift.org? It looks like the swift runtime in the toolchain is not codesigned. I remember this was an issue with some of the downloadable toolchains a few weeks ago.

Umm.. Yes.You set code sign identities inside Xcode using the Code Signing Identity properties on your targets.You can code sign on the command line using codesign.

@SridharRaj Could you help me? Where should I type this command? in the Terminal? Or is this a step giude? - codesign --force --deep --sign - /Applications/SpringToolSuite4.app I really appreciate if you could help me, I am totally rookie. Thank you!

Yes I'm referring to the files inside the .app. We need this info for statistics and create if possible also the reports. We execute the codesign inside a CI pipeline. Thanks

I’ve seen problems like this before. In one case it was because the developer was passing multiple subcommands to the codesign command. That is, they were passing in --sign (aka -s) and --verify (aka -v) to the same codesign invocation, and that caused weird issues. And the solution was to stop doing that (-: However, the most common cause is that the app doesn’t follow the rules in Placing content in a bundle or you’re not following the steps to sign nested code in Creating distribution-signed code for macOS. Consider this example: % mkdir -p MyTrue.app/Contents/MacOS % cp /usr/bin/true MyTrue.app/Contents/MacOS/MyTrue % cp /usr/bin/false MyTrue.app/Contents/MacOS/MyFalse % codesign --remove-signature MyTrue.app/Contents/MacOS/MyFalse % codesign --remove-signature MyTrue.app/Contents/MacOS/MyTrue % codesign -s - MyTrue.app MyTrue.app: code object is not signed at all In subcomponent: /Users/quinn/Test/MyTrue.app/Contents/MacOS/MyFalse This bundle structure is corr

so I run the command.$ codesign -d --entitlements :- /path/to/your.appand what? What is that useful for? how do I know I have the right entitlements, the my entitlements need special configuration so that KeyChain works? I dont understand.

I checked entitlements with the codesign command and it looks like my app is correctly entitled: application-identifierZ9FYRK8P89.com.imeve.avpenterprisetestcom.apple.developer.arkit.main-camera-access.allowcom.apple.developer.screen-capture.include-passthroughcom.apple.developer.team-identifierZ9FYRK8P89get-task-allow