Send a TestFlight / Play build

This is the moment CapWrap exists for.

Before you tap the button

• Capacitor is on the default branch (ios/ and/or android/)
• Apple and/or Google show Ready in Settings
• Pipeline is installed on the default branch
• Environment keys that the website needs are filled (or you accept a possible white screen)

If something is missing, Push to Production explains the blocker and links to the setting.

The modal

1. Select a commit on Overview.
2. Push to Production.
3. Choose Store build. (Live update is hidden until that product is on.)
4. Tick TestFlight, Play Internal, or both — independently, as long as that platform is ready.
5. Optional version number (the user-facing 1.2.0). Leave blank to bump. Build numbers (CFBundleVersion / versionCode) increment automatically so Apple / Google accept every upload.
6. Confirm.

CapWrap tells GitHub: “run capwrap-native.yml on this SHA.” You can close the modal and watch Overview or History.

After success

Testers install from:

• iOS: TestFlight app
• Android: Play Console internal testing opt-in link

Public App Store / Play production is still a manual step in Apple’s and Google’s consoles.

One run at a time

If a native run is already dispatching or running, a second confirm is refused. Wait or cancel the GitHub Actions run.

Failed run

Open the Actions log from the run card. Typical causes are in Troubleshooting. Fix, push if needed, pick the new SHA, ship again.