peach remote

Builds your app folder, or takes a prebuilt iOS or Android bundle, runs it on the production service and opens its viewer. The platform forms peach ios —remote and peach android —remote launch the same hosted path.

terminal
peach remote ios <app-dir|bundle.js|https://bundle-url> [--device <model>]
peach remote android <app-dir|bundle.js|https://bundle-url>
peach remote ios|android <metro-bundle-url> --watch
peach remote list [--json]
peach remote stop <sim-id>
peach remote close

Options

flagdescription
--device <model>pick a specific device model
--watchkeep a remote simulator connected to your Metro server until Ctrl+C

Examples

terminal
peach remote ios .
peach remote ios ./dist/main.js
peach remote android ./dist/main.js
peach remote list --json
peach remote stop <sim-id>
peach remote close

Run Your App

From your Expo or React Native app’s folder:

terminal
peach ios --remote .

Peach builds the app with the app’s own bundler, compiles its Expo modules, Nitro modules and C++ TurboModules on your Mac, and ships them with the bundle. Your Metro config needs no changes. Remote Android simulators do not load compiled Kotlin modules yet.

A prebuilt bundle also works. Build it with expo export:embed or react-native bundle through withPeach(config) from peachsim/metro, which records your installed package versions, then pass the file. Peach compiles the native modules of the app folder above the bundle, or of --native-project <app-dir>:

terminal
npx expo export:embed --platform ios --dev false --bundle-output dist/main.js --assets-dest dist
peach ios --remote ./dist/main.js