Mac throws warning about this software
alongouldman opened this issue · 27 comments
I get this message, when trying to open this app:
This is strange, because this didn't happen in the past, but started now.
I wish this will be fixed - I love this software!!
@jasonm23 Can I Ignore this somehow? Or add this to app store?
Unfortunately it's happening for me too. So far, I didn't found a (working) workaround.
The only way I found was to right click on cutbox > Information > Override malware protection. But that only helped to get rid of the message. Cutbox doesn't start after that.
Exactly the same for me. I was spending all of yesterday trying to find replacement for this app, but with no luck. I hope this will be fixed sometime...
console when over-riding malware protection:
default 11:59:50.283869-0500 lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "The file “PlugIns” couldn’t be opened because there is no such file." UserInfo={NSURL=PlugIns/ -- file:///Applications/CutBox.app/Contents/, NSFilePath=/Applications/CutBox.app/Contents/PlugIns, NSUnderlyingError=0x7fc8fc329a00 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
default 11:59:50.284015-0500 lsd - 45683955: Checking whether application is managed at file:///Applications/CutBox.app/info.ocodo.CutBox
default 11:59:50.305978-0500 lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "The file “PlugIns” couldn’t be opened because there is no such file." UserInfo={NSURL=PlugIns/ -- file:///Applications/CutBox.app/Contents/Library/LoginItems/CutBoxHelper.app/Contents/, NSFilePath=/Applications/CutBox.app/Contents/Library/LoginItems/CutBoxHelper.app/Contents/PlugIns, NSUnderlyingError=0x7fc8fb628840 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
default 11:59:50.306047-0500 lsd - 45683955: Checking whether application is managed at file:///Applications/CutBox.app/Contents/Library/LoginItems/CutBoxHelper.app//info.ocodo.CutBoxHelper
default 11:59:50.327800-0500 Finder LAUNCHING:0x0-0x68068 CutBox foreground=0 bringForward=0 seed=237 userActivityCount=0
default 11:59:50.350507-0500 amfid /Applications/CutBox.app/Contents/MacOS/CutBox signature not valid: -2147409652
default 11:59:50.362761-0500 kernel mac_vnode_check_signature: /Applications/CutBox.app/Contents/MacOS/CutBox: code signature validation failed fatally: When validating /Applications/CutBox.app/Contents/MacOS/CutBox:
The code contains a Team ID, but validating its signature failed.
Please check your system log.
default 11:59:50.362792-0500 kernel proc 2950: load code signature error 4 for file "CutBox"
default 11:59:50.363276-0500 kernel Security policy would not allow process: 2950, /Applications/CutBox.app/Contents/MacOS/CutBox
default 11:59:50.366189-0500 loginwindow -[ApplicationManager checkInAppContext:eventData:] | ApplicationManager: Checked in app : CutBox
default 11:59:50.371581-0500 ReportCrash Parsing corpse data for process CutBox [pid 2950]
default 11:59:50.371345-0500 loginwindow -[PersistentAppsSupport applicationQuit:] | for app:CutBox, _appTrackingState = 2
default 11:59:50.415709-0500 dmd Received xpc stream event (distributed notification matching) with name: com.apple.LaunchServices.applicationRegistered user info: {
bundleIDs = (
"info.ocodo.CutBox"
);
isPlaceholder = 0;
}
default 11:59:50.415954-0500 dmd Received xpc stream event (distributed notification matching) with name: com.apple.LaunchServices.applicationRegistered user info: {
bundleIDs = (
"info.ocodo.CutBoxHelper"
);
isPlaceholder = 0;
}
Note I created the missing PlugIns directories listed and it had no difference.
This really sucks. CutBox has been awesome and even the crashes were possible to workaround.
Thanks for the additional information. It may be possible to overcome this.
It looks like a louder fail message concerning application signing.
So it may be possible to fix it.
I'm in the process of updating the libraries and updating to Swift 5, so I can rebuild. Hopefully this is fixable.
load code signature error
This is the breadcrumb we needed.
As a note my old install of FlyCut still works. (It's nowhere near as useful as CutBox though.)
Cutbox is the only working alternative I could find after switching from Windows to Mac, and now this malware warning. Any chance it can be fixed?
Maybe this is helpful:
Notarized macOS builds
https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution
Saw that in the recent VSCode update.
@levjad - BTW since I don't participate in the Apple Developer program I cannot notarise builds, but it seems to be ok without on a clean MacOS that's unrelated to the dev machine. Hope 1.4.6 works for you.
1.4.7 pre-release is now available from the release page
It solves the problem on macOS Catalina 10.15.4 (MBP 15" 2019). Thank you !
@theofruitrouge that's good news.
I'll slice off a proper release and update the landing page.
1.4.8 official release now available
Sorry about the wait!
why me? :(
@theofruitrouge please post your Catalina about window to compare with @hanan-simplee
Thank you.
Oh sorry folks, check this post to display build number of macos.
Hi,
Sorry about the little delay.
Here it is :
Maybe it has to do with the fact I have disabled Gatekeeper, and the Cutbox app could be somewhat "whitelisted" (I opened it in the past with: Right clic > Open). I also tried to deactivate various securities from macOS to try to have Cutbox working some weeks ago . It might be related.
This is mine. 10.15.4 (19E287) - so it does look the same.
Update: looks like it's working and even updated itself to 1.4.9
I'm not sure exactly what changed. I removed and downloaded again, and at some point saw that the "can't be open" message changed and had an "open" button... and it worked.
As you will see above this is a problem on Apple side.
If the situation gets worse I will simply pull the binary releases altogether, and provide a brew style method of installation. Giving users a compile and use their own binary option.