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.
need to document env var approach to driver install params in 2.0 migration guide
See original GitHub issueIs the chromedriver part of the uiautomator2 driver ?
In the past it was possible to add the --chromedriver-skip-install flag to the npm installation.
This is currently also possible when i install appium with
npm install appium@next --chromedriver-skip-install --drivers=uiautomator2
But its not possible if i want to install via
appium driver install uiautomator2
Would it be possible to add the flag there also ?
_Originally posted by @StephanB75 in https://github.com/appium/appium/discussions/15812#discussioncomment-1299645_
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 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
I think it’s a different issue.
--chromedriver-skip-installis not a driver CLI arg, it gets wrapped up intoprocess.envautomatically by NPM (NPM has special support for using custom flags duringnpm install).I think the unfortunate reality here is that we won’t be able to support these flags, since we are abstracting away from NPM. I think we’ll need to rely on and document an environment-variable based approach (which in this case is already supported, as @KazuCocoa mentioned in #15812).
yes the environment variable “APPIUM_SKIP_CHROMEDRIVER_INSTALL=true” works for both perfectly. Thank you for the tip !