Maestro CLI · CLI
Maestro CLI 2.8.0
2.7.0→2.8.0·
Minor release: element-relative swipe points, safer artifact paths, report/Cloud linking improvements, and Android/iOS device reliability fixes.
- [new]
swipe supports an element-relative point so you can start a swipe from a position within a matched element
- [new] JUnit and HTML reports link back to Maestro Cloud via per-flow
cloud.runId / cloud.runUrl and suite-level cloud.uploadId / cloud.url
- [new]
setPermissions values accept variables
- [new]
assertScreenshot threshold accepts variables
- [fix]
takeScreenshot / startRecording no longer fail with "No such file or directory" when the path contains ..
- [fix]
takeScreenshot / startRecording fail clearly when the path names a directory, instead of writing a hidden ..png
- [fix] Artifact paths that escape the command’s output folder are rejected when bundling debug output
- [fix]
childOf selectors no longer match against a stale view hierarchy
- [fix] Run artifacts are kept when an
onFlowComplete hook fails
- [changed] Local runs record start times in JUnit and HTML reports; HTML shows human-readable start times
- [changed] JUnit
timestamp values are truncated to whole seconds so strict CI importers accept them
- [changed] Suite duration accuracy improved in JUnit and HTML reports
- [changed] Console output reports durations consistently
- [fix] Cloud uploads whose outcome is unknown are not retried
- [fix]
maestro cloud shows the correct “similar device” hint
Platforms
- [fix] Android: locale is applied to the correct emulator after
start-device (not a pre-existing device)
- [fix] Android: locale setup no longer blocks on the locale broadcast
- [fix] Android: emulator boot failure no longer blocks forever
- [fix] iOS: listing devices no longer fails when
devicectl is unavailable
Under the hood
- Hardened path handling for screenshots, recordings, and debug-output bundling
- More reliable report timing and Cloud upload behavior
- Contributor thanks to @PankovSerge