Nicolas Goutte

Yes, there are teacher serial numbers.

No, it is linked to the serial number, if VW is in Pro mode oder in Student mode (or in Teacher mode, which is in-between)

I have been thinking during the weekend, why apparently we have no such problems (apart not signing our plugins). I have realized that we use the BuildVWR script, even in Debug, as PostBuild-Step. That means an intermediary step between editing and the created plug-in, even inside a .vwr folder. Alternatively, you could try using editors not creating resources, but that would probably mean you have to change your tools, so that is probably not a realistic option.

For compiling the plug-ins, you do not need to sign them. As far as I understood, Xcode has a switch somewhere.

Double-check that VW really uses that serial number.

Crashes when switching between 2D and 3D (or vice-versa) are often due to GPU problems. Have you set your system explicitly so that VW uses the good graphic card of your computer (and not the onboard GPU)?

No, see

The rule of thumb is: you need notarization if you use Apple tools that trigger GateKeeper. As VW unzips the file by its own mean, not by Apple tools, Gatekeeper is not triggered and therefore the notarization is not needed. (However, that is a reason (at least for C++-plugins) why VW must advertise that it loads extra code outside the app bundle.)

Plug-Ins by themselves are not apps, so you cannot notarize them (as far as I understand). If you do not or cannot use what @JBenghiat has meant above, you will have to make an installer in such a way that you can sign and notarize it.

Well it is difficult. I have already told what I knew. One possible reason why we had problems where that the format records for the PIO were already existing in the document. (We have not really checked, as soon as we have realized that it worked in new documents.) However if you have your problem with all kind of documents, new or old, then our one-time experience is of little help. (Therefore my previous post.)

Try to put all those in a DMG and sign the DMG (notarizing it is probably optional, but can be a good way to notarize all applications contained on it). Probably you will need to sign and notarize the installers too.

Sorry, then I cannot help, as apparently the problem is something else as the one we had.

How do you release your plugins? For example downloading a ZIP per Safari and unpacking the plug-ins, that will lead to quarantined plug-ins.

OK, then I re-phrase what I have meant: does it happen with any kind of template documents or only with certain ones?

Is the "new" document completely empty or has it already a format record for the PIO? (We had similar problems, using the C++-SDK. In old documents, the indentation did not show up, only in new documents.)