ArnauBuild

**FLOW:** # ----- Launch App and perform setup ----- ``` - launchApp: clearState: true - assertVisible: "Setup XXX" - tapOn: "Setup XXX" - assertVisible: "XXX YYYYYY." - killApp: appId: ${app_id}...

I saw this logs on the logcat, while executing locally, but without a GUI (when opening the app for the second time): 16:39:03.414 2386 2409 W UiDevice: Cannot verify accessibility...

No, locally works as expected. It's just when it's executed on a CI environment, in which there are emulators without GUI. With iOS works fine

I tried it several times to run it on a headless emulator locally. It always worked expect one time, in which it didn't. In a CI environment, it has never...

I reproduced this issue locally, and I got the logcat. Analizing it, what appears to be happening is that: - After the second launch app, the app launches successfully, however,...

It not only happens with the adb install, I have other adb commands that I need to make, such as adb pull/adb push/... that also fail

I have tried to place this code, before and after the adb calls: - runScript: file: ../terminal.js env: exec: 'sleep 2' async: false label: "Wait for 2 seconds" In a...

As a summary of what's this issue about: **Summary** After executing adb install commands within a Maestro test flow, the accessibility service loses its ability to inspect the UI hierarchy,...

ADB commands are definitely working — I can see them completing successfully in the logs. The next command (launchApp) also runs fine, but after that Maestro is no longer able...

Yes, it was already running. I even tried to place an adb command just before executing the maestro test command, and still fails.