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
Time - Confirm page opens instead of Merchant page after clearing merchant field #82107
Version Number: 9.3.17-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#80480 Email or phone of affected tester (no customers):josidjnoidjoisjisod@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Money Requests
👋 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.
Classification: Frontend bug Causing PR: #80480 - "Update create transaction Manual flow to ask for merchant after asking for amount v2" by @nkdengineer (High confidence) Related Issues: None
Recommendation: REVERT
PR #80480 introduced complex navigation changes for the merchant step in the manual expense flow. The bug occurs when moving a time expense between reports and clearing the merchant field - the navigation logic does not properly handle the back navigation, causing the confirmation page to open instead of the merchant page.
Given the complexity of the navigation flow changes and the specific edge case affected, a revert is the safest approach to unblock the deploy while the navigation logic is fixed properly.
Labels: Keeping DeployBlockerCash (App deploy is blocked). Removing DeployBlocker (no backend changes involved).
📋 Detailed Analysis
Evidence
The bug follows this exact reproduction path:
Create time expense in workspace chat
Remove from report (moves to self DM)
Submit to workspace chat (triggers merchant step per new flow)
Clear merchant field and save
Click back button on confirmation page
Bug: Confirmation page opens instead of merchant page
This specific flow was introduced/modified in PR #80480 which changed when and how the merchant step appears in the expense creation flow.
src/libs/IOUUtils.ts - Added shouldRequireMerchant function
The merchant step component has a useFocusEffect hook (lines 85-90) that resets state, and navigation logic (lines 92-102) that determines next screen. When backTo parameter exists and merchant is cleared, the navigation does not properly maintain the merchant step in the back stack.
When merchant is cleared and saved during the "submit to workspace" flow, the backTo parameter exists, causing the code to call navigateBack() instead of explicitly navigating to confirmation. However, the back navigation stack is not properly configured for this edge case, resulting in incorrect page being shown on subsequent back button press.
Activity
melvin-bot commentedon Feb 11, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #80480
melvin-bot commentedon Feb 11, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 11, 2026
Triggered auto assignment to @sonialiap (
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.github-actions commentedon Feb 11, 2026
👋 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:
OSBotify commentedon Feb 11, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #80480 - "Update create transaction Manual flow to ask for merchant after asking for amount v2" by @nkdengineer (High confidence)
Related Issues: None
Recommendation: REVERT
PR #80480 introduced complex navigation changes for the merchant step in the manual expense flow. The bug occurs when moving a time expense between reports and clearing the merchant field - the navigation logic does not properly handle the back navigation, causing the confirmation page to open instead of the merchant page.
Given the complexity of the navigation flow changes and the specific edge case affected, a revert is the safest approach to unblock the deploy while the navigation logic is fixed properly.
Labels: Keeping
DeployBlockerCash(App deploy is blocked). RemovingDeployBlocker(no backend changes involved).📋 Detailed Analysis
Evidence
The bug follows this exact reproduction path:
This specific flow was introduced/modified in PR #80480 which changed when and how the merchant step appears in the expense creation flow.
Verification
PR #80480 modified these files:
src/pages/iou/request/step/IOURequestStepMerchant.tsx- Added navigation logic after save (lines 97-101)src/pages/iou/request/step/IOURequestStepAmount.tsx- AddedshouldRequireMerchantcheckssrc/pages/iou/request/step/IOURequestStepParticipants.tsx- Added merchant step navigationsrc/libs/IOUUtils.ts- AddedshouldRequireMerchantfunctionThe merchant step component has a
useFocusEffecthook (lines 85-90) that resets state, and navigation logic (lines 92-102) that determines next screen. WhenbackToparameter exists and merchant is cleared, the navigation does not properly maintain the merchant step in the back stack.Root Cause
In
IOURequestStepMerchant.tsxlines 97-101:When merchant is cleared and saved during the "submit to workspace" flow, the
backToparameter exists, causing the code to callnavigateBack()instead of explicitly navigating to confirmation. However, the back navigation stack is not properly configured for this edge case, resulting in incorrect page being shown on subsequent back button press.7 remaining items
lakchote commentedon Feb 11, 2026
@nkdengineer can you link the PR here please?
nkdengineer commentedon Feb 11, 2026
@lakchote, We reverted the offending PR, so I closed my PR.
cead22 commentedon Feb 11, 2026
Looks like the offending PR got reverted, so we can probably close this
m-natarajan commentedon Feb 11, 2026
Reproduced, Windows 11 / Chrome, v9.3.17-5 9Waiting for the validation results for other platform)
confirm.page.mp4
lakchote commentedon Feb 11, 2026
cc @nkdengineer @cead22 looks like it's still reproducible?
nkdengineer commentedon Feb 11, 2026
@lakchote It's not a bug now since the PR was reverted and merchant step is not a step before confirmation step now.
lakchote commentedon Feb 11, 2026
We can close this then.