[BUG] waitForAnimationToEnd always shows 0ms

[chrisjin-swipe]

Description

waitForAnimationToEnd always shows 0ms
✓ waitForAnimationToEnd (0ms)

From the official docs this should work with a timeout flag ie.

  - waitForAnimationToEnd:
      timeout: 5000 # Wait up to 5s for movement to stop

Which should wait 5s for the UI to settle.

Use case:

• After submitting a form, there is a loading content UI which takes a couple seconds to settle. I have tried adding waitToSettleTimeoutMs on taps, and also extended wait on the loading UI, however these seem to hang for 17s even after the loading message has disappeared (on Android)

Steps to Reproduce

1. Run command 'waitForAnimationToEnd'

Expected Behavior

Waits 5s for the UI to settle

Actual Behavior

0ms wait

Environment

• maestro-runner version: latest-version
• Executor: UIAutomator2
• Device/Simulator: Android Medium_Phone_API_36.1

[omnarayan]

Fixed on main in b26fd2c. Thanks @chrisjin-swipe for the clear repro
— the 0ms screenshot pointed straight at the issue.

The step was a stub on UIA2 / DeviceLab / WDA — it returned success
immediately, and the timeout: field was parsed but discarded. That's
why you were seeing waitForAnimationToEnd (0ms).

It now actually polls: takes two consecutive screenshots, decodes
both, and considers the screen "static" when ≤ 0.5% of pixels differ
(matches the upstream Maestro algorithm). Default timeout is 15s if
unset; your timeout: 5000 is now honoured on all four drivers
(Android UIA2 / DeviceLab, iOS WDA, web CDP). On timeout the step
soft-returns success — it never blocks the flow even if an animation
genuinely never settles.