Closed askucins closed 1 year ago
One workaround that comes to my mind is to repack v115 to not contain the additional directory, upload it to a location accessible by the build and then use a custom driver urls configuration json file pointing at the custom location with repacked zip for v115.
Fixed in #40.
It works now like a charm! Thanks a lot!
Recently I've updated the version of ChromeDriver in my tests to 115.0.5790.102 which, as suggested on https://chromedriver.chromium.org/downloads required also slightly different urls - that part went just fine - com.github.erdi.webdriver-binaries in version 3.1 picked that new chromedriver and unzipped it.
But here the problems starts - in the logs of my tests there is this:
and indeed, there is an extra folder in that zip file (so the same exists after it's extracted), like:
Please compare the content of v114 vs v115
v114
v115
Is there maybe any quick fix I can do to this on my side? (I mean of course manually copying that chromedriver to the parent folder worked just fine, but I mean something less manual so to speak :)