tauri-ios-distribution_skill

This skill guides you through distributing Tauri iOS apps to the App Store, including enrollment, signing, TestFlight, and submission steps.

12

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dchuk/claude-code-tauri-skills --skill tauri-ios-distribution

SKILL.md13.2 KB

Overview

This skill guides you through distributing Tauri v2 applications to the iOS App Store, from Apple Developer enrollment to final App Store submission. It focuses on bundle configuration, code signing, provisioning profiles, Xcode setup, TestFlight testing, and automated uploads. The goal is a repeatable, CI-compatible release flow for iOS builds.

How this skill works

The skill inspects and documents the required Apple and Tauri configuration steps: bundle identifier and versioning in tauri.conf.json, required Info.plist keys, Xcode signing and capabilities, certificate and provisioning profile creation, and IPA generation. It also explains upload options (altool, Transporter, Xcode Organizer), App Store Connect API key usage for automation, and common troubleshooting tips. Example CI workflows and scripts show how to automate builds and uploads securely.

When to use it

When preparing a Tauri v2 app for App Store distribution
When setting up Xcode signing and provisioning for iOS builds
When creating TestFlight beta releases (internal or external)
When automating iOS releases with CI/CD (GitHub Actions, etc.)
When troubleshooting code signing, provisioning, or upload errors

Best practices

Use a stable reverse-domain bundle identifier and register it in Apple Developer before builds
Increment CFBundleVersion for every upload and update CFBundleShortVersionString for user-visible releases
Store App Store Connect API keys and certificates in secure CI secrets, not in repo
Verify Xcode capabilities match the App ID and regenerate provisioning profiles after changes
Build release IPAs with tauri ios build --export-method app-store-connect or archive via Xcode for manual control

Example use cases

Manual release: prepare tauri.conf.json, configure Xcode signing, archive and upload via Xcode Organizer
CI release: encode certificates and provisioning profiles as base64 secrets, run a macOS runner to build and upload via altool
TestFlight beta: upload IPA, add build to TestFlight, invite internal testers or submit for external beta review
Troubleshooting: use security find-identity and check provisioning profiles when facing signing errors
Version automation: run a script to bump bundleVersion before tagging a release and triggering CI

FAQ

A macOS machine with Xcode and the iOS SDK, an Apple Developer Program membership, and a Tauri project initialized for iOS.

How do I automate uploads without storing Apple credentials in plaintext?

Create an App Store Connect API key (.p8), store it and certificates as encrypted CI secrets, and use the API key with xcrun altool or Transporter in your workflow.