Skip to content

Book travel - User is not redirected to upgrade success page #75038

Closed

Description

@mitarachim

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: v9.2.57-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74035
Email or phone of affected tester (no customers): anythingmo@tstsg.com
Issue reported by: Applause Internal Team
Device used: macOS/chrome
App Component: Other

Action Performed:

Prerequisite:
use a private domain account without a workspace

  1. Press create + button > Book travel
  2. Press Book travel
  3. Press Upgrade
  4. refresh page
  5. Create the workspace by confirming

Expected Result:

User is redirected to upgrade success page

Actual Result:

RHN closes with out showing upgrade success page

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

Bug7002663_1763029919862.Screen_Recording_2025-11-13_at_12.30.22_in_the_afternoon.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @isabelastisser

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 13, 2025
  2. melvin-bot commented on Nov 13, 2025

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (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. melvin-bot commented on Nov 13, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 13, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 13, 2025

    @github-actions
    Contributor

    👋 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.
  6. marcochavezf commented on Nov 13, 2025

    @marcochavezf
    Contributor

    I don't think it's a backend deploy blocker. Also, I'm going to assign the help label to get more 👀 in case someone knows what could be offending PR

  7. 4 remaining items

  8. cristipaval commented on Nov 13, 2025

    @cristipaval
    Contributor

    this is the offending PR. But I think this is an NAB that can be fixed by the authors and get the regular path deploy.

  9. bernhardoj commented on Nov 14, 2025

    @bernhardoj
    Contributor

    PR is ready

    cc: @jayeshmangwani

  10. jayeshmangwani commented on Dec 8, 2025

    @jayeshmangwani
    Contributor

    @isabelastisser @puneetlath This issue can be closed now. The PR #75152 has been in production for two weeks, and since this was a regression, the payment was handled in the original issue #73396.

  11. puneetlath commented on Dec 8, 2025

    @puneetlath
    Contributor

    Cool, thanks.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions