Closed ggallo closed 2 years ago
That shouldn't happen. Can you try this branch and see if the issue is fixed: https://github.com/JeffLIrion/adb_shell/tree/streaming-shell-fix
You can install that branch via:
pip install https://github.com/JeffLIrion/adb_shell/archive/streaming-shell-fix.zip
You can install that branch via:
pip install https://github.com/JeffLIrion/adb_shell/archive/streaming-shell-fix.zip
@ggallo any feedback on whether this fixes the issue?
@JeffLIrion I haven't forgotten about this! Sadly I am blocked by what appears to be a similar issue over at #152 (see comment there)
@ggallo this pull request should fix the issue: https://github.com/JeffLIrion/adb_shell/pull/172
I think it will fix #152, too.
You can install that branch via
pip install https://github.com/JeffLIrion/adb_shell/archive/support-multiple-streams.zip
This should be fixed in the latest release (0.4.0).
pip install -U adb-shell
I have a routine looking for events. I'm mapping user input on the screen to a series of well-defined actions ("swipe left", etc.). I want a
streaming_shell()
for each gesture so I can delineate between them.It goes through the first gesture just fine, but on the second gesture it errors at the
next()
. Here is the output:I can open two non-streaming shells in a row and run commands without incident. Of course this won't work for my use case, because I'm waiting on input, but it's just to show that
shell()
doesn't have the same problem.Is this intended behavior? Are we meant to close the entire TCP cxn and retry for each streaming shell? (This isn't asked to be snarky, I haven't done much serious shell-adjacent programming in some time and am very rusty.)