What happened
agent-device 0.21.1, Android emulator, record start <path> --quality high, an action, then 6 to 11 s of waiting, then record stop. Across three runs and about ten clips, every clip ends roughly one second after the last input event: clips of 2.1 s, 2.7 s and 3.8 s for windows of 8 to 11 s. No error is reported. A result that appears on screen more than a second after the last tap (a toast, a list re-render after a network round trip) is not in the clip. iOS recordings in the same runs ran to record stop.
Proposal
Keep capturing until record stop, or, if the capture is intentionally bounded by input activity, say so in the record stop output with the captured duration so the caller can re-record.
What happened
agent-device 0.21.1, Android emulator,
record start <path> --quality high, an action, then 6 to 11 s of waiting, thenrecord stop. Across three runs and about ten clips, every clip ends roughly one second after the last input event: clips of 2.1 s, 2.7 s and 3.8 s for windows of 8 to 11 s. No error is reported. A result that appears on screen more than a second after the last tap (a toast, a list re-render after a network round trip) is not in the clip. iOS recordings in the same runs ran torecord stop.Proposal
Keep capturing until
record stop, or, if the capture is intentionally bounded by input activity, say so in therecord stopoutput with the captured duration so the caller can re-record.