[due for payment 2026-02-20] Different app navigation when invoice is sent for the first and second time from Account tab

[nlemma]

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.3.11-24
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: #78965
Email or phone of affected tester (no customers): sidnjosdnjdosijsojns@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.2
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Log in with a new account.
3. Create a workspace.
4. Go to workspace settings > More features.
5. Enable Invoices.
6. Go to Account tab.
7. Open FAB > Send invoice.
8. Send an invoice to any user.
   → Invoice room is opened when invoice is sent for the first time from Account tab.
9. Go back to Account tab.
10. Open FAB > Send invoice.
11. Send an invoice to any user.
    → Reports opens when invoice is sent from Account tab - expected Fix/77987 - Standardize product behavior using "Global Create" #78965

Expected Result:

When invoice is sent for the first time and second time from different tab other than Inbox, app navigation should be the same.

Actual Result:

In Step 8, when invoice is sent for the first time from Account tab, app opens invoice room.
In Step 11, when invoice is sent for the second time from Account tab, Reports tab opens.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7065353_1770124764971.ScreenRecording_02-03-2026_21-12-01_1.MP4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78965

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (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]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #78965 - "Fix/77987 - Standardize product behavior using Global Create" by @dmkt9 (High confidence)
Related Issues: #77987

Recommendation: REVERT

PR #78965 introduced logic to standardize navigation after expense creation from the global create button. However, this logic incorrectly treats invoices sent from the FAB (Floating Action Button) the same way as expenses, causing inconsistent navigation behavior.

Labels: Keeping DeployBlockerCash as this is a frontend bug requiring an App PR fix. Removing DeployBlocker as no backend changes are needed.

📋 Detailed Analysis

Evidence

The issue is reproducible on staging (version 9.3.11-24) and directly corresponds to PR #78965 which was merged on Feb 2, 2026. The PR explicitly changed navigation behavior for expenses created via the global create button, including invoices.

PR #78965 modified the invoice sending flow in SendInvoice.ts to use the new handleNavigateAfterExpenseCreate function, which determines navigation based on whether the user is on the Inbox tab and whether isFromGlobalCreate is true.

Verification

Key files modified by PR #78965 that relate to this bug:

1. src/libs/actions/IOU/SendInvoice.ts - Changed to call handleNavigateAfterExpenseCreate
2. src/libs/actions/IOU/index.ts - Added handleNavigateAfterExpenseCreate function and isFromFloatingActionButton flag
3. src/pages/iou/request/step/IOURequestStepConfirmation.tsx - Line 1064: isFromGlobalCreate: transaction?.isFromFloatingActionButton ?? transaction?.isFromGlobalCreate
4. src/pages/inbox/sidebar/FloatingActionButtonAndPopover.tsx - Line 652: Sets isFromFloatingActionButton: true when starting invoice from FAB

Root Cause

The navigation logic in handleNavigateAfterExpenseCreate (lines 1075-1113 in src/libs/actions/IOU/index.ts) works as follows:

1. If user is on Inbox tab OR isFromGlobalCreate is false → Open the invoice room (correct behavior)
2. If user is NOT on Inbox tab AND isFromGlobalCreate is true → Navigate to Reports > Invoice page (incorrect for invoices)

The bug occurs because:

• When sending an invoice from the Account tab FAB, isFromFloatingActionButton is set to true
• Line 1064 of IOURequestStepConfirmation.tsx uses: transaction?.isFromFloatingActionButton ?? transaction?.isFromGlobalCreate
• This means invoices from FAB are treated as "from global create"
• The first send may work due to transaction draft state, but subsequent sends retain the isFromFloatingActionButton flag
• The function then navigates to Reports > Invoice instead of opening the invoice room

Expected behavior: Invoices should always open the invoice room after sending, regardless of which tab the user is on or whether sent from FAB.

[dangrous]

@dmkt9 do you have a sec to look at this one? Seems like it could be an easy fix rather than a revert.