appium: can't find a corresponding relation between adb version and appium version when do web test on chrome

The problem

Appium desktop 1.11.0 + Android 8.0.0 + fastboot_adb(1.0.39 or 1.0.40) + Chrome70.0.3538.80 and suitable chromedriver. there will be an error as below: Encountered internal error running command: Error: Error getting device platform version. Original error: Error executing adbExec. Original error: ‘Command ‘‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’ -P 5037 -s HQLDU18904000025 shell getprop ro.build.version.release’ exited with code 3221226356’; Stderr: ‘’; Code: ‘3221226356’

If I change fastboot_adb to version 1.0.36, above error will be disappeared, but there will be a new error: Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to forward ports to device HQLDU18904000025. No port chosen: . Perhaps your adb version is out of date. ChromeDriver 2.39 and newer require adb version 1.0.38 or newer.

Environment

  • Appium version (or git revision) that exhibits the issue:
  • Last Appium version that did not exhibit the issue (if applicable):
  • Desktop OS/version used to run Appium:
  • Node.js version (unless using Appium.app|exe):
  • Npm or Yarn package manager:
  • Mobile platform/version under test:
  • Real device or emulator/simulator:
  • Appium CLI or Appium.app|exe:

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

Create a GIST which is a paste of your full Appium logs, and link them here. Do NOT paste your full Appium logs here, as it will make this issue very long and hard to read! If you are reporting a bug, always include Appium logs!

Code To Reproduce Issue [ Good To Have ]

Please remember that with sample code it’s easier to reproduce the bug and it’s much faster to fix it.

Please git clone https://github.com/appium/appium and from the sample-code directory, use one of your favourite languages and sample apps to reproduce the issue.

In case a similar scenario is missing in sample-code, please submit a PR with one of the sample apps provided.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

Hi, I tried again on adb1.0.40 , and the result seems different with you told me. I can get android platform version by command “adb shell getprop ro.build.version.release” or “adb -P 5037 -s HQLDU18904000025 shell getprop ro.build.version.release”

but,when I use Appium to start a session, I still get the result: “Encountered internal error running command: Error: Error getting device platform version. Original error: Error executing adbExec. Original error: ‘Command ‘‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’ -P 5037 -s HQLDU18904000025 shell getprop ro.build.version.release’ exited with code 3221226356’; Stderr: ‘’; Code: ‘3221226356’”.

Isn’t it a Appium issue?

In additional, when I execute “adb shell getprop”, I can get: [audio.high.resolution.enable]: [true] [bastet.service.enable]: [true] [bg_fsck.pgid]: [344] [bt.dpbap.enable]: [1] [bt.max.hfpclient.connections]: [2] [build.hisi_perf_opt]: [true] …

Closed as not an issue