Replace AppCenter CodePush with BytePush

This guide walks you through setting up CodePush with a custom server for your React Native application.

Prerequisites

• React Native project
• Basic understanding of iOS and Android development

Installation Steps

1. Base CodePush Setup

Note: If you have already installed the CodePush plugin, you can skip this step.

First, install and configure the CodePush plugin for your React Native project following the official documentation.

2. Configure Custom Server URL

Android Configuration

1. Navigate to your strings.xml file:

   android/app/src/main/res/values/strings.xml

2. Add the following line inside the <resources> tag:

   <string moduleConfig="true" name="CodePushServerUrl">https://bytepush.app</string>

iOS Configuration

1. Open your Info.plist file in Xcode or a text editor
2. Add the following entry:

   <key>CodePushServerURL</key>
   <string>https://bytepush.app</string>

3. React Native Checking for updates

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

...

 CodePush.sync({
        updateDialog: true,
        installMode: CodePush.InstallMode.ON_NEXT_RESTART,
        deploymentKey: Platform.OS === 'ios' ? DeploymentKey_ios : DeploymentKey_android,
      })

...

4. CLI Setup and Usage

1. Install the CodePush CLI globally:

   npm install code-push-cli@latest -g

2. Log in to your custom server:

   code-push login http://bytepush.app

3. Register your applications:

   # For iOS
   code-push app add YOUR_APP_NAME_ios ios react-native Production
   
   # For Android
   code-push app add YOUR_APP_NAME_android android react-native

5. Deploying Updates

To deploy over-the-air (OTA) updates to your applications:

# For iOS
code-push release-react YOUR_APP_NAME_ios ios -d Production

# For Android
code-push release-react YOUR_APP_NAME_android android -d Production

Common Issues and Troubleshooting

• If you encounter connection issues, verify that your custom server URL and deployment key is correctly configured in both platform-specific files
• Ensure your CLI is logged in to the correct server before attempting deployments
• Double-check app names match exactly when deploying updates