DeployPulse

Migrating from App Center to DeployPulse

Microsoft App Center CodePush was retired in March 2025. DeployPulse is a drop-in replacement: the same CodePush API and over-the-air update protocol, with active development and new capabilities App Center never offered (Auto Rollback, Code Signing, differential packages).

Migrating takes three changes to your app:

  1. Switch the npm package from react-native-code-push to @deploypulseio/react-native-code-push, update your imports and the Android codepush.gradle path, and reinstall CocoaPods. The API is the same, so your codePush calls do not change.
  2. Point the SDK at DeployPulse with your new deployment keys. The server URL is optional, because the fork already defaults to DeployPulse; replace or remove the old App Center URL if your config sets one.
  3. Ship your next app build. The package and the deployment keys are native changes, so they reach users through the app stores, not over the air.

Why switch packages: Microsoft's react-native-code-push is deprecated on npm and no longer supported, and it does not support the New Architecture. The main community fork is now run by Codemagic, which sells a competing update service. @deploypulseio/react-native-code-push is our fork, maintained for DeployPulse.

Our fork needs React Native 0.76 or later and an iOS deployment target of 15.5. On an older React Native version, keep Microsoft's package for now: do steps 2 and 3, and set the server URL keys too, since Microsoft's package defaults to App Center. See Compatibility.

Coming from somewhere else? Moving off EAS Update covers Expo apps on EAS Update, and Other OTA services covers Stallion, Hot Updater, Codemagic Patch and Pushy. Apps on another CodePush-compatible SDK (Codemagic, Revopush, Bitrise, Appcircle, AppZung) follow this page, with the notes in Other SDKs.


Prerequisites

  • dpctl CLI: npm install -g @deploypulseio/dpctl
  • Node.js 20.19 or later, or 22.12 or later
  • Your existing App Center app names (for reference when re-creating apps)

Step 1 - Create a DeployPulse Account

Sign up at app.deploypulse.io. After registering you will land on the dashboard where you can create your first app.


Step 2 - Re-create Your Apps

DeployPulse maintains separate apps per platform, matching App Center's convention:

dpctl app add MyApp-iOS --platform ios
dpctl app add MyApp-Android --platform android

Each app is automatically created with Staging and Production deployments.


Step 3 - Get Your Deployment Keys

dpctl deployment ls MyApp-iOS

The dashboard also shows deployment keys under App → Deployments → key icon.


Step 4 - Switch the SDK Package

Replace Microsoft's package with ours:

npm uninstall react-native-code-push
npm install @deploypulseio/react-native-code-push

With Yarn or pnpm:

yarn remove react-native-code-push && yarn add @deploypulseio/react-native-code-push
pnpm remove react-native-code-push && pnpm add @deploypulseio/react-native-code-push

Then reinstall the iOS pods so the native module is linked from the new package:

cd ios && pod install && cd ..

Then update the package name where your app refers to it. In JavaScript, change every import:

// Before
import codePush from 'react-native-code-push'

// After
import codePush from '@deploypulseio/react-native-code-push'

On Android, change the codepush.gradle path in android/app/build.gradle:

apply from: "../../node_modules/@deploypulseio/react-native-code-push/android/codepush.gradle"

If android/settings.gradle still links the old package by hand, remove those lines. React Native links the new package on its own, and keeping them builds the module twice:

// Remove these from android/settings.gradle (keep ':app' and any other projects in the include)
include ':app', ':react-native-code-push'
project(':react-native-code-push').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-code-push/android/app')

Also remove implementation project(':react-native-code-push') from android/app/build.gradle if it is there.

Your codePush calls stay as they are. See Which SDK do I need? for the full comparison.


Step 5 - Update Mobile Config

iOS - Info.plist

Replace the old App Center deployment key. The server URL entry is optional, since the fork defaults to DeployPulse, but if your Info.plist still sets an App Center URL, change it or remove it:

<key>CodePushDeploymentKey</key>
<string>YOUR_DEPLOYPULSE_IOS_KEY</string>
<key>CodePushServerURL</key>
<string>https://apps.deploypulse.io</string>

Android - strings.xml

The same applies here: set the new deployment key, and change or remove any App Center server URL.

<string name="CodePushDeploymentKey">YOUR_DEPLOYPULSE_ANDROID_KEY</string>
<string name="CodePushServerUrl">https://apps.deploypulse.io</string>

See the iOS Setup and Android Setup guides for full configuration details.

If your keys differ per build (an Xcode $(CODEPUSH_KEY) build setting, Gradle resValue lines per build type, react-native-config .env files), see Build configurations.

The SDK reads these values from Info.plist and strings.xml when the app starts, so the switch reaches users with your next app build. Release it through the App Store and Google Play as usual; once users are on that build, they receive updates from DeployPulse.


Step 6 - Update CI/CD

Replace appcenter codepush release-react with dpctl release-react in your pipelines:

# Before (App Center CLI)
appcenter codepush release-react -a MyOrg/MyApp-iOS -d Production

# After (dpctl)
DEPLOYPULSE_ACCESS_KEY="$DEPLOYPULSE_ACCESS_KEY" dpctl release-react MyApp-iOS ios --deploymentName Production

See the GitHub Actions, Bitrise, CircleCI, GitLab CI/CD, or Jenkins guides for full pipeline examples, and CI below for how each flag translates.


CLI Command Mapping

App Center CLIdpctl equivalent
appcenter logindpctl login
appcenter apps listdpctl app ls
appcenter apps create -n <name>dpctl app add <name>
appcenter apps delete -a <app>dpctl app rm <name>
appcenter codepush deployment list -a <app>dpctl deployment ls <app>
appcenter codepush deployment add -a <app> <name>dpctl deployment add <app> <name>
appcenter codepush release-react -a <app>dpctl release-react <app> <platform>
appcenter codepush patch -a <app> <deployment> <label>dpctl patch <app> <deployment> <label>
appcenter codepush promote -a <app> -s <src> -d <dest>dpctl promote <app> <src> <dest>
appcenter codepush rollback -a <app> <deployment>dpctl rollback <app> <deployment>
appcenter codepush deployment history -a <app> <deployment>dpctl deployment history <app> <deployment>

Other SDKs

Several services ship their own fork of the CodePush SDK. They speak the same CodePush protocol, so a build with one of them updates from DeployPulse once it carries a DeployPulse deployment key and the DeployPulse server URL. Each SDK spells those settings its own way.

In a bare React Native project, every SDK below except AppZung reads the same keys as ours: CodePushDeploymentKey and CodePushServerURL in Info.plist, and CodePushDeploymentKey and CodePushServerUrl in strings.xml. Set the server URL even if your config has none today: these SDKs default to their own service or to the retired App Center, not to DeployPulse.

In an Expo app, set them through the SDK's own config plugin entry:

PackageServiceDefault serverExpo plugin entryPlugin options
@code-push-next/react-native-code-pushCodemagicApp Center (retired)@code-push-next/react-native-code-push/expoCodePushDeploymentKey, CodePushServerURL on both platforms
@revopush/react-native-code-pushRevopushhttps://api.revopush.org/@revopush/expo-code-push-pluginCodePushDeploymentKey, CodePushServerUrl on both platforms, optional CodePushPublicKey
@bitrise/code-push-sdkBitriseApp Center (retired)@bitrise/code-push-sdk/expoCodePushDeploymentKey, CodePushServerURL on both platforms, optional CodePushPublicKey and CodePushEnableDeltaUpdates
@appcircle/react-native-code-pushAppcircleAppcircle on Android, App Center on iOSNoneBare projects only
@appzung/react-native-code-pushAppZunghttps://codepush.appzung.com/@appzung/expo-config-code-pushCodePushReleaseChannelPublicId, no server URL option

For example, with Codemagic's SDK:

{
  "expo": {
    "plugins": [
      [
        "@code-push-next/react-native-code-push/expo",
        {
          "ios": {
            "CodePushDeploymentKey": "YOUR_IOS_KEY",
            "CodePushServerURL": "https://apps.deploypulse.io"
          },
          "android": {
            "CodePushDeploymentKey": "YOUR_ANDROID_KEY",
            "CodePushServerURL": "https://apps.deploypulse.io"
          }
        }
      ]
    ]
  }
}

With Revopush's plugin the option is CodePushServerUrl instead, on both platforms. Give every plugin both an ios and an android block: these plugins skip a platform they are not given.

AppZung names its deployment key CodePushReleaseChannelPublicId, in Info.plist and strings.xml (and releaseChannelPublicId when passed from JavaScript). In a bare project, put your DeployPulse deployment key there and set CodePushServerURL and CodePushServerUrl as above. A CodePushSigningPublicKey is an RS256 public key: register it with dpctl app set-public-key and sign releases as Code Signing describes. AppZung's Expo plugin has no server URL option, so an Expo app on AppZung cannot be pointed at DeployPulse through it: switch to our SDK and its plugin (Expo Setup).

Switching to our SDK

These SDKs work, but we recommend @deploypulseio/react-native-code-push. It is the SDK we maintain and test against DeployPulse, it defaults to DeployPulse so there is no server URL to get wrong, and it ships an Expo config plugin.

Every one of these SDKs except AppZung uses the same native module names as ours (the com.microsoft.codepush.react Java package and the CodePush pod), so switching follows Step 4 with their package name in place of react-native-code-push: uninstall theirs, install ours, update the imports and the codepush.gradle path, replace their Expo plugin entry with ours, and run pod install. Never have two CodePush packages installed at once: both link a native module named CodePush, and the build fails. See Which SDK do I need?.


Expo plugins

Some Expo apps configure CodePush through their own config plugin, a file such as plugins/withCodePush.js listed in the app config's plugins. If yours does, keep using it and make sure it writes these values:

PlatformFileKeys
iOSInfo.plistCodePushDeploymentKey, CodePushServerURL
Androidstrings.xmlCodePushDeploymentKey, CodePushServerUrl (lowercase "rl")

The server URL is https://apps.deploypulse.io. A minimal version of that part of a plugin:

// plugins/withCodePush.js
const { AndroidConfig, withInfoPlist, withStringsXml } = require('expo/config-plugins')

const SERVER_URL = 'https://apps.deploypulse.io'

module.exports = function withCodePush(config, { iosKey, androidKey }) {
  config = withInfoPlist(config, (c) => {
    c.modResults.CodePushDeploymentKey = iosKey
    c.modResults.CodePushServerURL = SERVER_URL
    return c
  })
  return withStringsXml(config, (c) => {
    c.modResults = AndroidConfig.Strings.setStringItem(
      [
        { $: { name: 'CodePushDeploymentKey', translatable: 'false' }, _: androidKey },
        { $: { name: 'CodePushServerUrl', translatable: 'false' }, _: SERVER_URL },
      ],
      c.modResults,
    )
    return c
  })
}

If your plugin also writes the codepush.gradle line or the bundleURL and getJSBundleFile code, check that they name the package you have installed.

Do not add the @deploypulseio/react-native-code-push plugin entry next to a hand-made plugin. Both apply the same native wiring, and a doubled codepush.gradle line or bundle hook breaks the build. Use one or the other: keep your plugin, or delete it and follow Expo Setup.


Monorepos

In a monorepo, the package manager usually hoists dependencies into the node_modules folder at the repository root instead of the app's own folder. Native files that point into node_modules by a relative path then point at nothing.

The codepush.gradle line. apply from: in android/app/build.gradle is relative to android/app, so the usual ../../node_modules/... means the app folder's node_modules. For an app in apps/mobile whose dependencies are hoisted to the root, go two levels further up:

apply from: "../../../../node_modules/@deploypulseio/react-native-code-push/android/codepush.gradle"

To see where the package actually is, run this from the app folder:

node -p "require.resolve('@deploypulseio/react-native-code-push/package.json')"

A Podfile line that names the package by path (pod 'CodePush', :path => ...) needs the same care.

Keeping the package in the app folder. You can also tell the package manager not to hoist it:

  • Yarn 1 workspaces: add it to nohoist in the root package.json:

    {
      "workspaces": {
        "packages": ["apps/*", "packages/*"],
        "nohoist": ["**/@deploypulseio/react-native-code-push", "**/@deploypulseio/react-native-code-push/**"]
      }
    }
    
  • Yarn 2 and later with nodeLinker: node-modules: set nmHoistingLimits: workspaces in .yarnrc.yml.

  • pnpm: its default layout links every direct dependency into the app's own node_modules, so the default path works. Settings that hoist everything (node-linker=hoisted) bring the problem back.

  • npm workspaces have no nohoist: use the relative path to the root node_modules.

Expo apps on our config plugin. The plugin writes a fixed line, apply from: "../../node_modules/@deploypulseio/react-native-code-push/android/codepush.gradle", which assumes the package is in the app folder's node_modules. In a hoisted monorepo that file does not exist and the Android build fails. Keep the package in the app folder with one of the settings above. Editing the generated build.gradle by hand does not last: the plugin only looks for its own line, so a later npx expo prebuild without --clean adds its line again next to yours.


CI

Every release command in your pipelines changes to dpctl. Install dpctl (on GitHub Actions, with the setup-dpctl action) and log in with an access key before the release step:

dpctl login --key "$DEPLOYPULSE_ACCESS_KEY"
BeforeAfter
appcenter codepush release-react -a MyOrg/MyApp-iOS -d Productiondpctl release-react MyApp-iOS ios -d Production
code-push release-react MyApp-iOS ios -d Productiondpctl release-react MyApp-iOS ios -d Production
code-push-standalone release-react MyApp-iOS ios -d Productiondpctl release-react MyApp-iOS ios -d Production
revopush release-react MyApp-iOS ios -d Productiondpctl release-react MyApp-iOS ios -d Production
eas update --channel production -m "Fix"dpctl release-expo MyApp -d production --description "Fix"

dpctl rejects flags it does not know, so a leftover flag fails the step instead of being ignored. Translate or remove each one.

From appcenter codepush release-react. The app and platform become positional arguments: drop the MyOrg/ owner prefix, and add ios or android after the app name. These flags carry over unchanged: -d, -t, -m, -x, -r, --description, -b, -e, -g, -p, -s, -o, --development and -k. These change:

App Center CLIdpctl
--plist-file-prefix--plistFilePrefix
--pod-file--podFile
--use-hermes--useHermes
--extra-hermes-flag--extraHermesFlags
--private-key-path--privateKey (--private-key-path is accepted too)
--disable-duplicate-release-error--noDuplicateReleaseError
-c, -xt, -xp, --sourcemap-output-dir, --extra-bundler-option, --disable-telemetry, --quiet, --output, --debug, --envNo equivalent: remove them. --sourcemapOutput takes a file path if you need a sourcemap
--tokenRemove it, and log in with dpctl login --key first

From code-push, code-push-standalone or revopush release-react. The command has the same shape and the same camelCase flags, so usually only the command name changes. Two exceptions:

  • -h means --useHermes in those CLIs but --help in dpctl. A step with -h prints the help, releases nothing and still succeeds. Write --useHermes instead.
  • --initial (-i), --extraBundlerOption (-eo), --force, --buildNumber (-bn), --xcodeProjectFile (-xp), --xcodeTargetName (-xt), --buildConfigurationName (-c) and the legacy --config have no dpctl equivalent: remove them.

From eas update. See CI: replace eas update with dpctl release-expo for the flag table and the --environment caveat.

Every deployment or channel a step releases to (-d) must exist on the app. Create missing ones with dpctl deployment add <app> <name>.

Translate by hand. Release commands from Bitrise's CodePush CLI, Appcircle, AppZung, Hot Updater and Stallion do not map flag for flag. Replace each with dpctl release-react <app> <platform> -d <deployment> for an app on the CodePush SDK, or dpctl release-expo <app> -d <channel> for an Expo Updates app. Apps and deployments lists every option, and the GitHub Actions, GitLab CI/CD, CircleCI, Bitrise and Jenkins guides show complete pipelines.


What's New in DeployPulse

DeployPulse includes capabilities App Center never offered:

  • Auto Rollback - automatically revert a release if the error rate exceeds a threshold, configurable per deployment
  • Code Signing - RS256 JWT signing so devices verify bundle integrity before applying an update
  • Differential packages - DeployPulse automatically computes a diff between releases and sends only changed files to devices, reducing update download sizes significantly

Further Reading