I have a custom bundle of command line executables and its dependent libraries. I packaged them in a zip. Codesigned all the "Mach-O" files; the notarization went fine. The notarized zip is intended to be distributed via web, i.e. s3. When testing the zip downloaded from web, I see the dialog box about '"xyz" cannot be opened because the developer cannot be verified' for a handful of the executables.
What is interesting is that, some of the executables do not trigger the developer identity dialog box. It seems to be rather inconsistent. I double checked to ensure all these files are codesigned.
Does anybody have an idea what might be causing this issue?
What is interesting is that, some of the executables do not trigger the developer identity dialog box. It seems to be rather inconsistent. I double checked to ensure all these files are codesigned.
Does anybody have an idea what might be causing this issue?