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
463 stars 89 forks source link

Auto-southwest-check-in attempts to checkin for already traveled leg #265

Closed mhardin closed 6 months ago

mhardin commented 6 months ago

Version

Auto-Southwest Check-In v7.4

Browser Version

125.0.6422.76

Description

I used this script to checkin for my flight that I traveled on 5/23. I then tried using the script to checkin for my returning leg. However, the script seems to think it needs to check me in for the already traveled leg on 5/23. It runs into an error and then it won't try to automatically check me in for the flight on 5/27. Log output below (with private details omitted)

Successful checkin for the leg on 5/23:

matthew@matthews-mbp auto-southwest-check-in % python3 southwest.py foo_confirmation_code matthew
Successfully scheduled the following flights to check in for matthew :
Flight from DES1 to DES2 on 2024-05-23 5:30 PM PDT
Flight from DES2 to DES1 on 2024-05-27 6:15 PM MDT

Checking in to flight from 'DES1' to 'DES2' for matthew

Successfully checked in to flight from 'DES1' to 'DES2' for matthew!
Matthew got B22!

Then here is the error output when trying to checkin for the 5/27 leg:

matthew@matthews-mbp auto-southwest-check-in % python3 southwest.py foo_confirmation_code matthew
Successfully scheduled the following flights to check in for matthew:
Flight from DES1 to DES2 on 2024-05-23 5:30 PM PDT
Flight from DES2 to DES1 on 2024-05-27 6:15 PM MDT

Checking in to flight from 'DES1' to 'DES2' for matthew

Requesting error during fare check. Bad Request 400. Skipping...
Failed to check in to flight for matthew. Reason: Too Many Requests 429.
Check in at this url: https://mobile.southwest.com/check-in

To Reproduce

See above, you need a flight with an already traveled leg. The checkin script shouldn't be trying to checkin for a flight that has already been traveled.

Expected Behavior

No response

Relevant logs and program output

No response

Additional context

No response

jdholtz commented 6 months ago

This is a duplicate of #257. The fix is on the develop branch. To get the fix on your machine you can run git pull && git checkout develop.

mhardin commented 6 months ago

That’s weird.. this was reproducing when I checked out the repo this afternoon. Does that check out the develop branch by default?

jdholtz commented 6 months ago

Does that check out the develop branch by default?

By default you use the master branch which does not have the fixes yet (it only holds full releases), but I will make a release soon which will push this fix to the master branch.