Simulate Test
Since hot-updater does not work in dev environment, you need to test it in Release mode as shown below.
Checklist
- Make sure
hot-updater.config.tsis properly configured. - Make sure
HotUpdater.wrapis properly implemented.
Step 1: Simulator Release Mode
Run your app in Release mode to test hot-updater (it doesn't work in dev mode).
iOS:
cd ios && pod install && cd ..
npx react-native run-ios --mode ReleaseAndroid:
npx react-native run-android --mode ReleaseiOS:
npx rock run:ios --configuration ReleaseAndroid:
npx rock run:android --variant ReleaseiOS:
npx expo run:ios --configuration ReleaseAndroid:
npx expo run:android --variant releaseStep 2: Deploy
Deploy with interactive mode and force update flag enabled in hot-updater deploy mode.
When HotUpdater.wrap is set up, updates will be applied when you restart the app.
You can check the update progress status using useHotUpdaterStore.
For Normal Deployment
This is the standard deployment mode. After an update is created, users need to restart their app after downloading the bundle for the update to take effect.
npx hot-updater deploy -iFor Emergency Deployment
This is the emergency deployment mode. After an update is created, the bundle will automatically reload and apply the update as soon as users download it.
npx hot-updater deploy -i --force-updateStep 3: Rollback
When you set a bundle's enabled status to false in the console, users who have that bundle will immediately force update to the previous bundle.
Open the console and set the bundle's enabled status to false.
npx hot-updater consoleConsole (Rollback & Force Update)
Opens a localhost server based on plugins configured in `hot-updater.config.ts`. For security reasons, only localhost server is supported at the moment.
Channels
Channels let you manage updates across different environments (development, staging, production) and target specific user groups or separate applications.