From 87f720314149c189a6588a4ddecb7ae4c21afd7e Mon Sep 17 00:00:00 2001
From: automated-signal <37887102+automated-signal@users.noreply.github.com>
Date: Thu, 11 Jul 2024 14:03:07 -0500
Subject: [PATCH] CONTRIBUTING: Add info for macOS ad-hoc signing

Co-authored-by: ayumi-signal <143036029+ayumi-signal@users.noreply.github.com>
---
 CONTRIBUTING.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ab6b7ea4f4..14757886c0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -265,3 +265,22 @@ npm run build
 ```
 
 Then, run the tests using `npm run test-release`.
+
+### Testing MacOS builds
+
+macOS requires apps to be code signed with an Apple certificate. To test development builds
+you can ad-hoc sign the packaged app which will let you run it locally.
+
+1. In `package.json` remove the macOS signing script: `"sign": "./ts/scripts/sign-macos.js",`
+2. Build the app and ad-hoc sign the app bundle:
+
+```
+npm run generate
+npm run build
+cd release
+# Pick the desired app bundle: mac, mac-arm64, or mac-universal
+cd mac-arm64
+codesign --force --deep --sign - Signal.app
+```
+
+3. Now you can run the app locally.