Invoice - Merchant page opens when sending from FAB, but does not open when sending from invoice room

[vincdargento]

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.7-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: #76595
Email or phone of affected tester (no customers): jsiodjosjdnisojso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• User has received an invoice.

1. Go to staging.new.expensify.com
2. Open FAB > Send invoice.
3. Enter amount > Next.
4. Enter merchant > Next.
5. Select user.
6. On confirm page, click Send invoice.
7. On invoice room, click + > Send invoice.
8. Enter amount > Next.

Expected Result:

Merchant field should appear/not appear consistently when sending invoice from FAB and invoice room.

Actual Result:

Merchant field appears when sending invoice from FAB (Step 4).
Merchant field does not appear when sending invoice from invoice room (Step 8).

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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.

[cead22]

@nkdengineer can you comment here so I can assign you please?