Travel - Alaska Airlines doesn't present for travel 's list

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.1.69-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6317894
Email or phone of affected tester (no customers): applausetester+061925f@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: mac 15.4.1, iPhone 16 Pro Max/ 18.5
App Component: Other

Action Performed:

1. On the travel home page
2. Click on the date and set it to 1 month in the future
3. On the Where from? enter "SEA" (Seattle–Tacoma International Airport)
4. On the Where to? enter "SFO" (San Francisco International Airport)
5. Search the flight
6. On the results - Find the ones from Alaska Airlines

Expected Result:

Alaska Airlines should be present in list.

Actual Result:

Alaska Airlines doesn't present for travel 's list

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @Gonals (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[parasharrajat]

Not related to App.

[mallenexpensify]

Unable to reproduce.