Page MenuHomeAleph Objects Inc

Notarization required for Cura LE on macOS 10.15 Catalina
Open, Needs TriagePublic


Cura LE Version: Any (observed on 3.6.18)

Operating System: macOS 10.15 Catalina beta

Printer: N/A

Tool Head: N/A

Description of issue: Trying to open Cura LE on macOS 10.15 Catalina betas fails

macOS Catalina introduces a new requirement that software installed from external sources be notarized (by Apple) to run.
This means the app needs to be properly signed by a developer and submitted to Apple notary service

From Notarizing Your App Before Distribution

Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run.
Beginning in macOS 10.15, notarization is required by default for all software.

That page provides additional references.

Steps to reproduce:

  1. Install on a macOS 10.15 system
  2. (Attempt to) Launch
  3. Error dialog reflected that app is not notarized

Upload cura-lulzbot.log (attachment)

Event Timeline

idcrook created this task.Aug 24 2019, 5:01 PM
Orias added a subscriber: Orias.Aug 26 2019, 2:01 PM
jebba added a subscriber: jebba.Aug 29 2019, 12:57 PM

Am I following it correctly that all MacOS 10.15 end-user software will now require to be notarized? There is no way around this? Won't that break huge amounts of legacy Mac software or am I missing something?

idcrook added a comment.EditedAug 30 2019, 4:06 PM

Along with the notarization requirement, macOS 10.15 Catalina no longer will launch 32-bit apps.
So the answer to question about many legacy app being unavailable on 10.15 would appear to be yes.

I am not familiar with any way to bypass the notarization requirements for apps signed/distributed by Developer ID in macOS 10.15 Catalina.

Apple just posted a developer update related to notarization and macOS Catalina.

Notarizing Your Mac Software for macOS Catalina

It does not change notarization requirement. It is directed to adjusting (until January 2020) notarization requirements to work with more software situations.

On macOS 10.15 Catalina, I was able to launch LulzBot Cura 3.6.18 today. It seems to run fine-- didn't even get the Unsigned App dialog warning a la

# in an iTerm terminal session
open /Applications/cura-3.6/

I think it was made possible using the "Developer Tools" setting to enable to run software locally from Terminal or iTerm under System Preferences > Security & Privacy > |Privacy| tab?
(see attached screenshot)

My previous post was inadvertently misleading. It must have worked because I had opened/used the 3.6.18 version of in macOS Mojave pre-upgrade to Catalina. When I replaced 3.6.18 with a 3.6.20 app just now, the dialog about unable to open app, made famous on Catalina, appears.

However, the following incantation puts back the [ ] Anywhere option in Security & Privacy Preferences panel (see screencap).

sudo spctl --master-disable

And, having done that, I was able to launch and run on macOS 10.15 Catalina (19A583).
I have no idea whether this will be possible to override in future versions of macOS. It is a feature related to anti-malware measures.