Hi team — I’m seeing a syntax mismatch for setAirplaneMode between standard Maestro flow usage and what maestro-runner appears to accept.
What I expected
A flow using standard Maestro command syntax should parse in maestro-runner.
What I see
maestro-runner parsing fails with:
Validation errors:
- .maestro/flows/ideas/03-venue-error-handling.yaml: parse error: .maestro/flows/ideas/03-venue-error-handling.yaml:10: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `enabled` into flow.SetAirplaneModeStep
Error: validation failed with 1 error(s)
(raised at the next command after setAirplaneMode in the flow)
Repro
Flow snippet:
appId: com.abc.app
---
- setAirplaneMode: enabled
- tapOn: "Find Venues"
Actual behavior
Parser fails and reports invalid input for enabled.
Expected behavior
- Accept documented/common Maestro syntax for
setAirplaneMode
Environment
- macOS (Darwin 24.6.0)
- Project uses Maestro YAML flows under
.maestro/
- Command used:
maestro-runner --output .maestro/reports --flatten --auto-start-emulator .maestro/
Hi team — I’m seeing a syntax mismatch for
setAirplaneModebetween standard Maestro flow usage and whatmaestro-runnerappears to accept.What I expected
A flow using standard Maestro command syntax should parse in
maestro-runner.What I see
maestro-runnerparsing fails with:(raised at the next command after
setAirplaneModein the flow)Repro
Flow snippet:
Actual behavior
Parser fails and reports invalid input for
enabled.Expected behavior
setAirplaneModeEnvironment
.maestro/maestro-runner --output .maestro/reports --flatten --auto-start-emulator .maestro/