run builds (unless skipped) and launches your app on the selected target. After flowdeck config set, you can run without extra flags.
Options
If both
--simulator and --device are omitted, FlowDeck uses the saved target from flowdeck config set or interactive mode.--config here means the explicit command config file format. It is separate from .flowdeck/config.json and .flowdeck/config.local.json.Simulator launches open Simulator.app by default using the Simulator bundle from the selected Xcode developer directory. If that selected Xcode does not contain Simulator.app, FlowDeck opens an installed Xcode bundle that does. Pass
--headless to boot and run the simulator without opening Simulator.app (for example, when another surface renders it). --headless is ignored for macOS, Mac Catalyst, and physical-device targets.Pure Swift Package directories are routed through Xcode’s generated
.swiftpm/xcode/package.xcworkspace, matching Xcode’s build path. Package library schemes may still fail at launch time if xcodebuild does not produce an app bundle.For physical device runs,
flowdeck apps, flowdeck logs, and flowdeck stop continue to work as long as the app is running on the device.JSON Output
When--json is set, run emits NDJSON events (one JSON object per line). Example:
Compiler errors are always emitted in JSON failure events. Warning diagnostics are opt-in and emitted when
--show-warnings is set. Warning snapshots are still reconciled and stored under DerivedData (<DerivedData>/Warnings) when a build step runs.