DCP-o-matic

Sierra and 2.11.72 devel : after an eternal wait I aborted the verif and opened w/ ctrl-click.
it now reopens by simple click and no more traffic request.
--jp

Hi Carl,

I guess you already have seen this?

https://developer.apple.com/library/con ... dures.html

- Carsten

Thanks, yes. I *think* I have to sign the .dmg, for which I have to build on Sierra or High Sierra, which means I have to install that version on my Mac, which means my build scripts break a bit, but hopefully there will be another test version along soon...

Yes, while most of the document's details are hard for me to understand, it looks as if you need to be on a more recent OS X version to sign to current specs.

However, currently I (and probably most Mac users) do not care much about the need for the one-time Control-Click to start the apps. The re-occurring 'allow incoming connections' request was more annoying, and that seems to be gone now.

- Carsten

Carsten wrote: ↑Mon Mar 12, 2018 8:48 pmcurrently I (and probably most Mac users) do not care much about...

I am among these 'most'
to let 2.12.0 fly before spring time, you could postpone this feature to 2.13.n+ ??
.

Could you try 2.11.73? Seems to work for me on High Sierra.

No change in Sierra for me. Verification takes the same ca. 3min30s, and I need the initial control-click to open. Simple Click is blocked. When going to security prefs, it explicitly tells me 'DCP-o-matic 2 was blocked from opening because it is not from an identified developer'.

WHY is the 'allow incoming connection' request gone, when the app signing is still not recognized? Is that two completely different/separate issues?


- Carsten

I don't know... is this verification when opening the .dmg or when running the .app?

When running the app. Mounting the DMG only takes a second or so.

- Carsten

2.11.74?