Dan Caseley
Dan Caseley
On my Linux environment, it wasn't Maestro related at all. The emulator was terminating even if I left it alone.
Were you able to find a set of emulator options that worked for this configuration?
There's some fairly out-of-the-ordinary usage in your example. Could I simplify this down to something like: flow.yaml ``` appId: com.example tags: - do_not_run --- - launchApp ``` Command: ``` maestro...
Right now, the inverse (using includes) works: ``` maestro test --include-tags non-existent . ``` You'll get some red output ``` Include / Exclude tags did not match any Flows: Include...
I'm considering that this could be a risk to Maestro Cloud infrastructure. I'm wondering how we can limit that risk. Got thoughts?
Would users respond well to a thing that works locally but doesn't work in the Cloud execution environment though?
Would love your take on this @Leland-Takamine
I'm not sure we're going to be able to merge this PR in its current state. I had concerns about security that aren't entirely mitigated by the flag, since anyone...
I'd expect that in the current implementation for the second step to never start. The script would never complete. Without changes, this can't be merged. My comments above need addressing....