Capgo Live Updates

Capgo Live Updates

By Martin DonadieuTechnology
Download on the App Store

Capgo Live Updates episodes

  • Comparing Ci Cd Platforms For Ios Apps
    The episode explains why iOS CI/CD is far more complex than web deployment, focusing on Apple’s April 28 2026 mandate to use Xcode 26 and the iOS 26 SDK, the shift to Apple‑Silicon macOS runners, and the deprecation of legacy services like Microsoft App Center. Listeners learn how authentication now requires a .p8 App Store Connect API key, how signing certificates and provisioning profiles must be managed securely, and why the hardware licensing model drives higher costs on platforms such as GitHub Actions and GitLab.
    The discussion then compares dedicated iOS‑focused services—Xcode Cloud, Bitrise, Codemagic, and self‑hosted AppCircle—and introduces Capco Build for Capacitor apps, which lets a Linux runner offload the macOS build step. It also covers remote iOS simulators from Argent Cloud and practical migration pitfalls like exporting .p12 keys, build‑number continuity, and export‑compliance flags.
    Topics:
    - Apple’s Xcode 26 requirement and its impact on CI pipelines
    - Using .p8 API keys to replace fragile Apple ID logins
    - Choosing between Xcode Cloud, Bitrise, Codemagic, and AppCircle
    - Capco Build for hybrid Capacitor apps to avoid macOS runners
    - Migration checklist: certificates, build numbers, and encryption flags
    Full article
    https://capgo.app/blog/comparing-ci-cd-platforms-for-ios-apps/
    25 min
  • Comparing Ci Cd Platforms For Cordova Apps
    The episode explains how the shutdown of services like Microsoft App Center, Ionic AppFlow, and PhoneGap Build forces Cordova developers to rebuild their CI/CD pipelines from scratch. Listeners learn why the build environment, code signing, and over‑the‑air updates now fall entirely on their shoulders, and how to choose between self‑hosted runners, GitHub Actions, Bitrise, or AppCircle for reliable builds. The discussion also covers the limitations of iOS builds on Linux runners and the need for macOS agents with Xcode 26.
    Practical steps include extracting signing certificates before a service disappears, syncing version codes to avoid store rejections, configuring fresh Google Play and App Store API keys, replicating all environment variables in the new CI, and validating the new pipeline with internal and beta tracks before going live. The hosts also compare Cordova to Capacitor, showing how Capacitor’s static native projects and Capco’s native‑build service can eliminate costly macOS runners while enabling safe web‑only OTA updates.
    Topics:
    - How to migrate Cordova CI/CD to GitHub Actions, Bitrise, or self‑hosted runners
    - Setting up secure code signing and versioning for Android and iOS stores
    - Using Capco’s Cordova updater for web‑only over‑the‑air patches
    Full article
    https://capgo.app/blog/comparing-ci-cd-platforms-for-cordova-apps/
    24 min
  • Comparing Ci Cd Platforms For Android Apps
    The episode breaks down the essential components of an Android CI/CD pipeline in 2026—Linux, JDK 21, the Android SDK, and Gradle—and explains why every platform ultimately runs the same build commands. It then highlights the real differentiators: how each service secures keystores, manages Google Play authentication, and caches Gradle dependencies to keep builds fast and reliable.
    Listeners learn practical trade‑offs between DIY runners like GitHub Actions or GitLab CI and managed solutions such as Bitrise, Codemagic, AppCircle, Azure DevOps, and CircleCI. The discussion also covers common pitfalls like keystore loss, version‑code collisions, memory‑starved JVM settings, and service‑account misconfiguration, plus how Capco’s specialized pipeline and live‑update feature can bypass store review for web‑layer fixes.
    Topics:
    - Comparing DIY runners versus managed mobile CI/CD platforms
    - Security handling of keystores and service accounts
    - Gradle caching and JVM memory tuning to speed builds
    - Managing version codes and Google Play upload permissions
    - Using Capco’s live‑update capability for instant web‑layer fixes
    Full article
    https://capgo.app/blog/comparing-ci-cd-platforms-for-android-apps/
    24 min
  • Cloud App Performance
    The episode explains how mobile teams can bypass slow App Store reviews by using live‑update pipelines that treat delivery performance as a critical metric. It breaks down the four pillars—latency, throughput, availability, and consistency—and shows why average server times are misleading when a hotfix must reach thousands of users instantly.
    Listeners learn practical tactics such as measuring tail‑latency (P95/P99) instead of averages, using continuous profiling to pinpoint bundle‑parsing bottlenecks, and staging rollouts with explicit rollback triggers. The discussion also covers why edge CDNs can hurt hotfixes, how to pre‑compute manifests, and the importance of error‑budget‑driven release policies.
    Topics:
    - four‑pillar model for delivery performance
    - tail‑latency metrics and adoption rate monitoring
    - continuous profiling to debug bundle parsing delays
    - staged rollout workflow with predefined rollback triggers
    - limitations of edge caching for emergency updates
    Full article
    https://capgo.app/blog/cloud-app-performance/
    21 min
  • Ci Cd For Cordova Apps
    Mobile developers are forced to replace the vanished managed CI/CD services that once powered Cordova apps. The episode explains how to rebuild a reproducible pipeline from scratch, covering the need for Linux runners for Android, macOS runners for iOS, and strict version pinning of Node, Cordova CLI, and platform SDKs. Listeners learn how to keep secrets out of source control with envsubst and GitHub Secrets, and why committing generated platform folders leads to version drift and repository bloat.
    The discussion also shows how Capgo Live updates let teams ship over‑the‑air JavaScript fixes without App Store review, and when it makes sense to migrate from Cordova to Capacitor to avoid macOS build servers. Real‑world trade‑offs, such as legacy plugins that lock teams into Cordova, are examined to help decide the right migration timing.
    Topics:
    - Setting up reproducible CI runners and pinning tool versions
    - Injecting build secrets securely with envsubst and encrypted vaults
    - Avoiding version drift by not committing platform and plugins folders
    - Using Capgo Live updates for instant OTA fixes
    - Evaluating migration to Capacitor to eliminate macOS build requirements
    Full article
    https://capgo.app/blog/ci-cd-for-cordova-apps/
    16 min
  • Ci Cd For Capacitor Common Pitfalls
    Capacitor CI/CD pipelines often fail for reasons unrelated to the app's feature code. The episode explains how the web‑to‑native handoff can serve stale assets when capsync runs before the web build finishes, and how leaving a live‑reload URL in the config can break production builds. Listeners learn to enforce a strict order: run the web build, verify the output folder, then run capsync, and to keep dev‑only URLs out of the repository by using environment variables that are omitted in CI.
    The discussion also covers version pinning for Node, JDK, and Xcode to avoid hidden tool‑chain breaks, and the complexities of code signing on CI runners, including temporary keychain creation and using App Store Connect API keys. Practical tips include separating cheap Linux jobs for web builds from expensive macOS jobs, automating build‑number increments, and using a diff step to prevent over‑the‑air updates that require new native plugins.
    Topics:
    - Enforce linear build order to avoid stale UI
    - Remove live‑reload URLs from production config
    - Pin toolchain versions to ensure stable builds
    - Automate code signing with temporary keychains and API keys
    - Detect native plugin changes before OTA updates
    Full article
    https://capgo.app/blog/ci-cd-for-capacitor-common-pitfalls/
    0 min
  • Ci Cd Continuous Integration
    The episode explains how continuous integration (CI) for Capacitor JS apps works beyond simple linting, running commands like npm ci and npx capsync to verify that web assets and native plugins integrate correctly in a clean environment. It then distinguishes continuous delivery from continuous deployment, showing how risk tolerance determines whether a human must approve the final App Store or Google Play release or whether the pipeline can push updates automatically.
    Listeners learn practical ways to improve their mobile CI/CD pipeline: using test impact analysis to run only the tests affected by a change, storing signed IPA/AAB artifacts for reproducible releases, and separating store‑lane native updates from over‑the‑air live‑update lanes powered by Capgo. The discussion also covers essential security guardrails—dependency scanning, secret detection, and protected environments—and a maturity checklist that ensures any engineer can safely operate the pipeline during an incident.
    Topics:
    - Running npm ci and npx capsync to validate builds in a sterile CI environment
    - Choosing continuous delivery vs. continuous deployment based on risk and compliance
    - Applying test impact analysis to cut testing time by targeting only affected tests
    - Storing and promoting signed mobile artifacts to guarantee reproducible releases
    - Implementing security gates like dependency scanning and secret detection in the pipeline
    Full article
    https://capgo.app/blog/ci-cd-continuous-integration/
    0 min
  • Capgo Version Build Vs Version Name
    Capgo’s version build and version name are two separate versioning concepts that control OTA updates for Capacitor apps. Version build represents the native binary baseline – the iOS Info.plist CFBundleShortVersionString or Android Gradle config.versionName – and never changes without a new store release. Version name tracks the JavaScript bundle version from package.json or the Capgo CLI upload. Capgo validates update eligibility by comparing the channel’s target version directly against the native baseline, ignoring the currently installed web bundle, which prevents incompatible code from reaching devices.
    The discussion walks through where each version value lives, how configuration overrides in capacitor.config.ts can hijack the baseline, and why developers must verify the actual device‑reported native version during debugging. It also clarifies common confusions with Android WebView versions and stresses the need for explicit version handling in CI/CD pipelines to avoid silent mismatches that block critical updates.
    Topics:
    - Distinguishing native baseline (version build) from web bundle version (version name)
    - Locating version values in iOS Info.plist, Android Gradle, and package.json
    - Handling configuration overrides and CI/CD best practices for explicit versioning
    - Understanding Capgo’s channel eligibility checks against the native baseline
    - Avoiding confusion with Android WebView version versus Capgo version numbers
    Full article
    https://capgo.app/blog/capgo-version-build-vs-version-name/
    0 min
  • Capgo Pull Request Preview Cleanup Api Key
    The episode explains why using a dedicated, restricted API key for Capgo pull‑request preview cleanup is critical. It walks through the risks of reusing a master key, such as exposing credentials in logs and granting excessive permissions, and shows how to create a clearly named “CAPGO‑PREVIEW‑CLEANUP‑KEY” stored in a vault. Listeners learn the step‑by‑step process of safely deleting preview bundles: verify the PR is closed, confirm no active uploads, instruct devices to detach, then delete the server resources only after all checks pass.
    The discussion also covers how to avoid catastrophic wildcard deletions by fetching exact bundle IDs, implementing three security gates (format, channel alignment, commit SHA verification), handling race conditions between cleanup and deployment jobs, and enforcing strict logging hygiene. Finally, it stresses double‑checking that only targeted previews are removed and that production bundles remain untouched, embodying the principle of failing closed.
    Topics:
    - Create a limited‑scope API key and store it securely
    - Use exact bundle IDs instead of name‑based wildcards
    - Apply three validation gates before deletion
    - Coordinate device detachment and server cleanup to prevent crashes
    - Log actions without exposing credentials and verify final state
    Full article
    https://capgo.app/blog/capgo-pull-request-preview-cleanup-api-key/
    24 min
  • Capgo Pause Rollout Vs Rollback
    Capgo’s pause‑rollout versus rollback decision‑making is explored through a realistic outage scenario. Listeners learn how Capacitor.js apps use Capgo’s OTA platform to swap web assets, why pausing a progressive rollout limits exposure, and when a full rollback to a stable bundle is truly warranted. The episode highlights the limits of OTA updates— they can’t fix backend outages or add missing native plugins— and stresses the need for careful verification before changing the user base.
    The discussion also covers how to confirm a rollback’s success by monitoring channel analytics, filtering metrics to the affected bundle, and physically testing on a device. Finally, it advises against automating emergency rollbacks, recommending runbooks, manual approval, and fire‑drill rehearsals to build reliable response habits.
    Topics:
    - Distinguishing pause (containment) from rollback (recovery) in Capgo deployments
    - Verifying OTA changes with bundle‑specific analytics and real‑device testing
    - Understanding OTA limitations: no backend fixes or native code additions
    - Avoiding blind automation of rollbacks and using manual approval runbooks
    Full article
    https://capgo.app/blog/capgo-pause-rollout-vs-rollback/
    15 min

About Capgo Live Updates

From the publisher's feed

Capgo Live Updates is a podcast for developers building mobile apps with Capacitor and Ionic. Each episode explores an article from the Capgo blog, covering over-the-air updates, native integrations,…