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.
Appium don't use older chromeDriver version
See original GitHub issueThe problem
I wrote chromeDriver mappings json file to automatically select older driver for older android devices to use chromedriverExecutableDir capability. But Appium uses newest on the list. If newest version in the list is 2.35 it uses this version. If I used fixed chromedriver version 2.28 by
appium --chromedriver-executable /path/to/my/chromedriver it works fine for Android 5.1 device.
As I understand Appium 1.8.0 should dynamically select suitable chromeDriver for each Android device. I use multiple devices from Android 5.1 to 8.0.
Environment
- Appium version (or git revision) that exhibits the issue: 1.8.0
- Last Appium version that did not exhibit the issue (if applicable):
- Desktop OS/version used to run Appium: Win 10 64 bit
- Node.js version (unless using Appium.app|exe):
- Mobile platform/version under test: Android 5.1
- Real device or emulator/simulator: Motorola Moto G
- Appium CLI or Appium.app|exe:
Details
Link to Appium logs
https://gist.github.com/Dento55/e777cb056e67ff480fa4e765233e9627
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No, that’s not valid semver. https://github.com/appium/appium-chromedriver/pull/79 will fix the issue on our side by coercing it.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.