FreeCAD on macOS Mojave

[Kunda1]

Maybe we should open a ticket for this on the tracker ?

[chrisb]

Maybe we should open a ticket for this on the tracker ?

I have added an entry in the known issues topic.

[martijnthe]

A simple workaround for now:

Create an alias to the FreeCAD binary on your Desktop. When started from this alias, it will automatically open from a terminal. This for some reason fixes the freezes.

Works for me too -- Mojave 10.14.2 (18C54) on a MacBook Pro (Retina, 15-inch, Late 2013).

[martijnthe]

A simple workaround for now:

Create an alias to the FreeCAD binary on your Desktop. When started from this alias, it will automatically open from a terminal. This for some reason fixes the freezes.

This workaround works for me too.
Looking at the system logs, I suspect it has something to do with the FreeCAD.app not being code-signed.
When launching through Terminal.app (which the shortcut/alias helps doing), the checks are being by-passed.

Launching by double clicking FreeCAD.app:

Code: Select all

standaard	10:37:30.889721 +0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier , type: 0: 0x7fad78d00b30 at /Applications/FreeCAD-0.18_pre.app
standaard	10:37:30.889868 +0100	tccd	MacOS error: -67062
standaard	10:37:30.891132 +0100	tccd	MacOS error: -67062

Launching through Terminal or double clicking alias to FreeCAD.app/Contents/MacOS/FreeCAD:

Code: Select all

standaard	10:40:53.214961 +0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier com.apple.Terminal, type: 0: 0x7fad78c04720 at /Applications/Utilities/Terminal.app
standaard	10:40:53.222475 +0100	tccd	Platform binary prompting is 'Allow without Requiring Usage String' because: is Terminal

I'm not very familiar with macOS' codesigning / security architecture, but to test my theory, I tried code-signing the FreeCAD.app.
Miraculously, it helps to get rid of the system freeze!

So, this raises a question with me: should binary macOS releases be signed?

[leonardshelby]

If that's possible, they probably should be code signed. I wouldn't be surprised if Apple soon won't allow any unsigned apps at all. I believe the default setting on Mojave is already even stricter: App Store only.

I have tried to disable "gatekeeper", but it does not fix the freezes.

[Kunda1]

A simple workaround for now:

Create an alias to the FreeCAD binary on your Desktop. When started from this alias, it will automatically open from a terminal. This for some reason fixes the freezes.

This workaround works for me too.
Looking at the system logs, I suspect it has something to do with the FreeCAD.app not being code-signed.
When launching through Terminal.app (which the shortcut/alias helps doing), the checks are being by-passed.

Launching by double clicking FreeCAD.app:

Code: Select all

standaard	10:37:30.889721 +0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier , type: 0: 0x7fad78d00b30 at /Applications/FreeCAD-0.18_pre.app
standaard	10:37:30.889868 +0100	tccd	MacOS error: -67062
standaard	10:37:30.891132 +0100	tccd	MacOS error: -67062

Launching through Terminal or double clicking alias to FreeCAD.app/Contents/MacOS/FreeCAD:

Code: Select all

standaard	10:40:53.214961 +0100	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier com.apple.Terminal, type: 0: 0x7fad78c04720 at /Applications/Utilities/Terminal.app
standaard	10:40:53.222475 +0100	tccd	Platform binary prompting is 'Allow without Requiring Usage String' because: is Terminal

I'm not very familiar with macOS' codesigning / security architecture, but to test my theory, I tried code-signing the FreeCAD.app.
Miraculously, it helps to get rid of the system freeze!

So, this raises a question with me: should binary macOS releases be signed?

User opened issue #3744

[mikilon67]

Is this issue going anywhere? There have been several releases since 0.18 official one and it still impossible to use FC on mac. Its basically dysfunctional if you need to wait for the machine to unfreeze every time you need to open a file.

[looo]

Is this issue going anywhere?

You can use 0.18.3 from conda-forge:

Code: Select all

conda create -n freecad0.18.3 -c conda-forge

This one is based on qt5.9.
The bundles are only for the lazy people. In the background everything ispackaged with conda.

Also you can use the latest 0.19 bundle which is also based on qt5.9.

Best solution for sure is to avoid Mac at all.

[arvid]

Also experiencing this problem.
But at least I can add my voice saying that launching directly from the binary at /Applications/FreeCAD.app/Contents/MacOS/FreeCAD works (either via terminal or an alias).

I made an aplescript app with the code

Code: Select all

do shell script "/Applications/FreeCAD.app/Contents/MacOS/FreeCAD"

and gave it a nice icon by replacing the applet.icns with the freecad .icns file.

My info:

MacOS 10.14.6 (18G87)

FreeCAD 0.19:

OS: macOS 10.14
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17798 (Git)
Build type: Release
Branch: master
Hash: 7e60631239109c632a8f6cca83f6e7e5502e43a1
Python version: 3.7.3
Qt version: 5.9.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedStates (en_US)

FreeCAD 0.18:

OS: macOS 10.14
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16131 (Git)
Build type: Release
Branch: (HEAD detached at 0.18.3)
Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
Python version: 3.6.7
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedStates (en_US)

[chrisb]

I made an applescript app

I have added a link to this post to the "Known OS specific issues".