![]() The only for sure error in the log directly related to my Automator script is: And today, those specific errors do not show up precisely when I'd expect them to (unlike their appearance seemed to be yesterday), but a bit later in time. There seem to be a significant number of those 67062 code validation errors which do not correspond in time to my running the Automator script. In trying your suggestions I spent more time looking at the system.log. ![]() Unfortunately, neither of your suggestions solved my problem.Īfter more research, I'm wondering if I'm barking up the wrong tree. ![]() Is there some way to tell Automator to accept this unsigned script or a command or switch I can put in my bash script to have it accepted?įor f in -overwrite_original -AllDates-=1 "$f" I tried to add the script or my Automator workflow to System Preferences > Security & Privacy > Privacy > Accessibility but the panel won't accept either. But the script is well know in photography circles and has been used by many to edit the EXIF information in image files. I had to bypass Gatekeeper to install it in Yosemite (10.10.5). (OSStatus error -67062.)" i.e., Code object is not signed.Ĭorrect, exiftool is not signed, and there is nothing I can do about that. ![]() When I look in the system.log I find: "The operation couldn’t be completed. I can run the well-respected perl script exiftool from the command line in Terminal and achieve the desired result, but when I incorporate it in Automator as a Service I get a generic error message and the perl script is not executed. ![]()
0 Comments
Leave a Reply. |