You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After our app has been updated to use V0.12 our selenium tests no longer work, the following is seen when the selenium server attempts to start a session:
Caused by: org.openqa.selenium.WebDriverException: unknown error: cannot find Chrome binary
I have a workaround of renaming /node-webkit.app/Contents/MacOS/nwjs to /node-webkit.app/Contents/MacOS/node-webkit but I don't know what other side affects this could have?
I believe I have traced back the code to chrome/test/chromedriver/chrome/chrome_finder.cc in the chromium.src
After our app has been updated to use V0.12 our selenium tests no longer work, the following is seen when the selenium server attempts to start a session:
Caused by: org.openqa.selenium.WebDriverException: unknown error: cannot find Chrome binary
I have a workaround of renaming /node-webkit.app/Contents/MacOS/nwjs to /node-webkit.app/Contents/MacOS/node-webkit but I don't know what other side affects this could have?
I believe I have traced back the code to chrome/test/chromedriver/chrome/chrome_finder.cc in the chromium.src
Also created #37 against nwjs/chromium.src?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: