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
[RCA #72674] Distance - Amount field is blank, Rate field shows pending on confirm page #75387
Version Number: 9.2.60-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: Exp #74791 Email or phone of affected tester (no customers):sjdsjnodijsisjio@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Click + > Track distance > Manual.
Enter amount > Next.
Expected Result:
Amount and Rate field will show the correct info.
Actual Result:
Amount field is blank, Rate field shows pending on confirm page.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Distance - Amount field is blank, Rate field shows pending on confirm page[/-][+][RCA #74791] Distance - Amount field is blank, Rate field shows pending on confirm page[/+]on Nov 18, 2025
changed the title [-][RCA #74791] Distance - Amount field is blank, Rate field shows pending on confirm page[/-][+][RCA #72674] Distance - Amount field is blank, Rate field shows pending on confirm page[/+]on Nov 18, 2025
Activity
melvin-bot commentedon Nov 18, 2025
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.melvin-bot commentedon Nov 18, 2025
Triggered auto assignment to @MarioExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 18, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 18, 2025
👋 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:
[-]Distance - Amount field is blank, Rate field shows pending on confirm page[/-][+][RCA #74791] Distance - Amount field is blank, Rate field shows pending on confirm page[/+]twisterdotcom commentedon Nov 18, 2025
@grgia should we assign you to this?
MarioExpensify commentedon Nov 18, 2025
@grgia @twisterdotcom I believe this is actually related to other PR. See discussion here.
[-][RCA #74791] Distance - Amount field is blank, Rate field shows pending on confirm page[/-][+][RCA #72674] Distance - Amount field is blank, Rate field shows pending on confirm page[/+]blimpich commentedon Nov 18, 2025
Based on the PR being reverted being a frontend PR, this is frontend related, not a backend deploy blocker
melvin-bot commentedon Nov 18, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
twisterdotcom commentedon Nov 18, 2025
What can I possibly do here to help? This is my only
Hourlyright now.melvin-bot commentedon Nov 18, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Nov 19, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
IuliiaHerets commentedon Nov 19, 2025
This issue can't be reproduced anymore
20251119_163028.mp4
grgia commentedon Nov 19, 2025
Thank you for retesting @IuliiaHerets !