Following your suggestions, I try to reproduce the context of the crash as much as possible. I started with macOS 13 because I realized that the test I'd already done on Ventura was inconclusive because I was using a free demo plugin that wasn't authorized with iLok. Fortunately, other demo versions using iLok exist, so I’ll try this way. If the bug is not reproductible on Ventura, I'll consider downgrading to macOS 12 or installing it on an external drive. All this is time consuming, but hopefully I'll have more info in a few days. If so, I'll share them here. Anyway, thanks for your help!

Oups, sorry for that ! (once opened in a text editor, such a report becomes difficult to read...) Ok, since the same beta tester was here today, we tried again the whole sequence of operations and I have some more precise results: Actually, the most common bug I describe in my first message don't produce any crash report. They just produce a big binary file (that seems to be an image of the bundle, I could upload it if you want) saved in the temp folder of the host application, display a first warning described in my previous message, and finally this one: Even if the application didn't crash, we were not able to open any of these plugins with my application (practically they are unusable). I don't know if it could help, but it appears that all of these plugins are protected by iLok keys (https://www.ilok.com). Moreover they all open without problem in Logic Pro and Ableton Live. On the other hand, the partial crash report I joined was related to an issue having some specificities: it also crashed the host application so that it produced a crash report. This second category seems related to less plugins, all related to the same manufacturer. It could be a problem of the plugin itself, however we were also able to open such plugins in Logic Pro without encountering the same issue. I join a new report produced with a plugin of the latter type: anonymous.crash

Yes it's the name of the plugin (an emulation of a famous Solid State Logic mixer), not something from my application. I join the full report, anonymized as indicated in the instructions. Initially it's a file with the .ips extension (coming from the Console app), but because it was not possible to join it, I changed the extension to .crash. Thanks! Anonymous Crash Report.crash

The warning appears when trying to create an instance of any audio unit provided by some specific manufacturers and to open it in its editor (both things being merged as a single operation). The message body was followed by another sentence : macOS cannot verify that this app does not contain any malicious software and created this file today at 15:32 The file in question was a file called NSCreatedObjectFileImageFromMemory-p47UEwps stored in the temporary directory (-[NSURL temporaryDirectory]) of the host application. The panel buttons proposed either to trash the file or to cancel. Whatever the button clicked, a second dialog appears with an exclamation mark in a red icon and the Fatal Error 100001 message, and the plugin never opened (but the host application didn't crash). Here is a part of the crash report (if you want, I can send the full report to your email address): Date/Time: 2023-08-24 15:04:45.7209 +0200 OS Version: macOS 12.5.1 (21G83) Report Version: 12 Bridge OS Version: 6.6 (19P6066) Anonymous UUID: 0495D4E2-3107-8006-D560-7301560EB3CE Sleep/Wake UUID: 2CFC336A-EB4A-4493-BB08-8CCCBA20E12F Time Awake Since Boot: 73000 seconds Time Since Wake: 596 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000137c7cc34 Exception Codes: 0x0000000000000002, 0x0000000137c7cc34 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10 Terminating Process: exc handler [41378] VM Region Info: 0x137c7cc34 is in 0x137bb1000-0x137cc9000; bytes after start: 834612 bytes before end: 312267 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL mapped file 135c56000-137773000 [ 27.1M] r--/rwx SM=COW ...t_id=d8860195 GAP OF 0x43e000 BYTES ---> __TEXT 137bb1000-137cc9000 [ 1120K] r-x/rwx SM=COW ...le SSL 4000 G __DATA 137cc9000-137cf5000 [ 176K] rw-/rwx SM=COW ...le SSL 4000 G Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 bx_console SSL 4000 G 0x137bdf476 0x137bb1000 + 189558 1 bx_console SSL 4000 G 0x137c7e739 AUV2AdapterEntry + 439641 2 dyld 0x1148ca334 dyld4::RuntimeState::notifyObjCInit(dyld4::Loader const*) + 170 3 dyld 0x1148cff03 dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const + 167 4 dyld 0x1148cffb2 dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const + 108 5 dyld 0x1148dee00 dyld4::APIs::dlopen_from(char const*, int, void*) + 592 6 CoreFoundation 0x7ff815cd6994 _CFBundleDlfcnLoadBundle + 149 7 CoreFoundation 0x7ff815d5094f _CFBundleLoadExecutableAndReturnError + 484 8 AudioToolboxCore 0x7ff81712efa5 APComponent_FromBundle_Loadable::ResolveFactoryFunction() + 67 9 AudioToolboxCore 0x7ff81712ded2 APComponent::newInstance(unsigned int, bool, void (OpaqueAudioComponentInstance*, int) block_pointer) + 126 10 AudioToolboxCore 0x7ff817223c90 instantiate(OpaqueAudioComponent*, unsigned int, bool, void (OpaqueAudioComponentInstance*, int) block_pointer) + 311 11 AudioToolboxCore 0x7ff81722402c __AudioComponentInstanceNew_block_invoke + 88 12 AudioToolboxCore 0x7ff8170b5479 Synchronously + 87 13 AudioToolboxCore 0x7ff817223ee2 AudioComponentInstanceNew + 183 14 <AppName> 0x10f9274e3 mx::EditableDevice::instanciate(AudioComponentDescription*, unsigned short, unsigned char) + 77 15 <AppName> 0x10f9273cf mx::EditableDevice::EditableDevice(mx::MixerBase*, AudioComponentDescription*, unsigned short, bool) + 101 16 <AppName> 0x10f9087ab mx::Insert::Insert(mx::MixerBase*, AudioComponentDescription*, unsigned char, unsigned char, unsigned char) + 41 17 <AppName> 0x10f90e957 mx::Track::insertEffectAtIndex(unsigned long long, unsigned char, unsigned char, unsigned char, unsigned char) + 559

Thanks for you reply. I tested one of these plugins on an intel iMac running macOS 10.15 without problem. Today, I also tested the same plugin on an intel iMac running macOS 13.2.1 and it opened normally. So, no, I wasn't able to reproduce the bug. But it could be due to the fact that the systems I used was different (unfortunately I don't have a machine running macOS 12 here). For Catalina, the result is probably related to the fact the system is less secure than Monterey, but for Ventura it's unclear if it's related to the plugin, the hardware or the system. I also forgot to say that, during this beta testing session, we tried to disable Gate Keeper on the beta tester machine using the 'sudo spctl --master-disable' command, and that was successful. This seems to confirm your assumption. Knowing that, do you think there is a possible workaround using some other entitlements ? dp