Shipping Darwin Apps
Use this for any work that builds or ships an app targeting iOS or macOS, regardless of the source language (native Swift/ObjC, Wails, Tauri, Electron, Go, Rust). This is the routing hub: it tells you which reference doc to read based on what is in the repo and what you are doing.
Guardrails
- Keep private keys, files, certificates, provisioning profiles, and files out of chat, logs, and git; they reach CI only as encrypted repository secrets. Keep , , , and exported app bundles out of git and chat; they leave the machine only through the release workflow's upload and artifact steps.
- Never print certificate passwords, app-specific passwords, API keys, base64 certificate payloads, temporary keychain passwords, or notarization credentials.
- Get explicit approval before submitting to App Store review, publishing publicly, changing bundle identifiers, rotating credentials, or altering account/team settings. Internal TestFlight upload may proceed only when the user authorized release automation.
- Treat Apple Developer Team IDs, bundle IDs, and App Store Connect app IDs as project configuration. Do not hard-code personal examples into public docs.
- Check before touching unrelated workflow, signing, version, or project changes.
- If a signing identity's private key is missing, stop. A certificate alone cannot produce a usable signature.
Route to the right doc
Read only what you need. Start here, then open the doc the repo signal points to.
If the environment is uncertain, or this is a project's first release, start with readiness.md to understand what is checked and installed.
Detect the build doc from the repo:
| Repo signal | Read |
|---|
| / / / | build/native.md |
| or Wails in | build/wails.md |
| build/tauri.md |
| with electron / electron-builder | build/electron.md |
| / producing a / | build/go-rust.md |
Detect the ship doc from the distribution target:
| Distribution target | Read |
|---|
| iOS via App Store / TestFlight | ship/appstore.md |
| macOS outside the App Store (Developer ID, notarization) | ship/direct.md |
Only ask the human when the repo cannot answer it: is this release or debug? which distribution channel? real release or dry run? Use repo signals for everything else.
Quick reference
| What you are doing | Necessary command |
|---|
| Build a native Xcode app | xcodebuild archive -scheme <scheme> -archivePath <path>
|
| Build a Wails app | / |
| Build a Tauri app | |
| Build an Electron app | npx electron-builder --mac
|
| Sign (Developer ID) | codesign --force --options runtime --timestamp --sign "<identity>" <app>
|
| Notarize | xcrun notarytool submit <file> --apple-id ... --team-id ... --password ... --wait
|
| Staple + verify | xcrun stapler staple <file>; xcrun stapler validate <file>
|
| Gatekeeper assess (app/DMG) | spctl --assess --type execute --verbose=4 <app>
/ --type open --context context:primary-signature <dmg>
|
Cross-reference: reusable
contracts live in the
skill in the
repo.