Dan Caseley

Does this only affect situations with mixed iOS and Android environments? Can you work around this with `maestro -p android test someFlow.yaml` and/or `maestro --device=emulator-5554 test someFlow.yaml`?

This is marked as an enhancement, but I'd consider it's borderline bug. It's reasonable to expect that copyTextFrom returns the text from the element selected, not some modified version of...

Came looking for this error. Ideally a few things would happen: * Log to the console * Fail the test and stop processing commands * Reduce the amount of noise...

@bartekpacia Reopen please

I've recreated this in a simple example. https://github.com/Fishbowler/maestro-examples/tree/env_vars/env-vars (I regret naming the folder and branch the same - sorry about that) Running `run.sh` gives: ``` Running on emulator-5554 ║ ║...

Locally, I'm working around this in v1.39.1 by passing them tiresomely at the CLI. e.g. For the OP's example, `maestro test -e MAESTRO_TEST_EMAIL=$MAESTRO_TEST_EMAIL myFolderOfFlows`

A quick conversation in Slack with Mário Raček set me onto a key difference: running an individual flow accurately captures variables from the environment. Running a folder does not. This...

This fix will be included in the next CLI release. Thanks to @nboxill for reporting, and to @mario-racek-devnautica for finding the important differences that led to the fix.

Without further reports, and without further information, I'm going to go ahead an close this. If anyone's still experiencing the problem, and the steps in here don't help, please open...

Thanks @NorseGaud! This looks really handy! Any chance of some tests for the new capabilities? You could certainly do an integration test, and perhaps some of the maths is unit...