search

jdholtz / auto-southwest-check-in

A Python script that automatically checks in to your Southwest flight 24 hours beforehand.
GNU General Public License v3.0
458 stars 87 forks source link

Error occurs on login v7.1 #208

Closed wpkato closed 9 months ago

wpkato commented 9 months ago

Version

Auto-Southwest Check-In v7.1

Browser Version

Using browser version: 120.0.6099.224

Description

Upon executing script, at login to SWA, script errors out and crashes out

To Reproduce

Execute script: python3 southwest.py --verbose username passwd

Expected Behavior

Script schedules appropriate checkins and fare checks and sleeps till next run

Relevant logs and program output

2024-01-27 09:28:37 DEBUG MainProcess[log:23]: Initialized the application
2024-01-27 09:28:37 DEBUG MainProcess[main:112]: Auto-Southwest Check-In v7.1
2024-01-27 09:28:37 DEBUG MainProcess[main:113]: Called with 2 arguments
2024-01-27 09:28:37 DEBUG MainProcess[config:107]: Initializing configuration file
2024-01-27 09:28:37 DEBUG MainProcess[config:135]: Reading the configuration file
2024-01-27 09:28:37 DEBUG MainProcess[config:139]: No configuration file found. Using defaults
2024-01-27 09:28:37 DEBUG MainProcess[config:118]: Creating configurations for 1 accounts
2024-01-27 09:28:37 DEBUG MainProcess[main:129]: Account added through CLI arguments
2024-01-27 09:28:37 DEBUG MainProcess[main:142]: Monitoring 1 accounts and 0 reservations
2024-01-27 09:28:37 DEBUG Process-1[reservation_monitor:154]: Acquiring lock...
2024-01-27 09:28:37 DEBUG Process-1[reservation_monitor:156]: Lock acquired
2024-01-27 09:28:37 DEBUG Process-1[reservation_monitor:178]: Retrieving reservations for account
2024-01-27 09:28:37 DEBUG Process-1[webdriver:103]: Starting webdriver for current session
2024-01-27 09:28:39 DEBUG Process-1[webdriver:119]: Using browser version: 120.0.6099.224
2024-01-27 09:28:39 DEBUG Process-1[webdriver:123]: Loading Southwest Check-In page
2024-01-27 09:28:42 DEBUG Process-1[webdriver:80]: Logging into account to get a list of reservations and valid headers
2024-01-27 09:28:44 DEBUG Process-1[webdriver:152]: Waiting for headers_set to be set
2024-01-27 09:28:44 DEBUG Process-1[webdriver:156]: headers_set set successfully
2024-01-27 09:28:44 DEBUG Process-1[webdriver:144]: Login response has been received
2024-01-27 09:28:49 DEBUG Process-1[webdriver:186]: Login form failed to submit. Clicking login button again

Additional context

File "/home/sjilagan/auto-southwest-check-in/lib/webdriver.py", line 93, in get_reservations self._wait_for_login(driver, account_monitor) File "/home/sjilagan/auto-southwest-check-in/lib/webdriver.py", line 163, in _wait_for_login self._click_login_button(driver) File "/home/sjilagan/auto-southwest-check-in/lib/webdriver.py", line 187, in _click_login_button driver.click(login_button) File "/home/sjilagan/.local/lib/python3.9/site-packages/seleniumbase/core/sb_driver.py", line 54, in click page_actions.click(self.driver, *args, **kwargs) File "/home/sjilagan/.local/lib/python3.9/site-packages/seleniumbase/fixtures/page_actions.py", line 1526, in click element.click() File "/home/sjilagan/.local/lib/python3.9/site-packages/selenium/webdriver/remote/webelement.py", line 93, in click self._execute(Command.CLICK_ELEMENT) File "/home/sjilagan/.local/lib/python3.9/site-packages/selenium/webdriver/remote/webelement.py", line 394, in _execute return self._parent.execute(command, params) File "/home/sjilagan/.local/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 347, in execute self.error_handler.check_response(response) File "/home/sjilagan/.local/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 229, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.ElementClickInterceptedException: Message: element click intercepted: Element is not clickable at point (712, 302). Other element would receive the click:

(Session info: chrome=120.0.6099.224) Stacktrace:

0 0x5616f0201f83

1 0x5616efebacf7

2 0x5616eff12d92

3 0x5616eff107f4

4 0x5616eff0d894

5 0x5616eff0c4b9

6 0x5616efefe313

7 0x5616eff340b2

8 0x5616efefdb49

9 0x5616eff344ce

10 0x5616eff53006

11 0x5616eff33e53

12 0x5616efefbdd4

13 0x5616efefd1de

14 0x5616f01c6531

15 0x5616f01ca455

16 0x5616f01b2f55

17 0x5616f01cb0ef

18 0x5616f019699f

19 0x5616f01ef008

20 0x5616f01ef1d7

21 0x5616f0201124

22 0x7fc5680faea7 start_thread

jdholtz commented 9 months ago

This error is actually a 429. The exception you are seeing has been handled in the develop branch to correctly report the error (this is a duplicate of #189). Closing to keep track of the issue in #201.