peach ios

Start a simulator on iOS. The platform picks the device: your current device is kept when it is already an iOS model, otherwise the default iOS device is used. Use —remote with your app folder, or a prebuilt bundle, to run it on the production service and open its viewer.

terminal
peach ios [target] [--device <model>]
peach ios --remote <app-dir|bundle-path|https-url> [--device <model>]
peach ios --remote <metro-bundle-url> --watch

Options

flagdescription
--streamstream this local simulator to your team until Ctrl+C
--watchkeep a remote simulator connected to your Metro server until Ctrl+C
--device <model>pick a specific iOS device model. an Android model here is refused by name rather than silently overriding the platform
--remotebuild the app folder, or take the bundle, and run it on a remote simulator with its viewer open

Examples

terminal
peach ios
peach ios --device iphone-16
peach ios --remote .
peach ios --remote ./dist/main.js
peach ios --remote https://cdn.example.com/main.js

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