tauri-apple-release

# Tauri Apple Release Use this skill for Tauri iOS/TestFlight or macOS Apple release work. ## Prime directive Treat Apple release work as **one release packet**, not a sequence of drip asks. A usable packet includes: 1. **Team/app metadata** — Bundle ID, Team ID, version, build number, App Store Connect app record. 2. **Upload auth** — App Store Connect API key _or_ Apple ID app-specific password + provider public ID. 3. **Distribution signing** — Apple Distribution cert/private key and App Store provisioning profile for iOS; Developer ID cert + notarization auth for macOS direct download. 4. **Artifact path** — `.ipa`, `.app`, `.dmg`, etc. Never ask for only “the issuer ID” unless the packet is otherwise complete and that exact field failed. ## Safety rules - Do not print or paste private key, `.p8`, `.p12`, app-specific password, provisioning profile contents, or real secret values. - It is okay to discuss non-secret identifiers: Bundle ID, Team ID, certificate SHA-1 fingerprint, profile UUID/name, key ID, issuer ID/provider public ID. - Prefer 1Password/GitHub Secrets/env vars for secrets. - Do not upload to TestFlight/App Store Connect until export validation passes with an App Store distribution provisioning profile. ## Standard triage Start by identifying which gate failed: 1. **Build correctness** — `pnpm build`, `tauri build`, `tauri ios build` fails before Apple export/upload. 2. **Apple trust/signing** — archive/export fails, invalid provisioning profile,...