flowdeck config set, you can call flowdeck build with no 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.On failed builds, FlowDeck prints the extracted failure reason plus the absolute persisted build log path. Read that log before rerunning with
--verbose.JSON Output
When--json is set, build 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 always reconciled and stored under DerivedData (<DerivedData>/Warnings) on every build.build_errors event lists each error and warning. Items include an optional language token (swift, cpp, objc, objcpp, c, or metal) so you can tell which compiler produced each diagnostic. The field is omitted when the language can’t be determined — issues with no source file (linker, code signing) or ambiguous files (such as .h headers). A grouped multi-target compile error has no single file but is still tagged when all of its diagnostics share one language, so language can appear without a file. Consumers should ignore unknown future values.
✗ [Swift] cannot find type 'Foo').