You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the release of the 1.26.0 version, our tests started failing because tapping on a button right after hiding the keyboard caused it to not get actually tapped on. I think that the solution is that the hideKeyboard command should block the test run until the keyboard has finished the blocking of tapping other things on the screen.
Ohhh can you share the reproducing steps with some sample apps? Or if you can share the binary and flow for this? Feel free to share over DM on our Slack community: https://docsend.com/view/3r2sf8fvvcjxvbtk
Problem:
After the release of the 1.26.0 version, our tests started failing because tapping on a button right after hiding the keyboard caused it to not get actually tapped on. I think that the solution is that the
hideKeyboard
command should block the test run until the keyboard has finished the blocking of tapping other things on the screen.Environment:
Example code:
Versions:
Example recording:
example.mp4
The text was updated successfully, but these errors were encountered: