Migrate from CodePush
Microsoft retired App Center CodePush in 2025. Bundle Drop provides the same core OTA model for JavaScript and bundled assets, with channels, staged and targeted rollouts, managed publishing, patch delivery, and safe rollback.
How CodePush Concepts Map
- Deployment keys and deployments become channels. Apps check a named channel, and proven bundles can be promoted between channels.
codePush(App)andcodePush.sync()becomeBundleDrop.init,useBundleDrop, and update policies.- Install modes map to update policies.
- Mandatory release flags have no direct per-release equivalent. Application policy and UI own any required prompt or blocking flow; managed publishing controls server-side eligibility rather than forcing client installation.
- Target binary version gating maps to runtime compatibility: explicit platform versions by default, opt-in native fingerprints, or both.
- Differential updates map to Bundle Drop patch delivery with automatic full-bundle fallback.
- Rollback maps to dashboard rollback and on-device crash protection.
Run the Guided Migration
This bare React Native walkthrough starts after package installation and project connection. It separates the references you remove manually from the native migration changes you review and approve.
Review your migration. Keep your app structure.
CLI walkthrough- Inspect
- Clean up
- Migrate
- Rebuild
Next, add BundleDrop.init, refresh iOS pods, and test and distribute a rebuilt native app before sending OTA updates.
Install Bundle Drop and start setup from the project root. Keep the CodePush dependency installed so setup can detect and migrate it:
yarn add @gfean/react-native-bundle-drop
npx bundle-drop loginOn first-time configuration, login enters AI-assisted setup. It asks permission to send project context for analysis, detects the existing CodePush integration, and previews the proposed migration. It asks for migration consent and approval before applying changes. In a bare project, the reviewed native edits update Android and iOS bundle-resolution paths while preserving the app's current ReactHost, ReactNativeHost, or AppDelegate structure. Expo projects use the config plugin path described in Expo.
If the project already has Bundle Drop configuration, login does not rerun AI setup. Start or repeat the bare React Native migration explicitly:
npx bundle-drop init --project-type bare --migrate-code-pushThere is no separate native initialization command.
Clear CodePush References Before Applying
For bare React Native migration, setup stops before applying changes if CodePush references remain outside the native entrypoints it patches. Remove the reported references manually:
- Remove CodePush JavaScript imports, the
codePush(App)wrapper, andcodePush.sync()calls. - Remove
CodePushDeploymentKeyfrom iOSInfo.plistand Androidstrings.xml. - Remove the
codepush.gradleapply line from Android Gradle configuration. - Remove other reported custom native CodePush references. Leave the existing MainApplication and AppDelegate bundle-resolution seams for the reviewed AI migration.
Rerun the migration command, review the proposed file diffs, and approve the setup changes. The CLI removes react-native-code-push using your project's package manager, applies the reviewed native and project configuration changes, and runs doctor. You do not need to remove that dependency separately.
Add your application's BundleDrop.init call; the native migration does not rewrite your JavaScript startup code. Then refresh iOS pods and verify the project:
cd ios && pod install && cd ..
npx bundle-drop doctorChoose the compatibility strategy before building the migrated app. Fingerprint mode is Beta and opt-in; it does not let an existing CodePush binary acquire Bundle Drop's native integration through an OTA. Test and distribute the rebuilt binary before publishing updates for its compatibility line.
Move Release Tracks to Channels
Recreate CodePush deployment tracks as Bundle Drop channels. A common mapping is:
- CodePush Staging →
developorbeta - CodePush Production →
production
Initialize the SDK with the intended channel, then publish the first compatible Bundle Drop update. Do not reuse CodePush deployment keys; Bundle Drop project configuration and channel names replace them.
After Migrating
- Configure startup behavior with BundleDrop.init.
- Publish with Uploading.
- Control eligibility with Managed Publishing.
- Release gradually with Staged Rollouts.
- Review compatibility rules in Runtime Version.