Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

supportedLogTypes does not get assigned properly on driver init since beta27

See original GitHub issue

The problem

After base driver update to 8.4.0 getLogTypes and getLog commands of appium-android-driver stopped working properly because this.supportedLogTypes property does not get initialized. I assume this is related to the recent typing refactoring in base-driver/lib/basedriver/commands/log.js. Previously this variable has been assigned by defining extensions.supportedLogTypes, which was equal to {} by default and is overridden in each driver if necessary. Now it always equals to {}. See https://dev.azure.com/AppiumCI/Appium CI/_build/results?buildId=20705&view=logs&j=12e12a94-6f82-50bd-49c9-566fb2052675&t=7ba1c276-5935-513a-f217-d07020732771 for more details.

Environment

Appium version (or git revision) that exhibits the issue: base-driver 8.3.0
Last Appium version that did not exhibit the issue (if applicable): base-driver 8.4.0
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: