search

wimpywarlord / appliFLY

Automate application process for ASU on-campus Job portal
https://kshitijdhyani.com/appliFLY/
7 stars 3 forks source link

Unexpected error #7

Closed Devraj1997 closed 1 year ago

Devraj1997 commented 1 year ago

I ran the following command: python appliFly.py The application did log into my asu and searched for jobs. Later crashed with following error. Issue

wimpywarlord commented 1 year ago

Adding for further investigation

WhatsApp Image 2023-09-12 at 22 08 51

wimpywarlord commented 1 year ago

Initial Recommendations: https://stackoverflow.com/questions/75160044/how-do-i-resolve-this-error-in-selenium-error-couldnt-read-tbscertificate-as

https://stackoverflow.com/questions/47392423/python-selenium-devtools-listening-on-ws-127-0-0-1/56408800#56408800

Devraj1997 commented 1 year ago

WhatsApp Image 2023-09-12 at 22 29 06

wimpywarlord commented 1 year ago

Tested Chrome version: 116.0.5845.187

investigation:https://stackoverflow.com/questions/69801774/selenium-python-code-that-used-to-work-now-opens-browser-and-then-gets-stuck-in

wimpywarlord commented 1 year ago

Solution

This turned out to versioning issue, between selenium driver, python and chrome.

I found an error in the script logs saying:

ERROR:page_load_metrics_update_dispatcher.cc(194)] Invalid first_paint error using Selenium Python ChromeDriver

Upon surfing the web, I found this thread: https://stackoverflow.com/questions/75830184/errorpage-load-metrics-update-dispatcher-cc194-invalid-first-paint-error-usi

It talks about how the above error message indicates that there is a mismatch between the binary versions you are using.

On a more deeper level

As per the [comment](https://bugs.chromium.org/p/chromedriver/issues/detail?id=3341#c1) within the [discussion](https://bugs.chromium.org/p/chromedriver/issues/detail?id=3341):

The supported configuration is to always match the version between Chrome and ChromeDriver - so when you are using Chrome 80, you should use Chrome 80. It is also possible to run ChromeDriver N with Chrome N+1, but this will always generate the warning you see. Most operations will complete successfully, but it is not the recommended approach.

The solution is to upgrade ChromeDriver to version 80: https://chromedriver.chromium.org/downloads

This is understandable because, most of the operations were working fine in the script, but some operations were acting wonky.

The straight and simple solution is to

You need to ensure:

Go to Google’s official driver support website: https://chromedriver.chromium.org/downloads and then go to the downloads section : https://googlechromelabs.github.io/chrome-for-testing/

Download the latest stable version of the chrome driver according to your operating system : https://googlechromelabs.github.io/chrome-for-testing/#stable

Copy the absolute path to the chrome.exe file inside the downloaded chrome driver folder.

Look into line number 61 in [appliFly.py](http://appliFly.py) file and uncomment as well as update the absolute path to the chrome driver which you just downloaded from the above mentioned link.

```
# You can use other drivers like Firefox, Edge, etc.

  # ____________ If Facing Jobs 0 Jobs found issue ________________
  # Absolute Path to Chrome Driver Example: C:\Users\ASUS\Downloads\chrome\chrome.exe
  # chromeDriver = webdriver.Chrome(executable_path=r"Absolute Path to the Chrome Driver")  # Uncomment this if facing 0 jobs found issue
  # ____________ No Erros ____________________
  chromeDriver = webdriver.Chrome()  # Comment this out if facing 0 jobs found issue
```

Download the latest version chrome or update the existing version to the latest version. Here is how: https://support.google.com/chrome/answer/95414?hl=en&co=GENIE.Platform%3DDesktop

Therefore re-clone the repository from Github and do a fresh pip install -r requirements.txt

wimpywarlord commented 1 year ago

Hey, @Devraj1997 I would be more than happy to assist you with this over a call if you are unable to figure it out.

Shoot any questions that you may have.

wimpywarlord commented 1 year ago

Closing, as resolved