15,050
edits
Troubleshooting of selenium errors: Difference between revisions
Jump to navigation
Jump to search
→How to resolve [WARNING]: This version of ChromeDriver only supports Chrome version xx or [WARNING]: This version of ChromeDriver has not been tested with Chrome version 86
mNo edit summary |
|||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[https://www.selenium.dev/ SeleniumHQ Browser Automation] ([https://github.com/php-webdriver/php-webdriver php-webdriver/php-webdriver: PHP client for Selenium/WebDriver protocol. Previously facebook/php-webdriver]) | [https://www.selenium.dev/ SeleniumHQ Browser Automation] ([https://github.com/php-webdriver/php-webdriver php-webdriver/php-webdriver: PHP client for Selenium/WebDriver protocol. Previously facebook/php-webdriver]) | ||
== How to resolve the selenium errors == | |||
* Checking the standalone selenium server is running or not {{kbd | key=<nowiki>ps aux | grep selenium</nowiki>}} on {{Linux}} | |||
* Checking the log file of standalone selenium server e.g. launching the server by the command {{kbd | key=<nowiki>sudo nohup java -jar selenium-server-standalone-3.141.59.jar > /home/user/selenium.log 2>&1 &</nowiki>}}. The log file was located at {{kbd | key=<nowiki>/home/user/selenium.log</nowiki>}} | |||
* (optional) Checking the port where the selenium server is running e.g. {{kbd | key=<nowiki>wget http://localhost:4444</nowiki>}} | |||
* Checking the error log file of HTTP server e.g. {{kbd | key=<nowiki>sudo tail /var/log/nginx/error.log</nowiki>}} | |||
* (optional) Checking the error log file of PHP-FPM e.g. {{kbd | key=<nowiki>sudo tail /var/log/www.access.log</nowiki>}} which its file path defined in the configuration file {{kbd | key=<nowiki>/etc/php-fpm.d/www.conf</nowiki>}} | |||
* (optional) Checking the keyboard event e.g. CTRL works on {{Win}} but not works on {{Mac}}<ref>[https://stackoverflow.com/questions/30937153/selenium-send-keys-what-element-should-i-use python - Selenium - send keys - what element should I use - Stack Overflow]</ref> | |||
== How to resolve Uncaught Facebook\WebDriver\Exception\InvalidSelectorException == | == How to resolve Uncaught Facebook\WebDriver\Exception\InvalidSelectorException == | ||
| Line 14: | Line 23: | ||
* Solution1: Using headless chrome<ref>[https://developers.google.com/web/updates/2017/04/headless-chrome Getting Started with Headless Chrome | Web | Google Developers]</ref> | * Solution1: Using headless chrome<ref>[https://developers.google.com/web/updates/2017/04/headless-chrome Getting Started with Headless Chrome | Web | Google Developers]</ref> | ||
* Solution2: Not click the button which specified by XPath expression. Send the {{kbd | key=ENTER}} to submit the form<ref>[https://stackoverflow.com/questions/21243860/emulate-keypress-in-webdriver-using-php selenium - Emulate keypress in webdriver using php - Stack Overflow]</ref>. | * Solution2: Not click the button which specified by XPath expression. Send the {{kbd | key=ENTER}} to submit the form<ref>[https://stackoverflow.com/questions/21243860/emulate-keypress-in-webdriver-using-php selenium - Emulate keypress in webdriver using php - Stack Overflow]</ref>. | ||
== How to resolve [WARNING]: This version of ChromeDriver only supports Chrome version xx or [WARNING]: This version of ChromeDriver has not been tested with Chrome version 86 == | |||
Situation: Updating the ChromeDriver | |||
* Before Updating, If you encounter “file in use” errors: | |||
** {{Win}} Open Command Prompt as Administrator, Run command: {{kbd | key=<nowiki>taskkill /IM "chromedriver.exe" /F</nowiki>}} | |||
* Two option to update the ChromeDriver | |||
** Option 1: Manual Download: Download ChromeDriver from [https://chromedriver.chromium.org/downloads ChromeDriver Downloads] | |||
** Option 2: Package Managers: On {{Mac}}/{{Linux}}, use [https://brew.sh/ Homebrew]. On {{Win}}, use [https://chocolatey.org/ Chocolatey]. | |||
* Ensure the version matches your installed Chrome browser. Replace the existing ChromeDriver file | |||
== How to resolve macOS says the *.app is damaged. What now? == | |||
Error message<ref>GoogleChromeLabs/chrome-for-testing https://github.com/GoogleChromeLabs/chrome-for-testing</ref><ref>[https://errerrors.blogspot.com/2023/07/how-to-fix-google-chrome-for-testing.app-is-damaged-and-cannot-be-opened.html 解決「Google Chrome for Testing.app」已損毀，無法打開。 你應該將其丟到「垃圾桶」的問題]</ref> | |||
<pre> | |||
“Google Chrome for Testing.app” is damaged and can’t be opened. You should move it to the Trash. | |||
</pre> | |||
Solution | |||
* Open the terminal, and key-in the following command: | |||
<pre> | |||
xattr -cr 'Google Chrome for Testing.app' | |||
</pre> | |||
== References == | == References == | ||
| Line 19: | Line 50: | ||
{{Template:Troubleshooting}} | {{Template:Troubleshooting}} | ||
[[Category:Web scraping]] | |||