Open ryanhugh opened 1 day ago
May I first ask why you need to sign your own binary? Are there modifications to the app that you intend to distribute?
Looking at the error, The binary is not signed with a valid Developer ID certificate.
. Do you have one of these issued by Apple for your organization?
We made some changes to the app yeah.
Looking at the error, The binary is not signed with a valid Developer ID certificate.. Do you have one of these issued by Apple for your organization?
We have a valid Apple Developer ID and made a new profile for this. Here's a screenshot showing the profile is valid. There's a lot of options in the Apple Developer portal though, so the issue may be with how the profile was made.
Checks before filing an issue
Mattermost Desktop Version
release-5.9
Operating System
MacOS M2 15.1.1 (24B91)
Mattermost Server Version
No response
Steps to reproduce
We are running into an issue notarizing and signing the MacOS application.
npm run package:mac
does not work. It throw an error. We are unable to launch the binary that is produced.Full details here: https://rose-piranha-ec2.notion.site/Bounty-Electron-MacOS-Signing-Issue-1435eaeefd2180da87acebd500bdd884?pvs=74
Happy to pay if you help solve this for us thanks.
Expected behavior
I expect
npm run package:mac
to be able to compile, notarize and sign the MacOS application such that we can share the build app and run it on other Mac computers with no issues.Observed behavior
npm run package:mac
fails to build the Mac app. It produces a binary, but the binary refuses to launch. Mac OS saysLog Output
Additional Information
No response