@d-healey but if that's the problem I had to recompile hise. xcode10.1 + command tools 10.1

it made me the same. c is that the command tools was not the correct one for xcode

@Tania-Ghosh Make sure you have xcode installed and its command line is important. if you are using ipp check that everything is correctly installed. to export directly from hise you don't need to sign. remember to save your ID certificates and applications and especially their keys in the keychain glass. I made the mistake of creating 5 certificates of each I am blocked, I lost my keys I can no longer sign or notarize my work. and the apple support service is a real shit ^^

@Tania-Ghosh I noticed that too. personally I downloaded juce directly from the merchant site.

@arminh here is something reassuring then. I have a beta tester with an apple M1 it cannot run my test plugin with LOGIC. then my problem must be the notarization

will plugins or vst instruments work on M1 processors if they were developed on an intel processor?

@Lindon what do you call assigned plugin id? so precisely if it works on logic it will work everywhere ^^ I came back to the pkg problem. it is not possible for me to affix the certificate. it tells me that it cannot be used to sign a package or distribution because there is no associated private key. this story of notarization sincerely is really a crazy thing

@d-healey I cannot staple the .zip. I sent it to my beta tester. so good news my plugin is displayed as verified in the list of plugins (logic). but impossible to open it. to put it simply, logic recognizes it but when you want to create a new instrument on a track, my plugin does not exist

@Lindon @d-healey I just tried to directly notarize the plugin in a .zip. it worked without any problem. I will continue to know why the pkg is not working. last question. So can I distribute the .zip? (the same one I used to notarize?)

@Lindon yes I had already noticed the small label which somehow validates. but strangely, it is impossible for me to affix a certificate. I have the following response from whitebox>

The "Developer ID Installer: myname (7 *********)" certificate available in the keychain cannot be used to sign a package or a distribution. There is no private key associated with the certificate .