Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix: Expect ShellCommandResult from executing ShellCommandRequest #74

Merged
merged 1 commit into from
Feb 8, 2022
Merged

Fix: Expect ShellCommandResult from executing ShellCommandRequest #74

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/_tutorials/1-shell.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ val device = devices.firstOrNull { it.state == DeviceState.DEVICE } ?: throw Run
Now we have a device and can execute a request for it:

```kotlin
val response: String = adb.execute(ShellCommandRequest("echo hello"), device.serial)
val response: ShellCommandResult = adb.execute(ShellCommandRequest("echo hello"), device.serial)
```

All the waiting for response and establishing a transport connection happens transparently, you don't need to wait for anything. This also
doesn't allocate new threads.
doesn't allocate new threads.