Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

weekly builds are not signed and are shown as "damaged" on arm64 macOS #291

Open
smr02 opened this issue Aug 19, 2024 · 25 comments
Open

weekly builds are not signed and are shown as "damaged" on arm64 macOS #291

smr02 opened this issue Aug 19, 2024 · 25 comments

Comments

@smr02
Copy link

smr02 commented Aug 19, 2024

FreeCAD_weekly-builds-38467-conda-macOS-arm64-py311.dmg

Screenshot 2024-08-19 at 11 11 53
@JohnOCFII
Copy link

JohnOCFII commented Aug 19, 2024

Same experience:
Screenshot 2024-08-19 at 8 52 00 AM

Might be related? #290

@MisterMakerNL
Copy link

Is this how Apple solves all issues? XD

@BillTuttle
Copy link

Is this the arm or intel package? Intel doesn't seem to be damaged, but does now require MacOS 13.6 or later.

@JoanMendoza
Copy link

JoanMendoza commented Aug 19, 2024

On my ARM mac mini (M1 running MacOS 14.5) neither is working.

The arm version gives me the same error that was posted in the pictures.

The x86 version allows me to uncompress it and open it. Once I to open it, there is an error that says it can't initialize somthing. I don't know if this is a known error or if Rosetta is supposed to be able to run the x86 version of freecad. However I know that i was able to run the the x86 version successfully before switching to the arm version.

Screenshot 2024-08-19 at 16 21 27

@smr02
Copy link
Author

smr02 commented Aug 19, 2024

@BillTuttle It's the ARM package
however, the conda package conda install freecad/label/dev::freecad is working

@artica1
Copy link

artica1 commented Aug 19, 2024

Same issue

Using xattr -dr com.apple.quarantine /Applications/FreeCAD.app lets the app open, but it fails with the same 'Failed to init from config' error that appears when running the x86 version.

@wiz78
Copy link

wiz78 commented Aug 21, 2024

FreeCAD_weekly-builds-38495-conda-macOS-arm64-py311 doesn't start on my mac either

@luzpaz
Copy link
Collaborator

luzpaz commented Aug 21, 2024

Attempts to fix are happening at #293

@oursland
Copy link
Collaborator

The Intel build should be working again. The Apple Silicon build requires additional steps. My notes on the investigation are here.

The QRD is that FreeCAD was launched by a shell script that caused macOS to think the application required Rosetta (it does not). The shell script was replaced by a native program that fixes the Rosetta issue, but I had an error in it. The fixed version works on Intel, but Gatekeeper (macOS code signature enforcement) behaves differently on Apple Silicon. A command at the CLI will permit running the Apple Silicon version. A better solution that does not require user intervention is being investigated.

@pheraph
Copy link

pheraph commented Aug 23, 2024

I can confirm that the following steps fix the problem for me:

  1. Download and install: https://github.com/FreeCAD/FreeCAD-Bundle/releases/download/weekly-builds/FreeCAD_weekly-builds-38495-conda-macOS-arm64-py311.dmg
  2. Remove the quarantine attribute: sudo xattr -r -d com.apple.quarantine /Applications/FreeCAD.app
  3. Run FreeCAD

@maxwxyz
Copy link
Collaborator

maxwxyz commented Aug 23, 2024

this was always the case for me in the weekly builds for over a year now :D
Just right click and then click open.

@pheraph
Copy link

pheraph commented Aug 23, 2024

this was always the case for me in the weekly builds for over a year now :D Just right click and then click open.

The whole point of this issue is that right clicking isn’t doing the job. 🫠

@oursland
Copy link
Collaborator

My hypothesis is that Apple has decided to change the behavior of unsigned builds that are identified as Intel vs ARM. The Intel builds permit right-click and open to run unsigned code from the internet, but ARM builds do not.

Before the recent changes to the FreeCAD launcher, the launcher was a architecture-independent shell script. Apple's Gatekeeper could not identify the application as an ARM binary, which is why it claimed to require Rosetta 2 despite not needing it. This also meant that the legacy behavior of right-click and open would work. Now that the ARM binaries are correctly identified, they will not open without removing the attribute.

@skandragon
Copy link

My hypothesis is that Apple has decided to change the behavior of unsigned builds that are identified as Intel vs ARM. The Intel builds permit right-click and open to run unsigned code from the internet, but ARM builds do not.

I'm not sure about this. I've used right-click to open on other projects before and it works. I'm not about to say Apple would not force this issue by expiration of old systems, but I don't know why other downloads would allow me to right-click and open (and they are ARM64 builds, I have checked) while FreeCAD is some special case.

@oursland
Copy link
Collaborator

@skandragon See my analysis here: #293 (comment)

@theosib
Copy link

theosib commented Aug 27, 2024

Same problem with FreeCAD_weekly-builds-38553-conda-macOS-arm64-py311.

@oursland
Copy link
Collaborator

@theosib see my comment here: #293 (comment)

@pilhuhn
Copy link

pilhuhn commented Sep 11, 2024

Same for me with the rc1 build on macos/arm

@wblondel
Copy link

wblondel commented Sep 11, 2024

I had the same issue with the 1.0.0RC1 arm64 version for MacOS, however this allowed me to run it:
xattr -dr com.apple.quarantine "/Applications/FreeCAD.app"

@JohnOCFII
Copy link

Today's signed bundle launches correctly on my M1/arm Mac.

OS: macOS 14.6.1
Word size of FreeCAD: 64-bit
Version: 1.0.0RC1.38642 (Git)
Build type: Release
Branch: (HEAD detached at 1.0rc1)
Hash: 60a251354e203bdb924e2190fb9f5e18b48d7362
Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2
Locale: C/Default (C)
Installed mods: 
  * FeedsAndSpeeds 0.5.0
  * OpenTheme 2024.9.1
  * fasteners 0.5.28
  * Curves 0.6.47

@hyarion
Copy link

hyarion commented Sep 28, 2024

Today's signed bundle does not launch correctly on my M1/arm Mac <string>1.1.0dev-38843</string>
sudo xattr -r -d com.apple.quarantine /Applications/FreeCAD.app makes it work.
image

@JohnOCFII
Copy link

Today's signed bundle does not launch correctly on my M1/arm Mac <string>1.1.0dev-38843</string>
sudo xattr -r -d com.apple.quarantine /Applications/FreeCAD.app makes it work.

As far as I know, the current plan is the Release Candidates and final versions will be signed, but the weekly development builds won't be signed.

Yes - known issue. I believe that'll be resolved when @oursland and/or @looooo refine the build process.

@rolfeisenhut
Copy link

I have the same issue with the weekly build, because it was not codesigned.
It could be fixed by code signing with locale codesigning tool after expanding zip file , b ut before first time start it.
Then start the application and confirm in security to run this application.
After that it works fine, but must be resigned and confirmed after each new weekly version.
This is very annoying - so i vote for code signing the weekly arm64 version as well.

Rolf

@martin1951
Copy link

Same problem on my M2 MacBook Pro running Sonoma 14.6.1. I don't have the problem with the pre-release FreeCAD V1.0.

@oursland
Copy link
Collaborator

@martin1951 Run xattr -r -d com.apple.quarantine /Applications/FreeCAD.app to remove the quarantine attribute from the app that prevents macOS from running programs downloaded from the internet.

@adrianinsaval adrianinsaval changed the title weekly build 38467 for MacOS is damaged weekly builds are not signed and are shown as "damaged" on arm64 macOS Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests