Discover ADB executable in AdbBinaryInteractor #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes
adb
executable may be installed as a standalone binary, not as part of ANDROID SDK. For example, in debian/ubuntu based containers withandroid-tools-adb
package. We can discover it withwhere
command (read on SO thatwhich
should work on Windows, but I'm unable to test it).I'm not sure if this a suitable addition since
AdbBinaryInteractor
already has parameter for specifying path to adb. As a compromise functiondiscoverAdbBinary
can be refactor intoDiscoverAdbBinary
interactor.