You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Travel - Unable to book travel, an error occurred #55894
Version Number: 9.0.90-2 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail:#55300 Email or phone of affected tester (no customers): new expensifail account Issue reported by: Applause - Internal Team Component: Other
Action Performed:
Precondition: use new accounts: owner of a workspace and 1 or more admins, with logins from the same private domains that never used Travel before.
ND: Sign in with one of the admins account
OD: Sign in with one of the admins account and run script on workspace tab:
NVP.set('travelSettings', {'testAccount': true});
ND: Go to the Travel page and click the Book Travel button
ND: Enter address
ND: Accept the Terms and Conditions > click Continue
Expected Result:
Travel page is opened in a different tab
Actual Result:
An error 'Something went wrong'
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6726620_1738091465959.bandicam_2025-01-28_20-39-58-971.mp4
changed the title [-][Hold PR #57537] Travel - Unable to book travel, an error occurred[/-][+]Travel - Unable to book travel, an error occurred[/+]on Apr 15, 2025
Activity
melvin-bot commentedon Jan 28, 2025
Triggered auto assignment to @trjExpensify (
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.stitesExpensify commentedon Jan 29, 2025
Hey @lanitochka17 can you please update any travel-related QA steps to use this script
Instead of the current
NVP.set('travelSettings', {'testAccount': true});?lanitochka17 commentedon Jan 29, 2025
@stitesExpensify ok
stitesExpensify commentedon Jan 29, 2025
Thank you! This should prevent accidental deletion of any existing travel data and prevent false-positives :)
stitesExpensify commentedon Jan 29, 2025
Soon this won't be a problem because we will set the entirety of @applause.expensifail.com to be a test domain
trjExpensify commentedon Jan 31, 2025
@stitesExpensify are you saying this bug is known, or asking for a retest from Applause after following those steps?
stitesExpensify commentedon Jan 31, 2025
Yes, I don't think we need to keep this open. Travel is definitely still working on both prod and staging
IuliiaHerets commentedon Mar 25, 2025
QA team can repro this issue in the latest build (v9.1.18-3), used account applausetester+travel33@applause.expensifail.com
58899-Web.mp4
trjExpensify commentedon Mar 25, 2025
@stitesExpensify did we do this then?
stitesExpensify commentedon Mar 27, 2025
Yes, we did do that. I'll look into why this error happened
13 remaining items
trjExpensify commentedon Apr 15, 2025
The PR we were held on was deployed last week. @shubham1206agra can you confirm that we can close this issue then?
[-][Hold PR #57537] Travel - Unable to book travel, an error occurred[/-][+]Travel - Unable to book travel, an error occurred[/+]shubham1206agra commentedon Apr 15, 2025
@trjExpensify Yes
trjExpensify commentedon Apr 15, 2025
Cool, closing.
vincdargento commentedon Jul 24, 2025
@trjExpensify Testers were able to reproduce this issue again. Re-opening in case you want to take a look.
Recording.814.mp4
bandicam.2025-07-24.15-16-15-220.mp4
stitesExpensify commentedon Jul 25, 2025
@vincdargento can you create a new issue please? This is almost certainly a different root case given the original issue was opened 6 months ago
trjExpensify commentedon Jul 25, 2025
I agree with that, going to close this out.