“codesign”

Since I updated my Mac to Sierra, attempting to codesign anything (for OSX) results in an error message Trace/BPT trap: 5Internet searching seems to indicate this error message is related to dynamic libraries, but running otool -L did not tell me anything that is missing, i.e. I go this:> otool -L /usr/bin/codesign/usr/bin/codesign: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1348.28.0) /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 57740.31.2) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.4.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0)All those files are available on my system.When I run codesign -s with the same developer ID as always (which keychain says is valid through 2019) all I see is that Trace/BPT trap: 5 message with no explanation. I've attempted t

Sigil (https://github.com/Sigil-Ebookl/Sigil) is a Qt cross-platform epub2 and epub3 editor on Mac OS X / Windows / Linux. It embeds a relocatable Python3 framework inside Sigil.app on OSX.The OS X Code signing works for Sigil.app and for the dmg used to distribute it but upon first launch the internal embedded Python3 interpreter creates *.pyc compiled python code files inside various __pycache__ directories inside the Python.framework stored inside the Sigil.app.This causes further code-sign testing to fail with files added messages error messages as follows:codesign --verify --deep --strict --verbose=2 Sigil.app--prepared:/Applications/Sigil.app/Contents/Frameworks/Python.framework/Versions/Current/.Sigil.app: a sealed resource is missing or invalidIn subcomponent: /Applications/Sigil.app/Contents/Frameworks/Python.frameworkfile added: /Applications/Sigil.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python3.5/__pycache__/__future__.cpython-35.pycfile added: /Applications/Sigil.app/Contents

HiToday I signed an app, so people who use my app, wont get a pop-up about an unidentified developer.The app used to run without any problems, if you just press'ed run anyway, when the pop-up show. But now that I have signed the app, it wont run at all. The icon just keep bouncing and then after some time say that the application wont respond.I have developed the app in Qt and have used this to sign the applicatio:codesign --force --verify --verbose --sign My Developer ID ./MyApp.appfind MyApp.app -name *.dylib | xargs -I $ codesign --force --verify --verbose --sign My Developer ID $find MyApp.app -name Qt* -type f | xargs -I $ codesign --force --verify --verbose --sign My Developer ID $*I have changed the Developer Id and the AppNameThe App is a Mac app that should be able to download from the internet and not from App Store.Hope someone can help me.Thanks in advance.

Hello,I'm making a game with Unity and trying to sign the installer.I'm able to create my game.app file, sign it with 3rd Party Mac Developer Application using codesign tool and create an installer using productbuild tool.However, to sign an installer I need a Developer ID Installer Certificate that only the Team Agent of my company can make.My team role is Admin, but the option to Download this certificate is disabled, and the Team Agent can't export the certificate to send it to me (.p12 option is greyed out).Did I miss any step? How can I obtain this certificate (with it's private key) so that I can sign the game.pkg installer?Thanks in advance,IsmaelEdit: Only the .p12 option is greyed out.

I have built an installer (.pkg) for a signed application using PACKAGES. It works on 10.11 and the latest.This installer had been signed using codesign...When distributed the the .pkg when run causes Gatekeeper to display unknown developer message... we checked and everything is current. Anyone run into this and fixed the problem? please share what you did to solve this. We are stuck. when we try to resign it responds that the installer is already signed.Thanks.

Summary:I can not find a solution to this problem! When I compile any project (with this paid developer account) for a physical device (iPhone), in this case a simple ViewController with a HelloWorld label, the error is always the same:Error: Task failed with exit 0 signal 5 { / Usr / bin / codesign '--force' '--sign' '8581983B1080ABA9D731EE6CEBF1F3E8697C6009' '--verbose' '/ Users / antoniopinto / Library / Developer / Xcode / DerivedData / TestHello2-cqliftzommantyftlspfphtoysir / Build / Products / Debug-iphoneos / TestHello2.app/Frameworks/libswiftCore.dylib ' } I copied the project to a Mac Mini and with the same account works perfectly!!!!I want to test an app (simple Hello) on the device (iPhone) with a paid developer account I've tried using clean, hard clean, xattr -rc and nothing worked Tanks Steps toReproduce: Simply compile and run the project to a physical device

Before updating to xcode 8.3, I was able to export an unsigned macOS App like this:xcodebuild -exportArchive -exportFormat app -archivePath ${ARCHIVE_DIR}/${APP_NAME}.${version}.xcarchive -exportPath ${RELEASE_APP_DIR}/${version}/${APP_NAME}.appNow the -exportFormat option is not allow and -exportOptionsPlist is required. I tried switching to using -exportOptionsPlist, but I am getting the following error:No 'teamID' specified and no team ID found in the archiveSince I am releasing the App in an enterprise environment, I need to use a special codesigning mechanism, because I am not allowed to directly access the private key for the codesigning certificate. I need to be able to export the archive unsigned, so that I can sign it outside of xcode. How do I do this?thanks,-Nathan

I have had an ongoing problem with codesigning my applications. When a user downlaods one of my .apps that is codesigned correctly it still doesnt recognize it. I have tried everything and I cannot server my files without zipping them because they are large. I have read from many posts that this is a bug with Apple Gatekeeper. Is there a way to codesign my apps and have them successfuly zipped while still preserving its attributes. When users click to run my app it will say it is damage. The only options are to have my users disable their Gatekeeper via: sudo spctl --master-disable or have them run xattr -cr MYAPP.app. This is ridiculous to have users pull up their terminal to get an application to run. Does anyone have a solution for this, I have been looking forever and finally found that zipping my codesigned app is the issue. I have seen plenty of people who have had the same problem but everything that is suggested never seems to work.