This page is for developers with a Capacitor project who want signed Android and iOS builds from their own GitHub repository. You will see your app in the simulator, add one workflow, set the signing secrets, and get a signed .aab and .ipa as run artifacts. You do not need EAS.
See it in the simulator
From a Capacitor project, after npx cap sync or your web build, run shipvo sim or shipvo preview. Shipvo opens the built web folder (webDir in capacitor.config.*) on the Android and iOS skins. Expo apps build as before.
Add the workflow
From the root of your Capacitor repo:
npx shipvo ci init --framework capacitorThis writes .github/workflows/shipvo-build.yml. Use --dry-run to print it without writing. Use --force to overwrite an existing file.
The workflow runs by hand (Actions tab, "Shipvo build", Run workflow) and on tags that start with v. It needs npm run build to produce your web build, and an android/ and ios/ folder in the repo.
Add the secrets
In GitHub: Settings, Secrets and variables, Actions, New repository secret. The workflow never contains secret values; it reads them from here.
Android
Create an upload keystore if you do not have one, then encode it:
base64 -i upload.keystore | pbcopy # macOS
base64 -w0 upload.keystore # Linux| Secret | What it is |
|---|---|
ANDROID_KEYSTORE_BASE64 | The keystore file, base64 encoded |
ANDROID_KEYSTORE_PASSWORD | The keystore password |
ANDROID_KEY_ALIAS | The key alias inside the keystore |
ANDROID_KEY_PASSWORD | The key password |
The output is a signed .aab in the android-release artifact.
iOS
You need an Apple Distribution certificate exported as a .p12 file, and an App Store provisioning profile. Encode both with base64.
| Secret | What it is |
|---|---|
IOS_CERTIFICATE_BASE64 | The .p12 certificate, base64 encoded |
IOS_CERTIFICATE_PASSWORD | The password you set when you exported the .p12 |
IOS_PROFILE_BASE64 | The .mobileprovision file, base64 encoded |
IOS_PROFILE_NAME | The profile's name in the Apple developer portal |
IOS_TEAM_ID | Your 10-character Apple team ID |
IOS_BUNDLE_ID | Your app's bundle ID, for example com.example.app |
IOS_KEYCHAIN_PASSWORD | Any password; the runner uses it for a temporary keychain |
If your Xcode scheme is not App, add a repository variable (not a secret) named IOS_SCHEME.
The output is a signed .ipa in the ios-release artifact.
Upload to the stores
The template stops at the signed files. Download them from the run's artifacts and upload them with Play Console and Transporter, or add your own upload step. It uses the certificate and profile route, not an App Store Connect API key.
Build and submit with your own Expo account
shipvo eas setup makes a Capacitor repo ready for eas build and eas submit on Android and iOS. It uses your own Expo account and your own store credentials. Shipvo writes files and never sees your Expo token.
Please read Expo's acceptable use policy before you use EAS Build for a Capacitor app, and check that your plan allows it: https://expo.dev/terms. Expo's terms limit what you may build with EAS Build, and Shipvo cannot check that for you. Expo's custom build docs: https://docs.expo.dev/custom-builds/get-started/ and https://docs.expo.dev/custom-builds/schema/.
Run it in the repo root. It needs capacitor.config.* and an android/ or ios/App/App.xcodeproj folder, and refuses anything else.
shipvo eas setup --dry-run # print every file it would write
shipvo eas setup # write them
shipvo eas setup --run # write them, then run `eas-cli init` and `eas-cli build:version:set -p ios`What it writes (existing files are kept; running it twice changes nothing):
eas.json: profilesshipvo-android(imagelatest) andshipvo-ios(imagemacos-tahoe-26.5-xcode-26.6, Node 22), plus matchingsubmitprofiles. Your own settings ineas.jsonare not changed, but the file is written back with 2-space indentation, so its formatting may change on the first run..eas/build/android.yml: JDK 21 install, web build,npx cap sync android,eas/inject_android_credentials,eas/run_gradle :app:bundleRelease..eas/build/ios.yml: web build,npx cap sync ios, the EAS credential steps (eas/resolve_apple_team_id_from_credentials,eas/configure_ios_credentials),ExportOptions.plistwritten in a YAML step (methodapp-store, team id fromeas/resolve_apple_team_id_from_credentials), thenxcodebuild archiveand export with distribution signing. Everyeas/step is one of EAS's built-in functions, and a test checks that.ios/App/App.xcodeproj/xcshareddata/xcschemes/App.xcscheme, the shared scheme, if it is missing.- A
.gitignoreline forios/App.xcodeproj.
The scheme link
EAS looks for the Xcode project at ios/*.xcodeproj, but Capacitor puts it at ios/App/App.xcodeproj. Build with shipvo eas build. It creates the link ios/App.xcodeproj -> App/App.xcodeproj when it is missing, then runs eas build with your arguments. The link is git-ignored. Do not commit it.
shipvo eas build -p ios --profile shipvo-ios
shipvo eas build -p android --profile shipvo-androidOne-time steps
npx eas-cli init
npx eas-cli build:version:set -p iosThen npx eas-cli submit -p ios --profile shipvo-ios (or -p android) after a build finishes.
Troubleshooting
eas-cli submitasks for a profile. Pass the profile the template creates:--profile shipvo-iosor--profile shipvo-android.- iOS says the build number was already used. Set it with
npx eas-cli build:version:set -p ios, then build again. shipvo simsaysNo index.html in <folder>. Build your web app first. ThewebDirfolder incapacitor.config.*is empty or missing. Runnpm run build, thennpx cap copy, and startshipvo simagain.capacitor.config webDir "<path>" is outside the project.webDirmust point inside the project folder. Change it to a folder under the project root, for exampledist.This is not a Capacitor project. Run the command in the folder that holdscapacitor.config.*and anandroid/orios/App/App.xcodeprojfolder.- An Expo app in the same repo opens as Expo. A project with
app.jsonorapp.config.*is treated as an Expo app and builds withexpo export, as before.
Next steps
- Store path: take the signed builds to Google Play and the App Store.
- Adapters: what a runtime port covers for Capacitor web bundles.
- Getting started: create an app and run it in the simulator.