Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2020.3.X, 2021.1.X

Votes

10

Found in

Issue ID

1304455

Regression

Yes

macOS builds no longer run when with a quarantine attribute due to incorrect codesigning

MacOS

-

macOS builds no longer run when with a quarantine attribute due to incorrect codesigning

Repro Steps:
1. Download a mac editor (2021.1.x for instance)
2. Once downloaded, build a mac player
3. Move mac player to a different mac and try to run

Actual Result
A new error shows up (it started to happen around mi-December 2020 for me an a colleague) : "<Unity app> is damaged and can't be opened. You should move it to the Trash"

Expected Result
Before it started happening, another dialog was showing up and I could still open the app: "macOS cannot verify the developer of "<Unity app>. Are you sure you want to open it?"

Workarounds (you only need to apply one):
- After exporting the game on a path, resign the whole app bundle: "codesign --deep -s - -f path/to/game.app"
- Remove the quarantine attribute from the command line: "xattr -r -d com.apple.quarantine path/to/game.app"
- User an GUI app to strip the flag: xattred

Comments (25)

  1. bbyford

    May 07, 2021 15:49

    not fixed for 2020.2.6f1

  2. x70x

    May 01, 2021 20:56

    I updated to 2020.3.0f1 but I'm still experiencing this issue.

  3. Tautvydas-Zilys

    Apr 16, 2021 16:08

    Hi everyone, as far as we are aware, this issue is fixed in all known cases. If you're still running into "<Unity app> is damaged and can't be opened. You should move it to the Trash" error in Unity versions where it's listed as fixed, please either report a bug, or post to our macOS forum (https://forum.unity.com/forums/macos.95/) and we'll make sure to investigate/help you!

  4. botta-naverz

    Apr 16, 2021 06:10

    2021.1.3 also.

  5. botta-naverz

    Apr 16, 2021 06:08

    2020.3.3 2020.3.4 2021.1.1 still has this bug

  6. bcapdevila

    Apr 07, 2021 07:59

    Any word on this issue from Unity Team? Still present in 2020.3.2f1

  7. Ninad_Jagdish

    Mar 24, 2021 06:09

    Still seeing this in 2020.3.0f1 and 2020.3.1f1.

  8. bcapdevila

    Mar 23, 2021 17:49

    Same problem still in 2020.3.1f1

  9. yuli_volta

    Mar 19, 2021 17:56

    Also not fixed in 2021.1.0b12

  10. poliman

    Mar 19, 2021 10:52

    I also use 2020.3.0f1 and the BUG is NOT FIXED.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.