1255661 - Cannot run logcat: adb server deemed out-of-date & killed

Status: RESOLVED WORKSFORME

(Firefox Build System :: Android Studio and Gradle Integration, defect)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

afaik, I have three SDKs currently:
* /usr/local/opt/android-sdk (installed via brew)
* ~/.mozbuild (from mozilla)
* ~/.android-sdk (from latest sdk-manager-plugin changes)

I have /usr/local/bin in my path and typically run Android binaries from there. However, with a recent pull of fx-team, when trying to run `mach build <robocop-stuff> && mach robocop <test>` in one terminal and `adb logcat` in another, I get a message in the logcat shell that the adb server is out-of-date and that it will kill it.

I tried running `adb logcat` from all three locations concurrently with my mach commands and it did not fix the issue. I don't have the ANDROID_HOME envvar set.

Nick, thoughts?

Comment 1

[Nick Alexander :nalexander [he/him]]

> Nick, thoughts?

Not really.  I saw another contributor with the same symptoms in #mobile, but haven't a clue what he did to get unstuck.

A quick search on the web suggests this is a *device* incompatibility -- namely, that the device itself has an incompatible version of the ADB server installed.  This might be triggered by using more modern tools on your build host?  But I am not aware of anything that's really changed here.  Did you upgrade Android tooling, like fetching the Android N preview?

Comment 2

[Nick Alexander :nalexander [he/him]]

(In reply to Michael Comella (:mcomella) from comment #0)
> afaik, I have three SDKs currently:
> * /usr/local/opt/android-sdk (installed via brew)
> * ~/.mozbuild (from mozilla)
> * ~/.android-sdk (from latest sdk-manager-plugin changes)

Oh hai.  Did the sdk-manager-plugin download this?  It shouldn't have.

Comment 3

[Geoff Brown [:gbrown]]

fwiw, I would expect 'mach robocop' to use http://hg.mozilla.org/mozilla-central/annotate/f0c0480732d3/testing/mozbase/mozrunner/mozrunner/devices/android_device.py#l583 to find adb. In my experience, it is usually substs["ADB"] that finds it and it is usually in .mozbuild.

Comment 4

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Nick Alexander :nalexander from comment #2)
> > * ~/.android-sdk (from latest sdk-manager-plugin changes)
> 
> Oh hai.  Did the sdk-manager-plugin download this?  It shouldn't have.

I assume so – the modification date is 3/10 and I didn't put anything there intentionally.

Comment 5

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Got a more specific error output, adb is coming from my /usr/local/opt installation:
  adb server version (32) doesn't match this client (35); killing...

Come to think of it, I had updated the android-sdk in homebrew, which deleted my platform-tools installs and the only available platform tools (at the time) were the preview versions (for Android N). I appear to have fixed this by installing the stable platform tools (now available) and uninstalling the preview platform tools.

Thanks for your help, everybody!