My app can't be checked for malicious software?

I'm working on an app that I intend to publish online. The app is a bit odd - it's built by compiling executables directly from a Makefile, then placing them, an icon, a launch .sh, and an Info.plist into a bundle.

I've tried code-signing this app with my personal development certificate. This seems to work fine, except in some cases, others are forced to navigate to their Preferences and manually authorize the app as it's from an 'unidentified developer', or macOS Big Sur claims that it can't check the app for malicious software and that it needs to be updated.

What do I need to do? codesign --verify says that my app fulfills all requirements.
Accepted Answer

a launch .sh

But this do you mean that you’ve put a shell script in Contents/MacOS/ and then set CFBundleExecutable to point to that? If so, I recommend against that. Historically macOS was accepting of such a setup but in recent releases it’s started to cause problems.

What I recommend instead is that you put your main executable in Contents/MacOS/ directly.

Beyond that, you can find my general advice on this topic in Signing a Mac Product For Distribution.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
My app can't be checked for malicious software?
 
 
Q