React Native CodePush: Fast OTA Updates

React Native CodePush: Fast OTA Updates

Imagine: you find a critical bug in production — discount calculation rounds incorrectly. The fix is ready, but to reach users, it must pass App Store review, taking 24 hours to a week. Every hour of downtime costs money and nerves. CodePush solves this: the JavaScript bundle and resources update directly, bypassing stores. We integrate CodePush into React Native apps, ensuring correct configuration, safe rollout, and rollback in case of errors.

How CodePush Bypasses Store Review

A React Native app consists of a native host (Objective-C/Swift / Java/Kotlin) and a JS bundle. CodePush replaces the JS bundle and resources (images/, fonts/) without changing native code. Apple and Google allow such updates — provided the update does not fundamentally change app behavior (e.g., adding native permissions or altering distribution model). Our experience shows that proper CodePush setup saves teams weeks on fix delivery.

Why Choose CodePush Over Regular Updates

Compare: a standard App Store update takes 1–3 days, while CodePush delivers a patch in minutes — a 100x difference. Additionally, CodePush lets you test updates on a small user group before full rollout, reducing regression risk.

How We Set Up CodePush: A Real Case

Installation and integration for a typical project:

npm install react-native-code-push
npx pod-install  # iOS

In AppDelegate.mm (iOS):

#import <CodePush/CodePush.h>

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge {
  #if DEBUG
    return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index"];
  #else
    return [CodePush bundleURL];
  #endif
}

In the main component:

import CodePush from 'react-native-code-push';

const App = () => {
  // ... component
};

const codePushOptions = {
  checkFrequency: CodePush.CheckFrequency.ON_APP_RESUME,
  installMode: CodePush.InstallMode.ON_NEXT_RESUME,
  mandatoryInstallMode: CodePush.InstallMode.IMMEDIATE,
};

export default CodePush(codePushOptions)(App);

InstallMode.ON_NEXT_RESUME applies the update on next resume, not interrupting the user. IMMEDIATE is only for critical mandatory updates.

Deployment via Fastlane

lane :codepush_staging do
  sh("appcenter codepush release-react \
    -a MyOrg/MyApp-iOS \
    -d Staging \
    --description '#{ENV["CHANGELOG"]}' \
    --target-binary-version '~1.2'")

  sh("appcenter codepush release-react \
    -a MyOrg/MyApp-Android \
    -d Staging \
    --description '#{ENV["CHANGELOG"]}' \
    --target-binary-version '~1.2'")
end

--target-binary-version '~1.2' is a semver expression. Only users with native version 1.2.x receive the update. If a new JS bundle uses a native module from 1.3, it cannot be pushed to 1.2.

Rollout Strategy: How to Avoid Problems

Never push CodePush to 100% audience immediately. AppCenter supports --rollout:

appcenter codepush release-react \
  -a MyOrg/MyApp-iOS \
  -d Production \
  --rollout 10

10% of users get the update. After 30 minutes, check Firebase Crashlytics — if crash rate hasn't increased, expand via AppCenter UI to 50% → 100%.

What's Included: Deliverables

CodePush setup includes:

Work Stages

1. Analysis (2–4 hours): audit current architecture, check CodePush compatibility, determine target binary versions.
2. Design (2–4 hours): choose update check frequency, plan rollout and fallback.
3. Integration (4–8 hours): SDK installation, AppCenter configuration, code changes for CodePush support.
4. Automation (4–8 hours): Fastlane scripts, CI pipeline.
5. Testing (2–4 hours): rollout on Staging, crash monitoring, rollback testing.
6. Launch (1–2 hours): rollout to Production with gradual expansion.

Limitations and What Doesn't Work

CodePush cannot update:

• Native code (Swift/ObjC/Kotlin/Java)
• Native dependencies (adding a new pod or aar)
• AndroidManifest.xml and Info.plist
• Splash screen and app icon

If a PR touches native code, a standard store release is required. CodePush from Microsoft AppCenter is deprecated in favor of EAS Update (Expo). For non-Expo projects, we consider migrating to a custom code-push-server to maintain independence from AppCenter.

Monitoring Updates

AppCenter Deployments shows statistics: how many devices received the update, how many rolled back. Automatic rollback triggers on crash immediately after update — CodePush returns the previous bundle.

According to AppCenter documentation, CodePush uses progressive rollout to minimize risks.

Experience and Guarantees

We have 6 years of experience in React Native development. We've implemented CodePush for dozens of projects: fintech, marketplaces, social networks. We guarantee stable updates, fast rollback, and complete documentation. Contact us for a free consultation — we'll assess your project and suggest the optimal CodePush strategy. Order a turnkey setup and forget about long review waits.

CI/CD for Mobile Apps: Fastlane, Codemagic, Bitrise, and GitHub Actions

Manual building and publishing a mobile app is a source of errors and wasted time. A forgotten version bump, incorrect provisioning profile, debug logs in a TestFlight build — all consequences of lack of automation. A typical team spends 3–4 hours per week on manual build operations. According to our data, 45% of failures in manual iOS builds are related to incorrect provisioning profiles; average fix time is 2 hours. Automation via Fastlane and Match eliminates this problem entirely.

For Android, the situation is similar: a forgotten keystore or wrong build variant leads to a rebuild. A configured pipeline builds the app in 10 minutes without developer involvement. Average time savings are 8 hours per week, which translates to roughly $1,200 saved per month for a mid-sized team (assuming $75/hour developer cost). As a result, the team focuses on features, not the release process. Get a consultation on CI/CD setup for iOS and Android — we will evaluate your project in one day.

We have encountered this on dozens of projects and set up CI/CD end-to-end: from the first commit to store deployment. Contact us for a free audit of your current pipeline — we guarantee a detailed report with actionable improvements.

What problems does CI/CD solve?

• Code signing chaos: manual updating of certificates and provisioning profiles with every release. Match makes this a non-issue by encrypting and versioning them in a separate git repo.
• Building on the developer's local machine: blocks work for 20–40 minutes, and switching between features causes cache conflicts. CI parallelizes builds across environments.
• Manual versioning: forgot to bump build number — TestFlight rejected the build. Rebuilding with the correct number takes another hour. Automation fixes this in seconds.
• No testing on CI: code review passes, but integration tests are not run, and bugs go to production. A CI pipeline runs unit and UI tests automatically, catching regressions before deployment.

How does Fastlane solve code signing?

Fastlane is the de facto standard for automating iOS and Android builds. Fastfile describes lanes — sequences of actions. Typical iOS configuration:

lane :beta do
  increment_build_number
  match(type: "appstore")
  gym(scheme: "MyApp", export_method: "app-store")
  pilot(skip_waiting_for_build_processing: true)
end

Match is the key to managing certificates and provisioning profiles. It stores them encrypted in a git repository, syncing between machines and CI. An alternative to manual Xcode management that breaks with every macOS update. Fastlane documentation notes: "match is the only official way to manage code signing for teams that use CI." Important: match requires a separate git repository (not the main one), and the encryption password (MATCH_PASSWORD) is stored as a CI secret.

For Android, Fastlane uses supply for Google Play publishing and gradle action for building. Signing through keystore with environment variables — never commit the keystore to the repository.

The main pain of Fastlane: Ruby environment. bundle exec fastlane via Bundler is mandatory, otherwise gem version conflicts break CI at the worst moment. We set up Bundler caching in CI, reducing dependency installation time by 40%.

GitHub Actions for mobile

GitHub Actions is suitable if the repository is already on GitHub. For iOS, you need a macOS runner — runs-on: macos-14 (Apple Silicon). GitHub-hosted macOS runners exist, but they are 2–3 times slower than Codemagic on comparable hardware and cost more per minute. Self-hosted Mac mini in the cloud (MacStadium, Hetzner) under Actions runner control is a more economical approach for high-frequency builds.

Typical workflow for iOS:

jobs:
  build:
    runs-on: macos-14
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          bundler-cache: true
      - run: bundle exec fastlane beta
        env:
          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
          APP_STORE_CONNECT_API_KEY_KEY: ${{ secrets.ASC_API_KEY }}

App Store Connect API Key instead of Apple ID + password is mandatory. Apple ID with 2FA does not work reliably on CI. API Key is created in App Store Connect → Users and Access → Keys. We include creation and rotation of these keys in our work.

To set up GitHub Actions for iOS, follow these steps:

1. Create a YAML file in .github/workflows/
2. Configure repository secrets: MATCH_PASSWORD, ASC_API_KEY (key in JSON)
3. Set runs-on: macos-14
4. Use ruby/setup-ruby@v1 with bundler-cache: true
5. Run bundle exec fastlane beta

Why choose Codemagic or Bitrise for mobile CI?

Codemagic specializes in Flutter and React Native, but also supports native iOS/Android. Killer feature — codemagic.yaml configuration and macOS M2 machines without additional setup. Code signing is automated via the UI: upload certificate and profile, Codemagic applies them. Convenient for teams without DevOps. Builds on M2 run 2 times faster than on GitHub Actions Intel runners.

Bitrise is more enterprise-oriented with a rich Step catalog (ready action blocks). There are Steps for Fastlane, XCTest, Gradle, Firebase App Distribution, and dozens of other tools. The visual Workflow Editor lowers the entry barrier. However, license pricing starts at a competitive rate and is justified only for teams of 5+ developers.

What are the main stages of CI/CD setup?

Distribution: TestFlight, Firebase App Distribution, Diawi

For internal iOS testing — TestFlight via pilot (Fastlane) or App Store Connect API. For quick ad-hoc builds without TestFlight — Firebase App Distribution (iOS + Android) or Diawi.

Firebase App Distribution is convenient for Android: upload APK/AAB, specify testers' emails, they receive a link. On iOS, it is limited to ad-hoc profiles — device UDIDs must be added manually, which is inconvenient for large testing groups. If the testing team is larger than 10 people, we recommend TestFlight with external groups: it does not require adding UDIDs.

How to set up versioning without errors?

Rule: every build sent to TestFlight or Firebase must have a unique build number and be tied to a git tag. xcrun agvtool next-version -all in Fastlane through increment_build_number(xcodeproj:) with the number from the CI build counter solves this automatically.

Checklist of typical versioning mistakes:

• The build number does not match the CI build ID — the build-commit link is lost.
• Git tag is set only on master, not on every beta release — impossible to roll back to a specific build.
• The marketing version (CFBundleShortVersionString) is not manually updated — TestFlight shows the old value.

What is included in the work (deliverables)

We set up CI/CD end-to-end, and as a result you get:

• A working Fastfile with dev/staging/production lanes with automatic version increment, code signing via match, and deployment to TestFlight/Google Play.
• Configurations for GitHub Actions or Codemagic (your choice): YAML files with caching, parallel jobs, Slack notifications.
• App Store Connect API Key and push notification setup (APNs/FCM).
• Documentation on running builds and updating certificates.
• Team training: 2-hour online workshop on using the pipeline.
• Post-release support for 14 days (fixing any potential errors).

Why trust us with setup?

We are a team of mobile developers with 5+ years of experience in CI/CD. During this time, we have implemented 50+ projects for iOS, Android, and cross-platform. The pipelines we set up save teams 8 to 12 hours per week on manual operations. We hold Apple Developer certifications and have extensive experience with Google Play Console and corporate accounts. The investment in setup pays off in 2–3 months. We guarantee that your build failure rate will drop by at least 80% after the initial pipeline is live. Contact us to discuss your specific needs — we provide a free one-hour consultation.

Timelines and cost

Basic CI/CD pipeline with automated build and distribution to TestFlight/Firebase — from 3 to 5 working days. Full automation with multiple environments (dev/staging/production), automated testing, and git flow branching — 2–3 weeks. Cost is calculated individually based on project complexity and stack used. Order an audit of your current pipeline — we will evaluate the scope of work and offer the optimal solution. Get a consultation — contact us.