tapOn occasionally taps twice?

[abbbe]

Figured I ask here before filing a bug report, in case it is a known behavior (and it will be very tricky to create a simple reproducible test case).

So, on the very first screen of my app I have signInAnonButton button, which opens second screen, which has more buttons.
I do tapOn signInAnonButton on the first screen and it works perfectly, bringing me to the second screen, where I press settingsButton button later on. Here is the code

- launchApp:
    clearState: true
    arguments:
      mockBleManager: true

# anon login & go to calibration screen
- tapOn:
    id: "signInAnonButton"
- tapOn:
    id: "settingsButton"

And a screen recording of normal behavior: https://github.com/user-attachments/assets/c50888ff-01da-40ff-b446-1b73ab03776c

But occasionally, it looks like that tapOn also hits two buttons in succession, once the button on the first screen as it should and another button on the second screen which was never meant to be tapped. Here is the recording of the same script running agains the same app build, on the same simulator:

not-ok.mov

I figure the issue could be introducing some kind of a delay, but his is ugly. Any clues are appreciated...

[simon-gilmurray]

@abbbe this unfortunately is a known issue on Android - You can solve this by using retryTapIfNoChange: false on your initial tap and any other problematic tap:

https://docs.maestro.dev/troubleshooting/known-issues#accidental-double-tap

[abbbe]

Thank you. It has solved my problem.

Sometimes, tapOn will try to tap again if it doesn't detect a hierarchy change
I have a feeling this problem happens when the screen gets changed too fast in a response to the first click.

[Fishbowler]

This is now the default.