[BUG] startRecording, takeScreenshot commands not working

[nikhilbhandari]

Description

my YAML file contains the startRecording, stopRecording, takeScreenshot commands. When I run it with Maestro it gets executed, but when used with Maestro-runner, it doesn't record or capture the screen-shot.

Steps to Reproduce

1. Run command '...'
2. With flow file '...'
3. See error

Expected Behavior

What you expected to happen.

Actual Behavior

What actually happened.

Environment

• OS: macOS 26.3 (25D125)
• maestro-runner version: 1.0.8
• Executor: Native
• Device/Simulator: Pixel 8 Emulator

Flow File

appId: com.xx.yy.dev
name: Checkout flow
tags:

• Smoke
• TC-001
• High

---

• launchApp:
  clearState: true
• startRecording: "/Users/xxx/Documents/Projects/test-framework/mobile-test-automation/output/recordings/recording"
• extendedWaitUntil:
  visible: "Pair Register"
  timeout: 20000 # Wait
• takeScreenshot: /Users/xxxDocuments/Projects/test-framework/mobile-test-automation/output/screenshots/01-pair-register-screen.png
• tapOn: Pair Register
• tapOn: 0000 - 0000 - 0000 - 0000

Relevant flow file (anonymized if needed)

## Error Output

No error observed

## Additional Context

Add any other context about the problem here.

[omnarayan]

Hi @nikhilbhandari — startRecording is not yet supported in maestro-runner.

The docs incorrectly claim it is — that's a bug on our end and we'll fix it.

We're actively building out the core and adding features. Recording is on the roadmap.

In the meantime, takeScreenshot is fully supported:
https://devicelab.dev/open-source/maestro-runner/docs/flow-commands#takescreenshot

Screenshots are automatically attached to steps in the HTML report and save

  <output-dir>/
  ├── assets/
  │   ├── flow-000/
  │   │   ├── cmd-000-my-screenshot.png
  │   │   ├── cmd-001-screenshot.png
  │   │   └── ...
  │   ├── flow-001/
  │   │   └── ...
  ├── report.html
  ├── report.json
  ├── junit-report.xml
  └── allure-results/

[nikhilbhandari]

Thank you for the update. Can we add the feature to override the relative path if absolute path for screenshots is mentioned. Currently Maestro supports it.

[omnarayan]

@nikhilbhandari — not promising a fix , it's referenced in multiple places so we need to look into it properly.

On your actual need — if I understand correctly, you want to know where screenshots are stored and how they relate to steps. We've created a report.json for exactly this — it gives you the step-screenshot relationship programmatically, so you can build a custom report or query it however you need.

Not a perfect solution, I know , but the idea was to give the right structure and flexibility so you can mold it to your requirements.