Documentation
Pipelines
Install the GitHub Actions recipe that builds TestFlight and Play Internal from a commit you pick in CapWrap.
Settings → Pipelines. A pipeline is a recipe in your repo. CapWrap starts it; GitHub runs it.
Install
Install TestFlight + Play pipeline opens a PR (or commits to default if you chose that from the ship modal). GitHub can only dispatch a workflow that already exists on the default branch. Merge the PR before the first ship.
If an old placeholder workflow is present (it fails on purpose), replace it from this screen.
What the recipe does
At a high level: check out the SHA you picked → install JS dependencies → inject secrets → build the website → copy it into Capacitor → on a Mac, archive iOS and upload TestFlight → on Linux, sign an Android bundle and upload Play Internal. Full sequence: What happens during a build.
Store keys are not written into Git. The job asks CapWrap for them.
Workflow filenames
You can rename files, then save:
- Native workflow — default
capwrap-native.yml - Preview workflow — default
capwrap-preview.yml(optional)
CapWrap dispatches those names. If you hand-write a different Actions file, point Settings at it. It must accept workflow_dispatch inputs including sha and version.
Reinstall
Safe to run again if helpers are outdated. It refreshes the .capwrap/ files and workflow YAML.