Troubleshooting of selenium errors: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
(Created page with "[https://www.selenium.dev/ SeleniumHQ Browser Automation] == How to resolve Uncaught Facebook\WebDriver\Exception\InvalidSelectorException == Error message <pre> PHP Fatal er...")
 
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
[https://www.selenium.dev/ SeleniumHQ Browser Automation]
[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]]

Latest revision as of 17:52, 7 February 2025

SeleniumHQ Browser Automation (php-webdriver/php-webdriver: PHP client for Selenium/WebDriver protocol. Previously facebook/php-webdriver)

How to resolve the selenium errors[edit]

  • Checking the standalone selenium server is running or not ps aux | grep selenium on Linux  
  • Checking the log file of standalone selenium server e.g. launching the server by the command sudo nohup java -jar selenium-server-standalone-3.141.59.jar > /home/user/selenium.log 2>&1 &. The log file was located at /home/user/selenium.log
  • (optional) Checking the port where the selenium server is running e.g. wget http://localhost:4444
  • Checking the error log file of HTTP server e.g. sudo tail /var/log/nginx/error.log
  • (optional) Checking the error log file of PHP-FPM e.g. sudo tail /var/log/www.access.log which its file path defined in the configuration file /etc/php-fpm.d/www.conf
  • (optional) Checking the keyboard event e.g. CTRL works on Win   but not works on macOS icon_os_mac.png [1]

How to resolve Uncaught Facebook\WebDriver\Exception\InvalidSelectorException[edit]

Error message 

PHP Fatal error:  Uncaught Facebook\WebDriver\Exception\InvalidSelectorException: invalid selector: The result of the xpath expression "xxx" is: [object Attr]. It should be an element.
  (Session info: chrome=83.0.4103.61) in /path/to/vendor/php-webdriver/webdriver/lib/Exception/WebDriverException.php:105

Situation

  • After the term was keyed in into the text box, the script shuld auto click the specified button which specified by XPath expression.

Possibile soultions

  • Solution1: Using headless chrome[2]
  • Solution2: Not click the button which specified by XPath expression. Send the ENTER to submit the form[3].

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[edit]

Situation: Updating the ChromeDriver

  • Before Updating, If you encounter “file in use” errors:
    • Win   Open Command Prompt as Administrator, Run command: taskkill /IM "chromedriver.exe" /F
  • Two option to update the ChromeDriver
  • Ensure the version matches your installed Chrome browser. Replace the existing ChromeDriver file

How to resolve macOS says the *.app is damaged. What now?[edit]

Error message[4][5] 

“Google Chrome for Testing.app” is damaged and can’t be opened. You should move it to the Trash.

Solution

  • Open the terminal, and key-in the following command:
xattr -cr 'Google Chrome for Testing.app'

References[edit]

  1. ↑ python - Selenium - send keys - what element should I use - Stack Overflow
  2. ↑ Getting Started with Headless Chrome  |  Web  |  Google Developers
  3. ↑ selenium - Emulate keypress in webdriver using php - Stack Overflow
  4. ↑ GoogleChromeLabs/chrome-for-testing https://github.com/GoogleChromeLabs/chrome-for-testing
  5. ↑ 解決「Google Chrome for Testing.app」已損毀，無法打開。 你應該將其丟到「垃圾桶」的問題


Retrieved from "https://wiki.planetoid.info/index.php?title=Troubleshooting_of_selenium_errors&oldid=25451"