Use for Capgo Cloud Build native iOS and Android workflows, including CLI login, API-key handling, iOS build onboarding, signing credential storage, build requests, store upload settings, output download links, and troubleshooting. Do not use for OTA bundle uploads or generic Capacitor setup unless

Capgo Native Builds Use this skill when the user wants Capgo to build native iOS or Android binaries in the cloud. When to Use This Skill The user asks for a Capgo Cloud Build, native build, signed IPA/APK/AAB, TestFlight/App Store build, Play Store build, or temporary build download link. The user needs Capgo CLI login, build API key setup, or help choosing between login , CAPGO TOKEN , and a, apikey . The user needs iOS build onboarding, Apple signing setup, Android keystore setup, Play service account setup, or explicitly asks for credential rotation. The user asks about build init , build request , build credentials save , build credentials update , build credentials list , build credentials clear , or build credentials migrate . Do not use this skill for JavaScript only OTA update uploads, generic CI/CD setup, or local native builds that do not involve Capgo Cloud Build. Operating Rules Use npx @capgo/cli@latest in user facing commands. Treat API keys, P12 passwords, keystore passwords, App Store Connect keys, and Play service account JSON as secrets. Use placeholders in new generic examples, but do not replace user provided secret values in files or commands with placeholders unless the user explicitly asks. Do not echo supplied secret values back to the user, and do not tell the user to rotate secrets unless they explicitly ask for rotation guidance. Prefer Capgo CLI build flows before inventing custom CI scripts. Confirm the platform, app ID, project path, desired output destination, and whether the user wants store upload or a temporary download link. Credentials are stored locally by the CLI and are only sent to Capgo for the build job. They are not stored permanently on Capgo servers and are deleted after the build process. See the [Capgo CLI credentials documentation](https://capgo.app/docs/cli/cloud build/credentials/). First Checks Before requesting a build, verify: The project is a Capacitor app and has the native folder for the target platform ( ios/ or android/ ). The Capgo app exists. If needed, add it first: The user has a Capgo API key with permission to trigger native builds for the app. Signing credentials exist or the workflow will create/save them before build request . The output destination is clear: Store upload: provide App Store Connect credentials for iOS or Play config for Android. Download link only: use output upload , optionally with output retention <duration . Authentication and Login Use login when the machine should remember the Capgo API key: Authentication precedence for build commands: 1. a, apikey <apikey on the command. 2. CAPGO TOKEN environment variable. 3. Local key saved by login local in .capgo . 4. Global key saved by login in ~/.capgo . Use CAPGO TOKEN for CI secrets. Use a, apikey when creating a single copy pasteable command for onboarding or support. Use login local only when the key should stay scoped to this repository; verify .capgo is ignored by git. Recommended Build Flows iOS Fast Path: build init For a first iOS cloud build, prefer the interactive onboarding command: If no key is saved, pass one explicitly: build init also has the alias build onboarding . It is best when the user wants the CLI to create and save iOS signing material with the fewest manual steps. What it handles: Verifies the App Store Connect API key. Creates or reuses Apple signing assets where possible. Registers or reuses the bundle ID. Creates App Store provisioning profiles. Saves build credentials into the same local store used by build request . Can request the first cloud build at the end. Persists onboarding progress under ~/.capgo credentials/onboarding/ so the user can resume. Saves recovery/support material under ~/.capgo credentials/support/ after unexpected failures. Use manual credential commands instead when the user already has certificates, profiles, or CI secrets prepared. Manual iOS Credential Save Use this when the user already has Apple signing files: For apps with extensions or multiple targets, repeat ios provisioning profile and map each bundle ID: For ad hoc iOS builds, set the distribution mode and collect the IPA with output upload : Manual Android Credential Save Use this when the user already has Android signing files: If the user only needs an APK/AAB download link and not Play upload, save output upload and omit or override Play upload: Use android flavor <flavor when the Android project has multiple product flavors. Request a Build Use build request [appId] after login and credentials are ready: Useful request options: platform ios android : required. path <path : project directory, default is the current directory. build mode debug release : defaults to release. ios scheme <scheme and ios target <target for custom Xcode projects. ios distribution app store ad hoc . android flavor <flavor for Android product flavors. output upload to create temporary IPA/APK/AAB download links. output retention <duration from 1h to 7d . no playstore upload to skip Play upload for an Android build. This requires output upload . skip build number bump when the project owns native build numbers itself. verbose for support/debugging. Example: collect an iOS ad hoc IPA link: Example: Android flavor with a download link instead of Play upload: Credential Management Build credentials are stored globally in ~/.capgo credentials/credentials.json by default. Add local to use .capgo credentials.json in the project root. Never commit either credentials file. List masked saved credentials: Update only changed fields: For iOS provisioning profile updates: By default, new ios provisioning profile entries are merged into the existing map. Use overwrite ios provisioning map only when replacing the whole mapping intentionally. Migrate legacy iOS provisioning credentials: Clear credentials only when the user wants removal: CI Guidance For CI, prefer secrets in environment variables instead of local credential files: Android CI commonly uses: CAPGO TOKEN ANDROID KEYSTORE FILE KEYSTORE KEY ALIAS KEYSTORE KEY PASSWORD KEYSTORE STORE PASSWORD PLAY CONFIG JSON or output upload Use repository or CI secret storage. Do not commit signing files or generated credential JSON. Troubleshooting No Capgo API key found : run npx @capgo/cli@latest login , set CAPGO TOKEN , or pass a YOUR API KEY . Insufficient permissions : verify the API key can access the app and includes native build permission. Missing output destination: add store upload credentials or enable output upload . No download link: request or save credentials with output upload and set output retention if the default TTL is too short. iOS signing failure: verify certificate password, Apple Team ID, distribution mode, and every bundle ID to provisioning profile mapping. Legacy iOS provisioning profile error: run npx @capgo/cli@latest build credentials migrate appId com.example.app platform ios . Android signing failure: verify keystore path, alias, key password, store password, and product flavor. Play upload should be skipped: use output upload no playstore upload . Monorepo path mismatch: pass the app specific path value and run from the app root when possible. Need support evidence: rerun the failing command with verbose . Supporting Docs Build command reference: https://capgo.app/docs/cli/reference/build/ Login command reference: https://capgo.app/docs/cli/reference/login/ Cloud Build getting started: https://capgo.app/docs/cli/cloud build/getting started/ iOS build setup: https://capgo.app/docs/cli/cloud build/ios/ Android build setup: https://capgo.app/docs/cli/cloud build/android/ Credential management: https://capgo.app/docs/cli/cloud build/credentials/

capgo-native-builds