giada icon indicating copy to clipboard operation
giada copied to clipboard

Published 20 hours ago • verified publisher icon monocasual

Giada is damaged on MacOS

Open ademenet opened this issue 3 years ago • 13 comments

Environment

  • OS: macOS Big Sur 11.3
  • Giada version: giada-0.18.0.1-x86_64-macos

Describe the bug

When downloaded the compile version for macOS, I unzip then double click on the app and get the following message:

“giada” is damaged and can’t be opened. You should move it to the Trash.

To Reproduce

Steps described below.

Expected behavior

Running the application.

Screenshots

Thank you for your work!

ademenet avatar May 27 '21 17:05 ademenet

Message in kernel log: ASP: Security policy would not allow process: xxxxx, /Applications/giada.app/Contents/MacOS/giada

ggsubs avatar May 28 '21 15:05 ggsubs

Thank you @ademenet and @ggsubs for the feedback. What happens if you unpack the executable from the .app package and run it directly?

gvnnz avatar May 30 '21 08:05 gvnnz

There's a temporary workaround being discussed in #477.

gvnnz avatar Jun 05 '21 09:06 gvnnz

Thank you for you reply! I will try this workaround.

ademenet avatar Jun 14 '21 07:06 ademenet

@ademenet any progress on this?

gvnnz avatar Jul 23 '21 15:07 gvnnz

Is the Mac release being built on latest OS and Xcode versions? A year later and this is still an issue..

ST33LDI9ITAL avatar May 09 '22 21:05 ST33LDI9ITAL

@ST33LDI9ITAL try the instructions here in the "Problems with the macOS version?" paragraph.

gvnnz avatar May 10 '22 07:05 gvnnz

I mean I'm aware of the workaround but do you not think it wise to fix the build process and add code signing support to the GitHub action? As is, you are "releasing" builds that appear broken. You shouldn't need a dev account to self sign which would at least allow running it with a popup notification. I wouldn't say that the workaround is a solution, but sure.. it works.

ST33LDI9ITAL avatar May 10 '22 15:05 ST33LDI9ITAL

@ST33LDI9ITAL last time I checked the code signing was a paid process. That said, I'm not super familiar with the macOS way of releasing binaries (neither @tblrchstr I assume), so any help is appreciated.

gvnnz avatar May 13 '22 11:05 gvnnz

Hi team - this still seems to be an issue, and I agree should be resolved in the build process. The user experience of installing something that is unusable is not ideal, would you not agree?

meaganhanes avatar Jan 30 '23 19:01 meaganhanes

Hey @meaganhanes, yes I agree. The problem: currently we are too busy preparing the long-awaited Giada version 1.0 to set up the whole signing/notarization process. However, this is something that should be fixed sooner or later. I've marked this issue as "help wanted", anyone willing to help us is welcome :heart:

gvnnz avatar Feb 10 '23 16:02 gvnnz

Still getting this message :-(

“giada” is damaged and can’t be opened. You should move it to the Trash.

macOS v12.4 Macpro M1

hitautodestruct avatar May 30 '23 11:05 hitautodestruct

@hitautodestruct , please follow the instructions you can find at the bottom of this page: https://giadamusic.com/documentation-introduction, in the "Problems with the macOS version?" paragraph. Does that help?

And also:

Hey @meaganhanes, yes I agree. The problem: currently we are too busy preparing the long-awaited Giada version 1.0 to set up the whole signing/notarization process. However, this is something that should be fixed sooner or later. I've marked this issue as "help wanted", anyone willing to help us is welcome

gvnnz avatar Jun 03 '23 14:06 gvnnz