Dan Caseley
Dan Caseley
@arapocket Could be, it's not one I've looked into. In the meantime, some workaround ideas: - add a `waitForAnimationToEnd` before `hideKeyboard` - tap something non-interactive instead of using `hideKeyboard`, like...
Looks like it's missing from Web's driver implementation right now... https://github.com/mobile-dev-inc/Maestro/blob/a54ab46fc061540276ac87b0adce79e8bb685f53/maestro-client/src/main/java/maestro/drivers/CdpWebDriver.kt#L307
What's the timeout here? Is it that the OS couldn't process the open link instruction because the Expo app wasn't fully metro'd up yet?
Would love a way to reproduce this
@d4rky-pl Any thoughts on how we'd reproduce this / test if we'd fixed it?
I suspect that running a Simulator and a JVM and doing some e2e tests between them might simply be unstable or impossible in a resource starved environment...
So most of this shouldn't be necessary. The correct invocation, that you haven't listed, is just `maestro test someFile.yaml`. I wouldn't expect that to fix things though. I wonder if...
Looks like we're getting closer to the real problem. It's not just about device _detection_.
Was that after a long wait (~60s), or pretty quickly?
Try running your SDK Tools from Android Studio and check that the tools are up to date. This command uses the $ANDROID_HOME emulator binary.