Chris Lanoue
Add first-class support in EAS prepackaged Maestro workflows to export and retrieve test artifacts (screenshots, screen recordings, snapshots, JUnit/XML reports, logs) as downloadable artifacts or job outputs. This allows teams to integrate their own visual diff/regression systems (e.g., Percy, in-house tooling) without abandoning the convenience of the prepackaged workflow.
Problem / Current Limitation
When using the prepackaged type: maestro workflow:
  • Test artifacts generated by the Maestro CLI (failure screenshots, optional full-run screenshots, possible screen recordings, junit XML) are not exposed outside the job.
  • There is no documented output (e.g., artifact URLs or local path outputs) that downstream steps or external systems (Percy, custom diff pipelines) can consume.
  • To retrieve artifacts today, teams must:
- Re-implement a custom workflow (losing the simplicity of prepackaged workflows)
- Manually replicate internal logic (emulator provisioning, build download, Maestro CLI install, environment prep)
- Maintain fragile scripts whenever EAS internals evolve.
Concrete use case: Our team wants to diff UI screenshots over time using our own screenshot comparison pipeline. We can produce screenshots under a known directory (e.g. .maestro/tests/), but the EAS hosted workflow gives us no mechanism to export or download them automatically.