tauri-apps / tauri-apps/tauri-docs
[docs] Add instructions/tips on using self-signed certificates for macOS signing
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
For all aarch64/M series chips, all apps must be signed, even if it's not from Apple's Developer Program.
It took delving into the source code to find that the name for the certificate used MUST start with one of the pre-defined strings, like "Apple Distribution:". There should probably be a note about this in the docs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the documentation for existing macOS signing and self-signed certificate guidance; no specific file or test is named in the issue. The documentation is complete when it explains that Apple Silicon apps must be signed and that the certificate name must begin with an accepted prefix such as "Apple Distribution:".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100