capawesome-cloud
Capawesome Cloud
Set up and manage native builds, live updates, and app store publishing for Capacitor apps using Capawesome Cloud.
Prerequisites
- A Capawesome Cloud account and organization.
- A Capacitor 6, 7, or 8 app.
- Node.js and npm installed.
- For Native Builds: The app must be in a Git repository (GitHub, GitLab, Bitbucket, or Azure DevOps).
- For Apple App Store Publishing: An active Apple Developer Program membership and an app created in App Store Connect.
- For Google Play Store Publishing: A Google Play Developer account and an app created in Google Play Console with at least one version uploaded manually.
General Rules
Before running any @capawesome/cli command for the first time, run it with the --help flag to review all available options.
Procedures
Step 1: Authenticate with Capawesome Cloud
npx @capawesome/cli login
For CI/CD, use token-based auth:
npx @capawesome/cli login --token <token>
Step 2: Create an App in Capawesome Cloud
Skip if the user already has an app ID.
npx @capawesome/cli apps:create
The CLI prompts for organization and app name, then outputs the app ID (UUID). Save for subsequent steps.
Step 3: Identify Required Feature(s)
Ask the user which Capawesome Cloud feature(s) to set up:
- Native Builds — Build iOS and Android apps in the cloud.
- Live Updates — Push OTA web updates to deployed apps.
- App Store Publishing — Automate submissions to Apple App Store or Google Play Store.
The user may select one or more features. Proceed to the corresponding sections below.
Native Builds
Read references/native-builds.md for the full native builds setup and usage procedure. This covers:
- Connecting a Git repository
- Uploading signing certificates (Android keystores, iOS .p12 + provisioning profiles)
- Configuring environments and secrets
- Configuring build settings (monorepos, custom build commands)
- Triggering builds
- Monitoring and downloading build artifacts
- Configuring native configuration overwriting with Trapeze
- Setting up CI/CD pipelines
Live Updates
Read references/live-updates.md for the full live updates setup and usage procedure. This covers:
- Installing the
@capawesome/capacitor-live-updateplugin - Configuring the plugin in Capacitor config
- Adding rollback protection
- Adding update logic (Always Latest, Manual Sync, Force Update)
- Configuring iOS Privacy Manifest
- Configuring version handling (versioned channels, versioned bundles)
- Testing the setup
App Store Publishing
Read references/app-store-publishing.md for the full app store publishing setup and usage procedure. This covers:
- Creating Apple App Store destinations (API Key or Apple ID auth)
- Creating Google Play Store destinations
- Deploying builds to destinations
- Building and deploying in one step
Error Handling
Native Builds
invalid source release: 21→ SetJAVA_VERSIONenv var to17or21. Readreferences/build-troubleshooting.md.JavaScript heap out of memory→ SetNODE_OPTIONSenv var to--max-old-space-size=4096. Readreferences/build-troubleshooting.md.- Authentication errors → Re-run
npx @capawesome/cli login. For CI/CD, verify the token. - Missing signing certificate → Upload via
apps:certificates:create. Readreferences/certificates-android.mdorreferences/certificates-ios.md. - Expired provisioning profile → Regenerate in Apple Developer Portal and re-upload. Read
references/certificates-ios.md. - Web build step fails → Ensure
package.jsonhascapawesome:buildorbuildscript. Readreferences/build-configuration.md.
Live Updates
npx cap syncfails → Verify plugin version matches Capacitor version inpackage.json.- Bundles not applied → Ensure
LiveUpdate.ready()is called beforereadyTimeoutexpires. - App reverts to default bundle after restart →
ready()likely not called. Add it early in app init. - Upload auth errors → Re-run
npx @capawesome/cli login. - Updates not detected with
autoUpdateStrategy: "background"→ Updates only checked if last check was >15 min ago. Force-close and restart. - Read
references/live-update-plugin-api.mdfor the full SDK API reference. - Read
references/live-update-faq.mdfor compliance, billing, and limitations.
App Store Publishing
- Authentication errors → Re-run
npx @capawesome/cli login. - Destination creation fails → Verify credentials. Read
references/apple-app-store-credentials.mdorreferences/google-play-store-credentials.md. - iOS build not appearing in TestFlight → Build processing may take time. Common causes: build number not incremented, missing Privacy Descriptions in
Info.plist, insufficient permissions. - Google Play deployment fails → Ensure first version was uploaded manually. Verify service account has Release permissions.
- Deployment timeout → Use
--detachedflag and check logs withapps:deployments:logs. apps:deployments:createfails with "build not found" → Ensure the build completed successfully.- Cancel a stuck deployment →
npx @capawesome/cli apps:deployments:cancel --app-id <APP_ID> --deployment-id <DEPLOYMENT_ID>.
Related Skills
capacitor-app-development— For general Capacitor development topics, CI/CD patterns, and troubleshooting.capawesome-cli— For the full Capawesome CLI command reference, project configuration, and CI/CD integration details.capacitor-plugins— For installing and configuring Capacitor plugins, including the@capawesome/capacitor-live-updateplugin.ionic-appflow-migration— For migrating existing Ionic Appflow projects to Capawesome Cloud.capacitor-in-app-purchases— For setting up in-app purchases and subscriptions before publishing to app stores.