Apple team ID, code sign but ask for security to open the plugin

[Yannrog]

@Oli-Ullmann It seems to work. I have status accepted. God bless you.

[Yannrog]

@Oli-Ullmann @David-Healey

What is the command to verify if it is code signed ? thank you

[David Healey]

@Yannrog Can't remember, but there's some useful apps here that will give you the info https://forum.hise.audio/topic/14860/couple-of-handy-free-mac-apps-for-checking-code-signs-and-notarisation

[ustk]

@Oli-Ullmann I shouldn't need to remove the old signature prior to signing again.
The new codesign process warns you about the existing signature and automatically replaces it.

[Yannrog]

@David-Healey works well

[Oli Ullmann]

@ustk
What do you mean by “new codesign process”? The new notary tool?

[ustk]

@Oli-Ullmann no I just mean when you codesign again, the previous signature should be replaced. That's what I do with no issues.

[ustk]

@Oli-Ullmann

VST and AU:

Running: codesign --deep --force --timestamp --options runtime --sign "Developer ID Application: XXXXXXXXXXX" "/Library/Audio/Plug-Ins/Components/MyPlugin.component" --verbose

/Library/Audio/Plug-Ins/Components/MyPlugin.component: replacing existing signature
/Library/Audio/Plug-Ins/Components/MyPlugin.component: signed bundle with Mach-O universal (x86_64 arm64) [com.studio427audio.myplugin]

And AAX:

Warning! This binary has an invalid existing platform digital signature.
  This situation could happen if you wrapped a binary that was already signed.
  Regardless, a new signature will be created now, using your specified credentials.

[Oli Ullmann]

@ustk
I see. Your command looks a little different from mine. I'll try it next time. Maybe it'll work for me then, too. Thanks a lot! :-)

[dannytaurus]

@Oli-Ullmann The --force flag overwrites any existing signature.

[Oli Ullmann]

@dannytaurus
Thanks for the info! :-)