-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buildpack installs chromium-chromedriver when it shouldn't #94
Comments
I'm having the same issue. My Heroku CI pipeline broke as a result of this problem. The failure I'm seeing is this:
My app.json file looks like this:
But I've also tried removing the chromedriver buildpack and that fails with the following message:
|
Clearing my build cache fixed this issue for me. Instructions here. |
These build packs are a production nightmare. No combination of environment variables will have you a working chrome + chrome driver configuration that won't break the moment a chrome version moves between channels. |
My horrible scraping solution broke today because chrome driver got out of sync with chrome. I use
heroku-buildpack-chromedriver
which is run afterheroku-buildpack-google-chrome
During investigation, it turns out that there are two chromedrivers installed - one in
~/.apt
and another in~/.chromedriver
Looks like
heroku-buildpack-google-chrome
is dragging inchromium-chromedriver
somehow:According to the README this build pack shouldn't be doing that
The text was updated successfully, but these errors were encountered: