“codesign”

First off, I am rather new a Swift development. I come from a Microsoft C#.Net background.I wrote this applicaiton some time ago for MacOS 10.11 using some version of Swift. When I opened it in XCode 9.4 and coverted it to Swift 4 and then fixed all the errors I ran it. When the app instatiates NSOpenPanel I see three warnings that files are not found. These files were at one time on my computer. I have not yet found a way to clear these cached filenames.I would not be concerend about it except I am getting this weird errorerror: use of undeclared identifier '$arg' * thread #9, queue = 'quicklook.pluginload', stop reason = breakpoint 1.2 * frame #0: 0x00007fff64c7c1f6 libc++abi.dylib`__cxa_throw frame #1: 0x00007fff4a909c1f Security`Security::UnixError::throwMeNoLogging(int) + 61 frame #2: 0x00007fff4a6b7768 Security`Security::safeCopyFile(char const*, unsigned int, char const*, unsigned short) + 1174 frame #3: 0x00007fff4a6b6531 Security`Security::MDSSession::updateDataBases() + 1863 frame #4: 0x00007fff4a70

Hi,I'm trying to codesign a wflow file in a xxx.app bundle.I run the codesign -f -v -s Developer ID Application: xxxxxxx document.wflowBut everytime I get:document.wflow: replacing existing signature document.wflow: errSecInternalComponentWhen I try to remove the -f I get:document.wflow: is already signedBut when I run codesign -dv document.wflow I get:Executable=/private/var/folders/02/6nmx541x4rq4f6mz3n9__px40000gn/T/fxbundler5337258839194575333/images/image-2908348883327387593/PingID-TEST.app/Contents/Java/Uninstaller.app/Contents/document.wflow Identifier=document Format=generic CodeDirectory v=20200 size=168 flags=0x0(none) hashes=1+2 location=embedded document.wflow: no signature Info.plist=not bound TeamIdentifier=not set Sealed Resources=none Internal requirements count=1 size=168Please, any help appreciated. I'm sitting on this for the last couple of days with no luck.

Not sure to understand the interest of notarizations from some perspectives:- from an end-user perspective: if the Dummy is an application downloaded from the Internet. Are you sure you want to open it? dialog is still displayed, what's the point? Because this is the dialog itself that is annoying for 2 reasons: . the dialog is displayed even though the applications are codesigned. . the dialog steals the focus from the window hierarchy and never returns it correctly. Every single time.- from a security perspective: if the check is still only performed for downloads that have the quarantine flag set, then what kind of additional security is this adding? If I download a binary using curl, will Gatekeeper see anything?

Hi,I developed a JavaFX application and I build the .app using ant. This application will be dowloaded from our server and installed with dmg by the users. I want to avoid the message “This application was downloaded from the Internet. Are you sure you want to open it?” so I tried to sign it.This is what I did.1) I created a dev certificate with type “Mac Development” to test in Apple Site.2) I downloaded my certificate and the intermediate certificates (World Developer Relations Certificate Authority and Developer ID Certificate Authority)3) I added the 3 certificates in Keychain4) Steps to sign my app - codesign --force --verbose -s MyName (Code) MyApp.app/Contents/MacOS/libpackager.dylib - codesign --force --verbose -s MyName (Code)” MyApp.app/Contents/PlugIns/Java.runtime/ - codesign --force --verbose -s MyName (Code)” MyApp.app5) I verified it with - codesign -vv MyApp.app and the result was MyApp.app/: valid on disk MyAoo.app/: satisfies its Designated Requirement - s

I've reinstalled my product which contain a kext driver where in previous installation, the driver was manually approved.However, on the second installation it failes, due to kext signature rejection.I have seen in some places the same error, for example here: https://support.eset.com/kb6570, however even after clearing the kext_policy table in recovery mode, and approving the kext manually in settings --> security in the next boot, the kext still appears to be unapproved.For example, running kextutil provides the following:Kalyan:~ KalyanPentakota$ sudo kextutil /Library/Extensions/mycompanyAT.kext Kext rejected due to insecure location: <OSKext 0x7f8e9ff02e20 [0x7fffa11c8af0]> { URL = file:///Library/StagedExtensions/Library/Extensions/mycompanyAT.kext/, ID = com.mycompany.at } Kext rejected due to insecure location: <OSKext 0x7f8e9ff02e20 [0x7fffa11c8af0]> { URL = file:///Library/StagedExtensions/Library/Extensions/mycompanyAT.kext/, ID = com.mycompany.at } kext approval status in database:

I have been using Xcode and swift for a long time and testing on my iPad Pro but now it will not let me executed on it. It executes in the simulter but no longer on an actual device with Xcode 9.4.1. The bottom of the log is belowProbing signature of /Users/jack_reigh/Library/Developer/Xcode/DerivedData/FoodTracker-crswctreoaiwbvaadnltjzeyykfb/Build/Products/Debug-iphoneos/FoodTracker.app/Frameworks/libswiftCore.dylib /usr/bin/codesign '-r-' '--display' '/Users/jack_reigh/Library/Developer/Xcode/DerivedData/FoodTracker-crswctreoaiwbvaadnltjzeyykfb/Build/Products/Debug-iphoneos/FoodTracker.app/Frameworks/libswiftCore.dylib'/Users/jack_reigh/Library/Developer/Xcode/DerivedData/FoodTracker-crswctreoaiwbvaadnltjzeyykfb/Build/Products/Debug-iphoneos/FoodTracker.app/Frameworks/libswiftCore.dylib: code object is not signed at allCodesigning /Users/jack_reigh/Library/Developer/Xcode/DerivedData/FoodTracker-crswctreoaiwbvaadnltjzeyykfb/Build/Products/Debug-iphoneos/FoodTracker.app/Frameworks/libswiftCore.dyli

Creating package for Mac OS,I have application.app which is code signed successfully using codesign utility.When I create package using pkgbuild. it creates application.pkg properly which installs at /Applications dir.but when I run following command on installed application. codesign --verify --verbose application.app.I got error application.app: code object is not signed at all In subcomponent: Somehow pkgbuild is destroying my code signing.Any Guess?I am trying code sign using thirdpaty certificate not the apple dev I

I deleted my previous (large) post on this topic because I've made some progress, so this is an updated request for help.I am struggling with getting a MacOS app prepared for distribution outside the Mac App Store. I'm building under Xcode 8.3.3, under MacOS 10.12.6 (Sierra). I have two relevant targets in my project: the app itself, and a framework of my own creation, which incorporates some third party code (the AFNetworking framework and chromaprint framework for audio signal recognition, which expects a few dynamic libraries - .dylib files from the ffmpeg project).I am almost certain that that problems I see are related to these embedded frameworks and .dylib files. I have attempted to codesign these separately from the Xcode build process, which appears to work (but i'm not sure). For example:/usr/bin/codesign --force --sign Developer ID Application: <my company name and identifier code> --timestamp=none /usr/local/lib/libavcodec.57.61.102.dylib...seems to work, and when I check i

just got a new mac and now i get codesign errors. the time savedby a faster CPU is now burnt up fixing weird bugs related to codesigning.whatever.app: unknown error -1=ffffffffffffffffCommand /usr/bin/codesign failed with exit code 1it would be nice if apple had a verbose mode for this codesign command so we can trace the problemrather than saying unknown errorside note: for another account, i fixed the problem by regenerating signing certs and provisioning profiles.but this is for a client and they dont like us deleting certs because it disrupts other developers.there are various hints on this topic online and i have tried a bunch of them but no progress.same error always.i can codesign on my old mac. so the provisioning is correct. just not on this mac.should i return this new one to the apple store? it's real nice, but if ican't do critical operations...what we need is a verbose codesign mode for this type of thingthis is for production / upload to test flight b

I've built a Qt based application about to be submitted to App Store.Currently I am doing this:Build the application in Qt Creatior, which ends up with the application bundle prepared (MyApp.app)Run macdeploytool (part of Qt tools) to copy all required libraries and resources to application bundle (in Frameworks and Resources)Run codesign to sign the bundle (signing goes well wih all my identities)At this point the application bundle is perfectly fine (signed, sandboxed, etc.) and runs without any problem (in a sandbox, as expected).My question is: how can I create/generate the archive (pkg) which I can then submit to App Store using Application Loader, without going through Xcode automated process (build, sign, package)?Note please, I can build the application using Xcode, including signing and packaging (Archive), but point 2 above is not executed and as a result, application can't run, because of missing Qt libraries.Clarification: I distribute the Qt application under LGPL, hence I can't link sta