Skip to content

Travel - Unable to book travel, an error occurred #55894

Closed

Description

@lanitochka17

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.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.

  1. ND: Sign in with one of the admins account
  2. OD: Sign in with one of the admins account and run script on workspace tab:
    NVP.set('travelSettings', {'testAccount': true});
  3. ND: Go to the Travel page and click the Book Travel button
  4. ND: Enter address
  5. 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 evidence
Bug6726620_1738091465959.bandicam_2025-01-28_20-39-58-971.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 28, 2025
  2. melvin-bot commented on Jan 28, 2025

    @melvin-bot

    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.

  3. stitesExpensify commented on Jan 29, 2025

    @stitesExpensify
    Contributor

    Hey @lanitochka17 can you please update any travel-related QA steps to use this script

    var settings = NVP.get('travelSettings') || {};
    settings.testAccount = true;
    NVP.set('travelSettings', settings);
    

    Instead of the current NVP.set('travelSettings', {'testAccount': true});?

  4. lanitochka17 commented on Jan 29, 2025

    @lanitochka17
    Author
  5. stitesExpensify commented on Jan 29, 2025

    @stitesExpensify
    Contributor

    Thank you! This should prevent accidental deletion of any existing travel data and prevent false-positives :)

  6. stitesExpensify commented on Jan 29, 2025

    @stitesExpensify
    Contributor

    Soon this won't be a problem because we will set the entirety of @applause.expensifail.com to be a test domain

  7. trjExpensify commented on Jan 31, 2025

    @trjExpensify
    Contributor

    @stitesExpensify are you saying this bug is known, or asking for a retest from Applause after following those steps?

  8. stitesExpensify commented on Jan 31, 2025

    @stitesExpensify
    Contributor

    Yes, I don't think we need to keep this open. Travel is definitely still working on both prod and staging

  9. IuliiaHerets commented on Mar 25, 2025

    @IuliiaHerets

    QA team can repro this issue in the latest build (v9.1.18-3), used account applausetester+travel33@applause.expensifail.com

    58899-Web.mp4
  10. trjExpensify commented on Mar 25, 2025

    @trjExpensify
    Contributor

    Soon this won't be a problem because we will set the entirety of @applause.expensifail.com to be a test domain

    @stitesExpensify did we do this then?

  11. stitesExpensify commented on Mar 27, 2025

    @stitesExpensify
    Contributor

    Yes, we did do that. I'll look into why this error happened

  12. 13 remaining items

  13. trjExpensify commented on Apr 15, 2025

    @trjExpensify
    Contributor

    The PR we were held on was deployed last week. @shubham1206agra can you confirm that we can close this issue then?

  14. 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
  15. shubham1206agra commented on Apr 15, 2025

    @shubham1206agra
    Contributor
  16. trjExpensify commented on Apr 15, 2025

    @trjExpensify
    Contributor

    Cool, closing.

  17. vincdargento commented on Jul 24, 2025

    @vincdargento

    @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
  18. stitesExpensify commented on Jul 25, 2025

    @stitesExpensify
    Contributor

    @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

  19. trjExpensify commented on Jul 25, 2025

    @trjExpensify
    Contributor

    I agree with that, going to close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions