I have been using Cucumber all day and even though I did not change any files, it just stopped working.
It gives me an error that reads:
Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome (Selenium::WebDriver::Error::UnknownError)
Any idea, what is going on?
Here is a simple step-by-step that should get everything working again on OS X:
Download the latest prebuilt chromedriver server for OS X here: http://code.google.com/p/chromedriver/downloads/list
Move the chromedriver executable to your PATH. If you saved (and unzipped) chromedriver to your Downloads folder in step 1, try this (subbing your username for <your_username>:
sudo cp /Users/<your_username>/Downloads/chromedriver /usr/bin
Profit!
/usr/bin should definitely work as your PATH, but you can double check all available PATHs by typing $PATH into Terminal.app and hitting enter.
Today Selenium stopped working for me in Mac Os. I am using python and I am getting:
"Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome'" error.
Solution: Please update your driver file.
My guess is that Chrome updated silently in the background. Make sure you have the latest selenium-webdriver gem and chromedriver.
Ċ½eljko Filipin is right, I fixed this issue by downloading the new binary. Apparently there was a silent update for chrome.
Replace the binary:
http://code.google.com/p/chromedriver/downloads/list
For all who installed using homebrew: it seems that there isn't the latest version available.
Download the zip file from http://code.google.com/p/chromedriver/downloads/list, unzip, and do sudo mv chromedriver /usr/local/Cellar/chromedriver/20.0.1133.0/bin to replace the current with the latest version (the version in the path won't reflect the actual chromedriver's version this way, but hey, it's working again until homebrew updates its recipe for chromedriver).
Homebrew now has the latest chromedriver, so if you're using homebrew, all you need to do is
$ brew unlink chromedriver
$ brew install chromedriver
Try doing a Update brew
brew update
brew upgrade
and you should be good
Related
I am trying to install homebrew on m1 MacBook but I am getting this error message every time when I try to run this command.
Please anyone help me to fix this.
How to install HomeBrew on new MacBook: macOS Big Sur
install HomeBrew from terminal Homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
After installation, we need to change path
Warning: /opt/homebrew/bin is not in your PATH.
==> Installation successful!
To change path, follow Next steps: - Add Homebrew to your PATH in /Users/username/.zprofile As mentioned in terminal:
echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> /Users/username/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"
All done ready to use brew, check HomeBrew version:
brew --version
Output
Homebrew 3.1.5
Homebrew/homebrew-core (git revision 5741ae3fec; last commit 2021-05-08)
Ok, I managed to figure this out after being pointed in the right direction. Full details can be found here: https://github.com/Homebrew/homebrew-cask/issues/100633
In summary, my ISPs (Virgin Media) Web Safe Settings were on, and this resulted in some issue with connecting to github (ping GitHub.com via terminal and search the IP to see where its pointing to), so had to turn off the web settings, rebooted my router just in case and used a new terminal window to ping github.com again and noticed a change in the IP address. Tried reinstalling Homebrew again and it worked!!
in my case, i fix the problem open the terminal as rosseta.
finder - application - utility - terminal - right mouse button - 'bring the imformation (i'm not sure, i'm korean user)' - check the 'open with the rosseta' - and try install homebrew again ! !
(copy-paste Homebrew with the terminal)
and...
==> Installation successful!
But, you will get a warning " /opt/homebrew/bin is not in your PATH". Then, follow the Next steps guide showed in terminal to finish add Homebrew to your PATH.
To end, type "brew -v" to check installed brew version.
I would like to run a GMT file wrote in tcsh environment. When I'm running it, I have the following error message :
dyld: Library not loaded: /opt/local/lib/libhdf5.100.dylib
Referenced from: /opt/local/lib/gmt4/bin/gmtset
Reason: image not found
I went to /opt/local/lib path, and indeed, libhdf5.103.dylib is installing, and not libhdf5.100.dylib. I did not find a way to reinstall libhdf5.100.dylib using port or brew.
The later doesn't work :
sudo port install libhdf5-100
sudo port install libhdf5.100
sudo port install libhdf5.100.dylib
I already try:
brew reinstall osgeo-gdal --build-from-source
But, this doesn't work. I have the following issue:
Warning: You are using macOS 10.11.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience while you are running this old version.
qt: macOS Sierra or newer is required.
Error: An unsatisfied requirement failed this build.
Do you have any ideas?
Thank you.
Looks like gdal needs to be rebuilt with the current hdf5. You can try:
sudo port uninstall gdal && sudo port install -s gdal
This will build gdal from source and link against the installed HDF5 library.
I get the following error when trying to install valgrind on the version of macOS using brew:
valgrind: This formula either does not compile or function as expected
on macOS versions newer than Sierra due to an upstream
incompatibility. Error: An unsatisfied requirement failed this build.
I have tried to follow suggestions from all related posts on the issue, and even tried building valgrind using the ./configure option after downloading the source tarball. But that too fails with a gcc incompatibility error, which I am unable to overcome, despite following workaround suggestions on the Web.
Any help would be appreciated.
TIA
Vinod
brew install --HEAD valgrind seems to work now.
See this issue for more details.
You may wish to build it directly and install instead of using home-brew. I have created a port of valgrind 3.13.0 to work on macOS High Sierra (10.13.x). You can get it here: https://github.com/padiakalpesh/valgrind_3.13_high_sierra
Once you have obtained the source, run the following commands from inside the source directory:
./configure
make
sudo make install
I'm using ios-webkit-debug-proxy on Linux to try and debug an iOS Safari host using chrome.
The debug proxy runs and gives
Listing devices on :9221
Connected :9222 to Will's iPhone (8a48ac86edd4f299xxxxxxxxxxxxxxx)
The page localhost:9222
Opening the devtools though gives a whole lot of blank. Clicking on lots of things yields little.
Can someone with experience with these things give me a nudge? Cheers
What Chrome version are you using? This might happen as this feature is broken since chrome 38. Try downloading Chromium 37 to solve the issue.
Checkout this Bug Report for details:
https://github.com/google/ios-webkit-debug-proxy/issues/78
Old binaries can be obtained from here:
http://sourceforge.net/projects/osxportableapps/files/Chromium/
I followed this procedure from Ryan Ewen:
Comprehensive instructions for Windows:
Get files from https://github.com/fishbone1/remotedebug-ios-webkit-adapter
Install iTunes (https://www.microsoft.com/en-us/p/itunes/9pb2mz1zmb1s)
Install scoop (https://scoop.sh)
scoop install nodejs nvm
scoop bucket add extras
scoop install ios-webkit-debug-proxy
nvm install 11.15.0 (version 12 doesn't work for the final couple of steps)
nvm use 11.15.0 (might have to reopen PowerShell after this, it'll tell you)
npm install -g vs-libimobile cd to your download of remotedebug-ios-webkit-adapter
npm install
npm start
Continue onto Step 3 from the readme
make sure you installed latest ios_webkit_debug_proxy:
brew install ios-webkit-debug-proxy
and then launch ios_webkit_debug_proxyusing command:
ios_webkit_debug_proxy -f chrome-devtools://devtools/bundled/inspector.html
BTW you must use developer's certificate to build the app!
Install the adapter with :
npm install remotedebug-ios-webkit-adapter -g
Then, run remotedebug_ios_webkit_adapter --port=9000
I've manually installed the Xcode command line tools from the Apple website, and I went through the install process but it doesn't seem to be working. I ran this from the terminal to see if it installed:
Zach-Boyette-MacBook-Pro-2:~ zachboyette$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 5.1.0.0.1.1396320587
volume: /
location: /
install-time: 1398301024
groups: com.apple.FindSystemFiles.pkg-group com.apple.DevToolsBoth.pkg-group com.apple.DevToolsNonRelocatableShared.pkg-group
So it looks like the command line tools have installed, but when I run this:
Zach-Boyette-MacBook-Pro-2:~ zachboyette$ xcode-select --install
A popup says: The "xcode-select" command requires the command line developer tools. Would you like to install the tools now?
I clicked install and then it said: Can't install the software because it is not currently available from the Software Update server.
I've read on other answers that the solution is to do a manual install, but I just did that so I don't understand why it's not working. Also, in Xcode downloads, it's not showing the Command Line Tools.
I've tried installing it manually many times so I don't know why it's not working.
Installing Jekyll still won't work:
Zach-Boyette-MacBook-Pro-2:~ zachboyette$ sudo gem install jekyll
Password:
Building native extensions. This could take a while...
ERROR: Error installing jekyll:
ERROR: Failed to build gem native extension.
EDIT: echo $PATH returns this:
Zach-Boyette-MacBook-Pro-2:~ zachboyette$ echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/zachboyette/.rvm/bin
Command Line Tools are not included in XCode 5.1.1
You have to install it manually, BUT DON'T USE "xcode-select --install". It does not work.
Open Xcode app.
Click on Xcode > Open Developer Tools > More Developers Tools.
That will take you to Downloads for Apple Developers web site.
Use your AppStore Id to login.
Download Command Line Tools for your Mac OS X version.
I have stumbled across this issue before when I completely hosed my development environment by deleting an ancient Xcode version.
Have you tried running sudo xcode-select -r to clean up? This sorted my problem.
From the man page:
-r, --reset
Unsets any user-specified developer directory, so that the
developer directory will be found via the default search mecha-
nism. This command must be run with superuser permissions (see
sudo(8)), and will affect all users on the system.
The easiest work around is to install the XCode app from the App Store then open XCode and agree to the Terms and Conditions.
From there the Command Line Developer Tools package can be installed on using xcode-select --install or by trying to use any command line developer tool in Terminal like git.