Page MenuHomeAleph Objects Inc

Application does not launch after confirming app from web on mac
Closed, WontfixPublic


Cura2 vs 6.2.21 - Mac OS X (Sierra and El Capitan) - When launching application, user is prompted to confirm that they want to open an application that was downloaded from the web. User selects "open" and dialogue goes away but application also never opens and disappears from the application tray at the bottom of the screen. Once you double click icon a second time, application opens.

Event Timeline

Yahuba created this task.Aug 16 2017, 9:41 AM

This is being investigated. I've determined that it occurs for all previous builds of Cura 2, but not for Cura 1.

More investigation indicates that this is a problem with with how MacOS quarantines files that have not been signed. We might only be able to resolve this by digitally signing the package with a developer key. This could potentially be an ICS developer key so that ICS does not need to agree to the Apple developer agreement. We'll need to discuss if this is a viable option.

@mbocevski Can you make a build that signs the application using an ICS Apple developer key? If this resolves the issue, it is probably the best solution. If you make a test build we can test it and see how it works.

tranter changed the edit policy from "Custom Policy" to "Subscribers".

Added option to sign the build with the Apple Developer Id key. The codesign can be triggered by specifying -DAPPLE_ID_CERT_NAME="Mac Developer: [developer name here]" when invoking CMake. @alexei can you configure this on buildbot master?

alexei added a comment.Oct 4 2017, 6:46 AM

@tranter , @mbocevski : What is the exact string I should put in here

-DAPPLE_ID_CERT_NAME="Mac Developer: [developer name here]"

To sign the package on MAC buildbot slave?

We spent significant time investigating this and trying signed binaries and were not able to suppress the install warning. According to our Mac expert, signing a binary will still generate a warning about it coming from the Internet and the user needs to confirm to run it. This is causing it to only launch the second time. There is no way around the warning unless the app is released to the Apple store. It will only happen the first time you run a given version.

Signing is still desirable to make it clear the app is coming from a real developer but won't avoid this warning dialog. The recommendation is to continue to document that the user needs to adjust their security settings:

And somewhere we should mention the known issue that it will not run the first time you initially open it after downloading.

@tranter , I guess we can close this ticket then.

I'll leave the references to prev tickets here: T980
And reference to Documentation task: T446

alexei closed this task as Wontfix.Oct 24 2017, 12:54 PM