Closed chy8803 closed 5 months ago
Thanks for reporting this issue. There is a check to see if the flight is departed before attempting to check in (and skips it if it has departed). It uses the departure status of the flight though, not the time and perhaps Southwest has changed the status keyword for departed flights.
Could you add the line print(flight_info["departureStatus"])
on line 63 of lib/checkin_scheduler.py
to see what the departure status for the two flights are? If not, I have access to a flight departing later today so I can use that. (Edit: The departed flight is actually reporting the status the script expects once departed, so I'm interested to see what yours says)
Some more details if you or others are interested: Because Southwest uses the same reservation (conf number, name), Southwest thinks you're trying to check in to the returning flight, but the script thinks it is the departing flight (hence the Too early to check in
message).
2024-05-06 09:19:32 DEBUG Process-2[checkin_scheduler:58]: 2 flights found under current reservation
None
None
2024-05-06 09:19:32 DEBUG Process-2[checkin_scheduler:44]: 2 total flights were found
2024-05-06 09:19:32 DEBUG Process-2[checkin_scheduler:110]: 2 new flights found
2024-05-06 09:19:32 DEBUG Process-2[checkin_scheduler:114]: Scheduling 2 flights for check-in
2024-05-06 09:19:32 DEBUG Process-2[checkin_handler:47]: Scheduling check-in for current flight
2024-05-06 09:19:32 DEBUG Process-2[checkin_handler:47]: Scheduling check-in for current flight
2024-05-06 09:19:32 DEBUG Process-2[notification_handler:69]: Sending new flights notification
Successfully scheduled the following flights to check in for FIRST LAST:
Flight from San Jose to Honolulu (Oahu) on 2024-04-30 8:00 AM PDT
Flight from Honolulu (Oahu) to San Jose on 2024-05-07 12:00 PM HST
It returned None and None
I have a fix for this in the departed-flights branch. Could you do git pull && git checkout departed-flights
and then run the script again to see if the issue persists? If you aren't using the develop
branch, you will need to run pip install -r requirements.txt
as there was a new dependency added recently.
I'm not sure why the departure status of the old flight is None. Perhaps its because its a week old. I have a long flight I can access so I will look back in a week to see if I get the same status, which will confirm the hypothesis that flights on the same reservation don't have a departure status after a long period of time.
I changed the check to not rely on the departureStatus
returned by Southwest but instead see if the flight time is in the past.
I commended on the commit and seems like i got some package import error. I fixed it by changing from datetime import UTC as datetime_utc line 4 and return datetime.now(datetime_utc) line 79 to
return datetime.now(timezone.utc)
My check-in time is passed already so I won't be able to verify that tho, but I will also keep an eye on it. Thanks.
Thank you, will fix that (the original only works for Python 3.11+).
My check-in time is passed already so I won't be able to verify that tho, but I will also keep an eye on it. Thanks.
No worries. I have a flight in a similar situation to yours now so the fix I have is tested on a real situation and is probably more robust. I'll merge the fix and close this issue, but if you still receive any issues with this in the future, I can reopen it.
I have a long flight I can access so I will look back in a week to see if I get the same status, which will confirm the hypothesis that flights on the same reservation don't have a departure status after a long period of time.
To follow up, the flight departure status becomes None after a few days (probably a recent change by Southwest).
I have a fix for this in the departed-flights branch. Could you do
git pull && git checkout departed-flights
and then run the script again to see if the issue persists? If you aren't using thedevelop
branch, you will need to runpip install -r requirements.txt
as there was a new dependency added recently.I'm not sure why the departure status of the old flight is None. Perhaps its because its a week old. I have a long flight I can access so I will look back in a week to see if I get the same status, which will confirm the hypothesis that flights on the same reservation don't have a departure status after a long period of time.
I changed the check to not rely on the
departureStatus
returned by Southwest but instead see if the flight time is in the past.
Thanks for this, I was able to successfully check in for a returning flight on my round trip reservation using develop
branch 👍
Version
Auto-Southwest Check-In v7.4
Browser Version
124.0.6367.119
Description
Failed to schedule a check-in on a return flight within a round trip reservation.
To Reproduce
python3 southwest.py {Reservation#} {FirstName} {LastName} -v
Expected Behavior
Check-in can be scheduled.
Relevant logs and program output
Additional context
"messageKey":"ERROR__AIR_TRAVEL__BEFORE_CHECKIN_WINDOW"
Seems it is using the departure flight date as the check-in date for the returning flight check-in date?