Skip to content

Added codesigning script for upcoming macOS tree #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added codesigning script for upcoming macOS tree #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/Technical Notes/Deployment/macOS code signing/2.Code signing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ The benefits of using our script to code sign are:

You can download the code signing script [here](/assets/codesigning_macos/codesign_omnis.sh){:download="codesign_omnis.sh"} and its dependency script for generating application entitlements [here](/assets/codesigning_macos/generate_entitlements.sh){download="generate_entitlements.sh"}.

If you are using a version of Omnis Studio prior to 11.2 (which introduced the new macOS tree structure), you can use the following script from [here](/assets/codesigning_macos/codesign_omnis_old.sh){:download="codesign_omnis_old.sh"}.

## How to use the code signing script

Xcode 13.2 is the minimum required for notary tool, used during code signing.
Expand Down Expand Up @@ -66,4 +68,4 @@ We believe that for most applications, you may not need to add any extra compone
The safest approach would be to attempt notarization once your application has been code signed and if any components fail to pass, only then you should consider adding them to the signing script, and only if code signing was the issue they failed.

A notarization failure due to bad code signature might contain errors such as **The signature does not include a secure timestamp** or **The binary is not signed with a valid Developer ID certificate**.
{: .description}
{: .description}
Loading