Oh wait, got it by displaying the notarisation log. The binary had no timestamp.

After googling a bit, I fixed it by adding --timestamp=http://timestamp.apple.com/ts01 to "Other Code Signing Flags", and it was notarised successfully! :-)

Is --timestamp=http://timestamp.apple.com/ts01 a good choice for this flag? The SDK docs just say "include a secure timestamp with your code-signing signature;", which is not too much information ;-)

One follow-up question:

I have followed the steps described in https://developers.maxon.net/docs/Cinema4DCPPSDK/html/page_maxonapi_dev_macos.html#page_maxonapi_dev_macos_notarization_xcodecodesigning. Created a ZIP of my plugin (using Python, but it's still a normal ZIP, with the plugin binary, res folder etc.), signed it with my certificate from apple, and uploaded it using the xcrun altool --notarize-app ...and-so-on... call. Upload successful.

However, the plugin is never notarised, and looking into the notarisation history, it tells me:
2020-11-27 08:44:14 +0000 b1cb2d34-a374-40b4-95d3-64a5d9e4df38 invalid 2 Package Invalid

I saw posts on the web from people who had the same problem. They fixed it by enabling "Hardened Runtime" in their projects. I already did that, as described in the SDK docs, but the problem persists.

Is there any way to find out what's to invalid about the package?

Cheers,
Frank

Thanks, that's a good tip! I'll try that out!

By the way, @r_gigante , turns out my tester hat installed 23.008 on Big Sur, while I had compiled the plugin against 23.110... so... it works now. Thanks :-)

Cheers,
Frank

That's what I gotta do then ;-)

Thanks & greetings,
Frank

Hm, tester days, he did the Terminal call, and he had the security warning when starting Cinema 4D (that the binary from my product is from an unknown developer, so it won't be loaded). He then opened his System Preferences >> Security & Privacy, and confirmed that the library should be loaded. But no success :-(

I totally understand. Just wanted to know if it maybe points to something terribly dangerous. I'll just ignore it, then ;-)

Cheers,
Frank

• Can you ask your customer what "usual" security questions he answered?
• Can you ask your customer before unpacking the zip archive, that maybe he has downloaded from an email or a website, to run $ xattr -d "com.apple.quarantine <zip archive to your plugin>"

Ah, thanks, I'll ask him to try that!

So, to make the plugin run on my beta testers' Macs with Bir Sur without warnings, I not only need to sign the binary, I also need to send the binary to Apple to have it notarised? Every single time I release a beta version to my testers??

Cheers,
Frank

Btw, @kbar I had problems compiling my R20 plugins with Xcode 11, I run into a lot of debug breaks that all have to do with GePrint() and GeDebugOut(). With Xcode 10 that happens almost never, and with the good old Xcode 8.2.1, everything runs smooth... but 8.2.1 only runs on my old MacBook.

Hmmm. Are you signing your plugins?

I have XCode 11, but not the latest version, because the App Store keeps telling me the update has failed, before it even starts doing anything :-/ maybe that’s the reason.

EDIT: Hm, I have Xcode 11.6. It'S the 11.7 update that wouldn't download.

Hi,

one of my beta testers reports that since he updated to macOS Big Sur, my plugin does not show up in the Extensions menu anymore. He has answered the usual security question that macOS shows him (as I don't sign my plugins yet), but no success.

I don't want to update to Big Sur just yet, as I'm pretty sure that will kill Xcode 10, and then I can't build my plugins for R20 anymore. Oh Apple

Anyway, does anybody know how I can fix that?

Cheers & thanks,
Frank