macOS code signature errors cause crash at startup

[Be]

Beta build 6647 is okay. See attached log.

[Be (be.ing)]

This happened once with one of the 2.1 beta builds then somehow the next build was fine...

[Sean M. Pappalardo (pegasus-renegadetech)]

"code signature invalid for '/Applications/Mixxx.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib'"

@RJ: Do we need to update that dependency in the OSX build env?

[Be (be.ing)]

This looks like a recurrence of https://bugs.launchpad.net/mixxx/+bug/1730333 which mysteriously went away in future builds. I just manually triggered a new build.

[Be (be.ing)]

Build log shows:
Codesigning: osx64_build/Mixxx.app/Contents/Frameworks/libchromaprint.1.3.0.dylib
codesign -f -s 'Developer ID Application: Albert Santoni' --keychain /Users/mixxx/Library/Keychains/Mixxx.keychain osx64_build/Mixxx.app/Contents/Frameworks/libchromaprint.1.3.0.dylib

without any associated error. I don't know what's going on.

[Be (be.ing)]

Fixed by RJ:
"Just wiped the Jenkins workspace (which jenkins admins can do from the web interface) and restarted the mac VM. I also deleted the cached build environments so it'll re-download the golden environment."

[Foss-4 (foss-4)]

bit confused so adding another data point:
2.1.0-rc1 (build 2.1 r6663) opens fine on my macbook pro. but maybe that's already the fixed build?

[Foss-4 (foss-4)]

And now I am even more confused:
 mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.dmg

Downloaded today crashes on me with above error message. That build was created yesterday. But if I had another build earlier, why did about show the r6663 info I posted above?

So for me with latest 2.1 release build this is not fixed.

[jus (jus)]

Not fixed with the download available on website
"Mixxx" "2.1.0-rc1" "(git 2.1 r6655; built on: Apr 6 2018 @ 08:55:48
http://downloads.mixxx.org/builds/2.1/release/mixxx-2.1.0-rc1-2.1-release-macintel64-latest.dmg

and with the latest available build
``
$ /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/Mixxx
dyld: Library not loaded: @executable_path/../Frameworks/libchromaprint.1.3.0.dylib
  Referenced from: /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/Mixxx
  Reason: no suitable image found. Did find:
 /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib: code signature invalid for '/Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib'

 /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib: stat() failed with errno=1
 /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib: code signature invalid for '/Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib'

 /Applications/mixxx-2.1.0-rc1-2.1-git6663-release-macintel64.app/Contents/MacOS/../Frameworks/libchromaprint.1.3.0.dylib: stat() failed with errno=1
Abort trap: 6
``

[Be (be.ing)]

I can confirm the latest build is not working again. I'm not sure what changed since the last working build.

[RJ Skerry-Ryan (rryan)]

Disabled code signing (our DeveloperID cert is expired) and the latest build works.

[Be (be.ing)]

The latest build works. Curiously it also seems to be numbered 6663 like the last broken build.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9220