Portable Preferences and Code Signing

Help for Audacity on macOS.
Forum rules
ImageThis forum is for Audacity on macOS 10.4 and later.
Please state which version of macOS you are using,
and the exact three-section version number of Audacity from "Audacity menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Post Reply
juanBerger
Posts: 2
Joined: Fri Jun 05, 2020 12:59 am
Operating System: macOS 10.14 Mojave

Portable Preferences and Code Signing

Post by juanBerger » Fri Jun 05, 2020 1:37 am

On Mojave (10.14) the presence of the Portable Preferences folder prevents the ‘Audacity’ is an app from the internet, are you sure want to open it’ dialogue from appearing - instead it’s the ‘Audacity is damaged’ message (essentially there is no option to ‘un-quarantine’). The prefs folder works fine if you put it back into the app after it’s un-quarantined.

On Catalina the same app does not give you the ‘are you sure you want to open it’ message, prefs folder inside or not.

Essentially what I’m trying to do is make a version of audacity with modified preferences available to people directly. Since this seems like a developer signing thing, can I solve this by building from source?

juan

ps - also tried right-click open, same results

steve
Site Admin
Posts: 80752
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Portable Preferences and Code Signing

Post by steve » Fri Jun 05, 2020 4:20 pm

Apple are now insisting that apps are digitally signed with an certificate issued by Apple, and notarized. This makes it rather difficult to distribute builds of open source software.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

juanBerger
Posts: 2
Joined: Fri Jun 05, 2020 12:59 am
Operating System: macOS 10.14 Mojave

Re: Portable Preferences and Code Signing

Post by juanBerger » Fri Jun 05, 2020 6:03 pm

Thanks Steve that makes sense.

I made some progress with this by building with the prefs folder already in, just having some issues with build_dist.sh. Running this seems like a few parsing errors in the notarize function (for example: Entry, "notarization-upload:RequestUUID", Does Not Exist). Some of these were solved by removing the \ escapes from xcrun altool arguments, but there are others, so still seems like I'm doing something wrong. Anyone see this before?

-- Many Thanks

Post Reply