All c++ based plugins have an *.xlib file, which is the compiled plugin, and what does the work.

Running any plugin with an xlib , on MacOS Catalina(or later), will give you a warning, the first time it runs.


Welcome to MACOS...

  • Firstly, when you download a zip file which contains a plugin, do not let Safari unpack it for you. Otherwise it will get quarantined( and you will think it is an empty package)
  • Secondly, once you have simply downloaded the zip(really downloaded it, as is), do not use the system unpacker. Use pretty much any third party unpacker, other than the garbage system tool that Apple has given you, otherwise, it will also quarantine the contents. 


To allow the plugin to load normally :

  • Firstly, see the "Good Practice" suggestion at the bottom of this page.


  • Open the Mac System Preferences – Security and Privacy, while Cinema4D is loading.
  • When a warning window pops up, like “demearth4_R20.xlib ” cannot be opened because the developer cannot be verified. Proceed as follows:
  1. Click on Cancel. 
  2. In the System Preferences – Security and Privacy, click "Allow Anyway". 
  3. Repeat this for all issued warnings.
  4. Close Cinema4D and run it again. This time, when you get the warnings, click "Open". 
  5. The plugin will now load normally, without issuing any further warnings.


note: if you get an update for your plugin, the *.xlib file will have changed, and you will need to repeat the above process.


 M1(Apple Silicon) is currently supported via Rosetta (not native)

Select Get Info for Cinema 4D (from Applications > Maxon Cinema 4D R23)

Enable Rosetta.

see also this link for Rosetta 2..


on newer version of OSX, APPL decided to make it ever trickier for you, by hiding the option that would let you allow an application from and unknown developer. However, it is fairly easy to get that option back. 



Run the following command in the Terminal window and provide your password: 

sudo spctl --master-disable

NOTE : This does NOT disable gatekeeper. It simply gives you back the option (which you had before), to decide for yourself if you want to allow an unsigned plugin (or app), or not. Once you run the command, you  get that important option back, in your Security and Privacy Preferences, and you need to allow the plugin as before (see above)



Good Practice

Firstly, always keep a backup of the original zip. 


Note that the zip file contains 3 (or more) binary *.xlib files.

C4D tries to load all of those xlib files. It has to load them to determine which API each is for. This will result in you being asked 3 times to allow the plugin. That is not not necessary as you only need one of those xlib files for your c4d version.

i.e. MACOS tells you that the developer cannot be verified, for each of the xlibs.


There can be advantages to that, if you want to use one plugin folder for multiple versions of cinema 4d. However, if you want to avoid needing to allow the same plugin, multiple times, you can safely delete the versions you don't require. 

i.e.

your running in R25 or 26. You can delete the R20, R21, R23 xlib files.

your running in R23 or 24. You can delete the R20 and the R21 xlib files.

your running in R21 or 22. You can delete the R20 and the R23 xlib files.

if your running in R20, You can delete the R21, R23 and R25  xlib files.



Notes

S versions run from the previous R version.

i.e. 

R26, uses the R25 build.

S24, uses the R23 build.

S22 uses the R21 build.

R22 uses the R21 build.

R20 is the old license system (11 numbers)


Thank Maxon for this madness :)