--- description: Learn how to set up CI/CD for Capacitor apps. Compare DIY pipelines with managed solutions and find the best mobile DevOps approach for your team. title: CI/CD for Capacitor Apps: Choosing the Right Approach - Capawesome image: https://capawesome.io/docs/assets/images/social/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps.png --- [Skip to content ](#cicd-for-capacitor-apps-choosing-the-right-approach) [🖥️ Introducing the **Capacitor Electron Platform** — build desktop apps for macOS, Windows, and Linux. Free & open source. ](/blog/announcing-the-capacitor-electron-platform/) * [ SDKs ](/docs/sdks/) * [ Formbricks ](/docs/sdks/capacitor/formbricks/) * [ Geocoder ](/docs/sdks/capacitor/geocoder/) * [ Google Sign-In ](/docs/sdks/capacitor/google-sign-in/) * [ Grafana Faro ](/docs/sdks/capacitor/grafana-faro/) * [ Gyroscope ](/docs/sdks/capacitor/gyroscope/) * [ Haptics ](/docs/sdks/capacitor/haptics/) * [ Home Indicator ](/docs/sdks/capacitor/home-indicator/) * [ In-App Browser ](/docs/sdks/capacitor/in-app-browser/) * [ Install Referrer ](/docs/sdks/capacitor/install-referrer/) * [ Intercom ](/docs/sdks/capacitor/intercom/) * [ Intune ](/docs/sdks/capacitor/intune/) * [ Keep Awake ](/docs/sdks/capacitor/keep-awake/) * [ libSQL ](/docs/sdks/capacitor/libsql/) * [ Light Sensor ](/docs/sdks/capacitor/light-sensor/) * [ Live Update ](/docs/sdks/capacitor/live-update/) * [ Localization ](/docs/sdks/capacitor/localization/) * [ Mail Composer ](/docs/sdks/capacitor/mail-composer/) * [ Managed Configurations ](/docs/sdks/capacitor/managed-configurations/) * [ Maps Launcher ](/docs/sdks/capacitor/maps-launcher/) * [ Media Session ](/docs/sdks/capacitor/media-session/) * [ ML Kit ](/docs/sdks/capacitor/mlkit/) * [ Navigation Bar ](/docs/sdks/capacitor/navigation-bar/) * [ Network ](/docs/sdks/capacitor/network/) * [ NFC ](/docs/sdks/capacitor/nfc/) * [ Node.js ](/docs/sdks/capacitor/nodejs/) * [ OAuth ](/docs/sdks/capacitor/oauth/) * [ Passkeys ](/docs/sdks/capacitor/passkeys/) * [ Password Autofill ](/docs/sdks/capacitor/password-autofill/) * [ PDF Generator ](/docs/sdks/capacitor/pdf-generator/) * [ PDF Viewer ](/docs/sdks/capacitor/pdf-viewer/) * [ Pedometer ](/docs/sdks/capacitor/pedometer/) * [ Permissions ](/docs/sdks/capacitor/permissions/) * [ Phone Dialer ](/docs/sdks/capacitor/phone-dialer/) * [ Photo Editor ](/docs/sdks/capacitor/photo-editor/) * [ Photo Manipulator ](/docs/sdks/capacitor/photo-manipulator/) * [ PixLive ](/docs/sdks/capacitor/pixlive/) * [ PostHog ](/docs/sdks/capacitor/posthog/) * [ Printer ](/docs/sdks/capacitor/printer/) * [ Privacy Screen ](/docs/sdks/capacitor/privacy-screen/) * [ Proximity Sensor ](/docs/sdks/capacitor/proximity-sensor/) * [ Purchases ](/docs/sdks/capacitor/purchases/) * [ RealtimeKit ](/docs/sdks/capacitor/realtimekit/) * [ Root Detection ](/docs/sdks/capacitor/root-detection/) * [ Screen Brightness ](/docs/sdks/capacitor/screen-brightness/) * [ Screen Orientation ](/docs/sdks/capacitor/screen-orientation/) * [ Screen Reader ](/docs/sdks/capacitor/screen-reader/) * [ Screenshot ](/docs/sdks/capacitor/screenshot/) * [ Secure Preferences ](/docs/sdks/capacitor/secure-preferences/) * [ Settings Launcher ](/docs/sdks/capacitor/settings-launcher/) * [ Shake ](/docs/sdks/capacitor/shake/) * [ Silent Mode ](/docs/sdks/capacitor/silent-mode/) * [ SIM ](/docs/sdks/capacitor/sim/) * [ SMS Composer ](/docs/sdks/capacitor/sms-composer/) * [ Speech Recognition ](/docs/sdks/capacitor/speech-recognition/) * [ Speech Synthesis ](/docs/sdks/capacitor/speech-synthesis/) * [ Share Target ](/docs/sdks/capacitor/share-target/) * [ Square Mobile Payments ](/docs/sdks/capacitor/square-mobile-payments/) * [ SQLite ](/docs/sdks/capacitor/sqlite/) * [ Superwall ](/docs/sdks/capacitor/superwall/) * [ System WebView ](/docs/sdks/capacitor/system-webview/) * [ Tauri ](/docs/sdks/capacitor/tauri/) * [ Text Interaction ](/docs/sdks/capacitor/text-interaction/) * [ Text Zoom ](/docs/sdks/capacitor/text-zoom/) * [ Thermal State ](/docs/sdks/capacitor/thermal-state/) * [ Toast ](/docs/sdks/capacitor/toast/) * [ Torch ](/docs/sdks/capacitor/torch/) * [ Vault ](/docs/sdks/capacitor/vault/) * [ Volume ](/docs/sdks/capacitor/volume/) * [ Wallet ](/docs/sdks/capacitor/wallet/) * [ Wifi ](/docs/sdks/capacitor/wifi/) * [ YouTube Player ](/docs/sdks/capacitor/youtube-player/) * [ Zip ](/docs/sdks/capacitor/zip/) * [ Cordova ](/docs/sdks/cordova/) * [ Cloud ](/docs/cloud/) * [ Integrations ](/docs/cloud/live-updates/integrations/) * Concepts * Reference * [ Troubleshooting ](/docs/cloud/live-updates/troubleshooting/) * [ FAQ ](/docs/cloud/live-updates/faq/) * [ Native Builds ](/docs/cloud/native-builds/) * [ Set Up Environments ](/docs/cloud/native-builds/environments/) * [ Overwrite Native Configurations ](/docs/cloud/native-builds/native-configurations/) * [ Auto-Increment Build Numbers ](/docs/cloud/native-builds/auto-incrementing-build-numbers/) * [ Configure the Web Build Script ](/docs/cloud/native-builds/web-build-script/) * [ Build from a Monorepo ](/docs/cloud/native-builds/monorepo/) * [ Use pnpm, Yarn, or bun ](/docs/cloud/native-builds/package-managers/) * [ Install Private npm Packages ](/docs/cloud/native-builds/npm-private-registry/) * [ Override the Java Version ](/docs/cloud/native-builds/override-java-version/) * [ Custom iOS Provisioning Profiles ](/docs/cloud/native-builds/custom-ios-provisioning-profiles/) * [ Build without Git ](/docs/cloud/native-builds/build-without-git/) * [ Access Git Behind a Firewall ](/docs/cloud/native-builds/firewall-access/) * [ Integrations ](/docs/cloud/native-builds/integrations/) * Reference * [ Troubleshooting ](/docs/cloud/native-builds/troubleshooting/) * [ FAQ ](/docs/cloud/native-builds/faq/) * [ App Store Publishing ](/docs/cloud/app-store-publishing/) * [ Submit a Build ](/docs/cloud/app-store-publishing/submit-a-build/) * [ Submit Automatically After a Build ](/docs/cloud/app-store-publishing/submit-automatically/) * [ Troubleshooting ](/docs/cloud/app-store-publishing/troubleshooting/) * [ FAQ ](/docs/cloud/app-store-publishing/faq/) * [ Automations ](/docs/cloud/automations/) * [ Reference ](/docs/cloud/automations/reference/) * [ Troubleshooting ](/docs/cloud/automations/troubleshooting/) * [ FAQ ](/docs/cloud/automations/faq/) * [ Assist ](/docs/cloud/assist/) * [ CLI ](/docs/cloud/cli/) * APIs and SDKs * [ Webhooks ](/docs/cloud/webhooks/) * [ Integrations ](/docs/cloud/integrations/) * Account * [ Organization ](/docs/cloud/organizations/) * [ Two-Factor Enforcement ](/docs/cloud/organizations/two-factor-authentication/) * [ Audit Logs ](/docs/cloud/organizations/audit-logs/) * [ Billing ](/docs/cloud/organizations/billing/) * [ License Keys ](/docs/cloud/license-keys/) * [ AI ](/docs/ai/) * [ Insiders ](/docs/insiders/) * [ Billing & Plans ](/docs/insiders/billing-and-plans/) * [ FAQ ](/docs/insiders/faq/) * [ License ](https://capawesome.io/legal/eula/) * [ Support ](/docs/support/) * [ Contributing ](/docs/contributing/) * Contributing code * [ Code of Conduct ](/docs/contributing/code-of-conduct/) * [ Questions ](https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion#creating-a-discussion) * [ Blog ](/blog/) * Categories * [ Get Started ](#get-started) * [ Next Steps ](#next-steps) * [ Conclusion ](#conclusion) # CI/CD for Capacitor Apps: Choosing the Right Approach[¶](#cicd-for-capacitor-apps-choosing-the-right-approach "Permanent link") If you're still building and deploying your Capacitor app by hand, you're wasting time and shipping slower than you need to. CI/CD automates the repetitive parts — building, signing, and deploying — so you can focus on writing code. But setting it up for mobile apps isn't as straightforward as for web apps. Native builds, code signing, and app store submissions add layers of complexity that catch many teams off guard. In this post, we'll walk through what a CI/CD pipeline for Capacitor apps looks like, how to set one up yourself, and when it makes sense to use a managed solution like [Capawesome Cloud](/) instead. [ ![Build and deploy your Capacitor app with Capawesome Cloud](https://capawesome.io/assets/banners/cloud-build-and-deploy-capacitor-apps.png?t=1) ](/) ## Video Tutorial[¶](#video-tutorial "Permanent link") This walkthrough shows a complete Capacitor CI/CD pipeline from Git events to store delivery, which makes it easier to evaluate what is automated by default in a managed approach versus what you need to script in a DIY setup. ## What Is CI/CD?[¶](#what-is-cicd "Permanent link") CI/CD stands for **Continuous Integration** and **Continuous Delivery**. Continuous Integration means automatically building and testing your code every time you push changes. Continuous Delivery takes it further by automating the deployment process so your app can be released at any time with minimal manual effort. For web apps, this is fairly straightforward — push your code, run some tests, deploy to a server. For mobile apps, it's a different story. You need to compile native code for Android and iOS, manage code signing certificates and provisioning profiles, and submit builds to app stores that each have their own requirements. A CI/CD pipeline takes all of this off your plate and runs it automatically every time you push a change. If you're still weighing whether that automation is worth the effort, we make the full case in [Why Every Capacitor Team Needs a CI/CD Pipeline](/blog/why-every-capacitor-team-needs-ci-cd/). ## What a Capacitor CI/CD Pipeline Looks Like[¶](#what-a-capacitor-cicd-pipeline-looks-like "Permanent link") A typical CI/CD pipeline for a Capacitor app follows these stages: 1. **Install dependencies** — Install your Node.js packages and sync web assets to the native projects using `npx cap sync`. 2. **Build native projects** — Compile the Android APK/AAB using Gradle and the iOS IPA using Xcode. 3. **Code signing** — Sign the Android build with your keystore and the iOS build with your distribution certificate and provisioning profile. 4. **Run tests** — Execute unit tests, integration tests, or end-to-end tests to catch issues before they reach your users. 5. **Deploy** — Distribute the signed build to Google Play, the App Store, TestFlight, or deliver a live update directly to devices. Each of these steps introduces its own challenges. iOS builds require a macOS environment (here's [how to build iOS apps without owning a Mac](/blog/how-to-build-and-deploy-ios-apps-without-a-mac/)), and managing certificates across a team is notoriously painful. Let's look at the two main approaches to tackle this. ## The DIY Approach: GitHub Actions & Co.[¶](#the-diy-approach-github-actions-co "Permanent link") Many teams build their own CI/CD pipelines using platforms like GitHub Actions, GitLab CI, or Bitrise. Here's what that typically involves: * **macOS runners for iOS builds** — iOS apps can only be built on macOS. On GitHub Actions, macOS runners are free for open-source projects, but most teams work on closed-source apps where macOS minutes come at a significant premium. On GitLab, you need to provision and maintain your own macOS runners entirely. * **Code signing management** — You'll need to store your Android keystores, iOS certificates, and provisioning profiles as CI secrets and configure your build scripts to use them correctly. * **Build tooling** — Tools like [Fastlane](https://fastlane.tools/) are commonly used to automate the build and signing process, but they add another layer of configuration and maintenance. * **Keeping build tools up to date** — When Apple releases a new version of Xcode or macOS, you need to update your runners or build environments yourself. This often means waiting weeks for runner images to be updated or manually maintaining your own infrastructure. The DIY approach gives you full control over every step of the pipeline. But that control comes at a cost: significant setup time, ongoing maintenance, and the expertise needed to debug build failures that are often specific to the CI environment. ## The Managed Approach: Capawesome Cloud[¶](#the-managed-approach-capawesome-cloud "Permanent link") [Capawesome Cloud](/) takes a different approach. Instead of configuring and maintaining your own pipeline, you connect your Git repository and start building — no pipeline scripts or config files required for standard setups. Here's what makes it a strong option for Capacitor teams: **Get started in minutes.** Connect your Git repository from [GitHub](https://github.com/), [GitLab](https://gitlab.com/), [Bitbucket](https://bitbucket.org/), or [Azure DevOps](https://azure.microsoft.com/en-us/products/devops), and trigger your first native build without writing a single line of configuration. Capawesome Cloud detects your project setup and handles the rest. **More affordable than GitHub Actions.** Build minutes on Capawesome Cloud cost less than macOS runners on GitHub Actions. For teams that ship regularly, the savings add up fast. **Always running the latest build tools.** When Apple releases a new macOS or Xcode version, Capawesome Cloud has it available within days — not weeks. No manual upgrades, no waiting for third-party runner images to catch up. **Built and optimized for Capacitor.** Unlike generic CI runners, Capawesome Cloud is purpose-built for Capacitor apps. The build environment is tailored to what Capacitor needs, which means faster builds and fewer unexpected failures. **Live Updates included.** Need to push a hotfix without going through the app store review process? [Live Updates](/cloud/live-updates/) let you ship changes to HTML, CSS, and JavaScript instantly — right from the same platform. **Scales with your team.** Whether you're a solo developer or a large team shipping multiple apps, Capawesome Cloud grows with you. Unlimited build minutes are available on request for high-volume teams. ## Which Approach Is Right for You?[¶](#which-approach-is-right-for-you "Permanent link") There's no one-size-fits-all answer. Here's a quick way to think about it: **The DIY approach makes sense when:** * You have complex, custom workflows that require fine-grained control over every step. * Your team has dedicated DevOps expertise to set up and maintain the pipeline. * You're already running a mature CI/CD setup and just need to extend it for mobile. **A managed solution like Capawesome Cloud makes sense when:** * You want to get up and running fast without spending days writing pipeline scripts. * You're looking for affordable native builds without managing your own macOS infrastructure. * You'd rather spend your time building features than debugging CI environments. You don't have to pick one or the other. Many teams use a hybrid approach — running tests and linting in GitHub Actions while offloading native builds and deployments to Capawesome Cloud. ## FAQ[¶](#faq "Permanent link") ### Can I mix a DIY pipeline with a managed service instead of picking one?[¶](#can-i-mix-a-diy-pipeline-with-a-managed-service-instead-of-picking-one "Permanent link") Yes, and it's a common setup. Many teams keep tests and linting in GitHub Actions or GitLab CI — where they're already fast and free on standard runners — and offload just the native builds, signing, and store deployments to Capawesome Cloud, since that's the part that actually needs a macOS environment and certificate management. ### Why are GitHub Actions macOS runners expensive for closed-source projects?[¶](#why-are-github-actions-macos-runners-expensive-for-closed-source-projects "Permanent link") GitHub only waives macOS runner minutes for public, open-source repositories. Private repos pay a per-minute rate for macOS runners that's several times higher than Linux minutes, and iOS builds routinely take longer than web builds, so the cost compounds quickly for teams shipping multiple times a week. ### If I use a managed service, do I lose the ability to customize my build steps?[¶](#if-i-use-a-managed-service-do-i-lose-the-ability-to-customize-my-build-steps "Permanent link") Not entirely, but the trade-off is real. A managed service like Capawesome Cloud handles the standard Capacitor build/sign/deploy flow without config files, which is faster to set up but gives you less low-level control than a hand-written GitHub Actions or Bitrise pipeline where you script every step yourself. Teams with unusual native build requirements (custom Gradle tasks, non-standard Xcode schemes) are the ones most likely to need that extra control. ### How quickly does a managed CI/CD service pick up new Xcode versions?[¶](#how-quickly-does-a-managed-cicd-service-pick-up-new-xcode-versions "Permanent link") For Capawesome Cloud specifically, new macOS and Xcode versions are typically available within days of Apple's release. That matters because a new iOS version sometimes requires the latest Xcode to build against, and a DIY setup on GitHub Actions can be stuck waiting weeks for an updated runner image in the meantime. ### Does setting up CI/CD replace the need to manage signing certificates myself?[¶](#does-setting-up-cicd-replace-the-need-to-manage-signing-certificates-myself "Permanent link") It changes where you manage them, not whether you need them. Either approach still requires a valid iOS distribution certificate and provisioning profile, or an Android keystore — see [iOS Certificates and Provisioning Profiles Explained](/blog/ios-certificates-and-provisioning-profiles-explained/) for how those pieces fit together — a managed service just stores and injects them for you by name instead of you wiring them into CI secrets and build scripts by hand. ## Get Started[¶](#get-started "Permanent link") Ready to simplify your Capacitor CI/CD workflow? Book a demo to see how Capawesome Cloud can help your team ship faster. [Book a Capawesome Cloud Demo](https://cal.com/team/capawesome/cloud-demo) ## Next Steps[¶](#next-steps "Permanent link") For focused deep dives, see [Automate Builds with Git-Based Triggers](https://www.youtube.com/watch?v=39WNZroLZOE), [Managing Signing Certificates and Provisioning Profiles](https://www.youtube.com/watch?v=tKt3NNcFiCM), and [Using Environment Variables and Secrets](https://www.youtube.com/watch?v=aF1xIVZIuN8). ## Conclusion[¶](#conclusion "Permanent link") A CI/CD pipeline isn't optional for teams that want to ship Capacitor apps reliably. Building your own gives you full control but comes with real setup and maintenance costs — especially for iOS. Capawesome Cloud removes the hardest parts by providing optimized native builds, automatic code signing, live updates, and app store publishing out of the box. If you're evaluating your options, check out our post on [Capawesome Cloud as an alternative to Ionic Appflow](/blog/alternative-to-appflow/) for a detailed feature comparison, or see [The Best CI/CD Platforms for Capacitor Apps in 2026](/blog/comparing-ci-cd-platforms-for-capacitor-apps/) for a side-by-side of every platform still standing. If you already have a pipeline running, [common CI/CD pitfalls for Capacitor apps](/blog/ci-cd-for-capacitor-common-pitfalls/) covers the failure modes to watch for. Have questions or want to share your setup? Join the [Capawesome Discord server](https://discord.gg/VCXxSVjefW). And to stay updated on new features and guides, subscribe to the [Capawesome newsletter](/newsletter/). July 17, 2026 Back to top ```json { "@context": "https://schema.org", "@type": "BlogPosting", "headline": "CI/CD for Capacitor Apps: Choosing the Right Approach", "description": "Learn how to set up CI/CD for Capacitor apps. Compare DIY pipelines with managed solutions and find the best mobile DevOps approach for your team.", "image": "https://capawesome.io/assets/banners/cloud-build-and-deploy-capacitor-apps.png", "datePublished": "2026-02-21T00:00:00+00:00", "dateModified": "2026-07-17T00:00:00+00:00", "author": [ { "@type": "Person", "name": "Robin Genz", "url": "https://github.com/robingenz" } ], "publisher": { "@type": "Organization", "name": "Capawesome", "url": "https://capawesome.io", "logo": { "@type": "ImageObject", "url": "https://capawesome.io/assets/images/logo.svg" } }, "articleSection": "Capacitor", "keywords": ["Capacitor", "Cloud", "Guides"], "isPartOf": { "@type": "Blog", "@id": "https://capawesome.io/blog/#blog" }, "mainEntityOfPage": "https://capawesome.io/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps/", "url": "https://capawesome.io/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps/" } { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://capawesome.io/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://capawesome.io/blog/" }, { "@type": "ListItem", "position": 3, "name": "CI/CD for Capacitor Apps: Choosing the Right Approach", "item": "https://capawesome.io/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps/" } ] } {"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What Is CI/CD?", "acceptedAnswer": {"@type": "Answer", "text": "CI/CD stands for Continuous Integration and Continuous Delivery. Continuous Integration means automatically building and testing your code every time you push changes. Continuous Delivery takes it further by automating the deployment process so your app can be released at any time with minimal manual effort. For web apps, this is fairly straightforward — push your code, run some tests, deploy to a server. For mobile apps, it's a different story. You need to compile native code for Android and iOS, manage code signing certificates and provisioning profiles, and submit builds to app stores that each have their own requirements. A CI/CD pipeline takes all of this off your plate and runs it automatically every time you push a change. If you're still weighing whether that automation is worth the effort, we make the full case in Why Every Capacitor Team Needs a CI/CD Pipeline."}}, {"@type": "Question", "name": "Which Approach Is Right for You?", "acceptedAnswer": {"@type": "Answer", "text": "There's no one-size-fits-all answer. Here's a quick way to think about it: The DIY approach makes sense when: You have complex, custom workflows that require fine-grained control over every step. Your team has dedicated DevOps expertise to set up and maintain the pipeline. You're already running a mature CI/CD setup and just need to extend it for mobile. A managed solution like Capawesome Cloud makes sense when: You want to get up and running fast without spending days writing pipeline scripts. You're looking for affordable native builds without managing your own macOS infrastructure. You'd rather spend your time building features than debugging CI environments. You don't have to pick one or the other. Many teams use a hybrid approach — running tests and linting in GitHub Actions while offloading native builds and deployments to Capawesome Cloud."}}, {"@type": "Question", "name": "Can I mix a DIY pipeline with a managed service instead of picking one?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, and it's a common setup. Many teams keep tests and linting in GitHub Actions or GitLab CI — where they're already fast and free on standard runners — and offload just the native builds, signing, and store deployments to Capawesome Cloud, since that's the part that actually needs a macOS environment and certificate management."}}, {"@type": "Question", "name": "Why are GitHub Actions macOS runners expensive for closed-source projects?", "acceptedAnswer": {"@type": "Answer", "text": "GitHub only waives macOS runner minutes for public, open-source repositories. Private repos pay a per-minute rate for macOS runners that's several times higher than Linux minutes, and iOS builds routinely take longer than web builds, so the cost compounds quickly for teams shipping multiple times a week."}}, {"@type": "Question", "name": "If I use a managed service, do I lose the ability to customize my build steps?", "acceptedAnswer": {"@type": "Answer", "text": "Not entirely, but the trade-off is real. A managed service like Capawesome Cloud handles the standard Capacitor build/sign/deploy flow without config files, which is faster to set up but gives you less low-level control than a hand-written GitHub Actions or Bitrise pipeline where you script every step yourself. Teams with unusual native build requirements (custom Gradle tasks, non-standard Xcode schemes) are the ones most likely to need that extra control."}}, {"@type": "Question", "name": "How quickly does a managed CI/CD service pick up new Xcode versions?", "acceptedAnswer": {"@type": "Answer", "text": "For Capawesome Cloud specifically, new macOS and Xcode versions are typically available within days of Apple's release. That matters because a new iOS version sometimes requires the latest Xcode to build against, and a DIY setup on GitHub Actions can be stuck waiting weeks for an updated runner image in the meantime."}}, {"@type": "Question", "name": "Does setting up CI/CD replace the need to manage signing certificates myself?", "acceptedAnswer": {"@type": "Answer", "text": "It changes where you manage them, not whether you need them. Either approach still requires a valid iOS distribution certificate and provisioning profile, or an Android keystore — see iOS Certificates and Provisioning Profiles Explained for how those pieces fit together — a managed service just stores and injects them for you by name instead of you wiring them into CI secrets and build scripts by hand."}}], "url": "https://capawesome.io/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps/"} ```