3 ms·

I can't seem to open it; I keep getting this message: > “MeetingBar” can’t be opened because Apple cannot check it for malicious software. > This software nee

by Varauk 6y ago

I can't seem to open it; I keep getting this message: > “MeetingBar” can’t be opened because Apple cannot check it for malicious software. > This software needs to be updated. Contact the developer for more information. Both if I use brew or manually download it.

leits 6y ago
Apple isn't very friendly to software distributed outside of AppStore. For installing it you need to: Allow installing software outside of AppStore before installation Allow opening the app from Preferences after installation Follow this official from Apple Support to do this: https://support.apple.com/en-us/HT202491c https://support.apple.com/en-us/HT202491c
floatingatoll 6y ago
This error occurs on default macOS when using software precompiled on another computer, when the person who compiled and released that software has not signed up for an Apple Developer account and submitted the precompiled bundle for notarization, one of Apple's anti-malware prevention mechanisms. https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution https://developer.apple.com/documentation/xcode/notarizing_m... You can usually work around it by right-clicking the app and choosing Open, which usually triggers a special approval dialog. You should generally use caution when doing so, as you're granting an arbitrary binary whose contents you are unlikely to verify access to your private data. ps. Developers, automating this process as part of your releasing is relatively easy, assuming you have a paid Developer account. The shell script at this link is accompanied by a clear walkthrough, and can be adapted to most workflows run locally on a machine containing your signing keypair. (And if your precompiled binary or bundle was not built with Xcode, you would skip the “xcodebuild” step.) https://scriptingosx.com/2019/09/notarize-a-command-line-tool/ https://scriptingosx.com/2019/09/notarize-a-command-line-too...

by Varauk 6y ago

leits 6y ago

Apple isn't very friendly to software distributed outside of AppStore. For installing it you need to: Allow installing software outside of AppStore before installation Allow opening the app from Preferences after installation Follow this official from Apple Support to do this: https://support.apple.com/en-us/HT202491c https://support.apple.com/en-us/HT202491c

floatingatoll 6y ago

This error occurs on default macOS when using software precompiled on another computer, when the person who compiled and released that software has not signed up for an Apple Developer account and submitted the precompiled bundle for notarization, one of Apple's anti-malware prevention mechanisms. https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution https://developer.apple.com/documentation/xcode/notarizing_m... You can usually work around it by right-clicking the app and choosing Open, which usually triggers a special approval dialog. You should generally use caution when doing so, as you're granting an arbitrary binary whose contents you are unlikely to verify access to your private data. ps. Developers, automating this process as part of your releasing is relatively easy, assuming you have a paid Developer account. The shell script at this link is accompanied by a clear walkthrough, and can be adapted to most workflows run locally on a machine containing your signing keypair. (And if your precompiled binary or bundle was not built with Xcode, you would skip the “xcodebuild” step.) https://scriptingosx.com/2019/09/notarize-a-command-line-tool/ https://scriptingosx.com/2019/09/notarize-a-command-line-too...