Skip to content

Invoices - Missing Merchant and Date field in invoice confirmation page with new accounts #61636

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: 9.1.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): shdinuhsiuudishidh@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with a new Gmail account.
  • Workspace has invoicing feature.
  1. Go to staging.new.expensify.com
  2. Open FAB > Send invoice.
  3. Enter amount > Next.
  4. Select a user.

Expected Result:

On the confirmation page, Merchant and Date field are shown.

Actual Result:

On the confirmation page, Merchant and Date field are missing.

This issue only happens with new accounts.

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

Bug6825042_1746667494999.20250508_091556.mp4

View all open jobs on GitHub

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 May 8, 2025
  2. melvin-bot commented on May 8, 2025

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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 May 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  5. github-actions commented on May 8, 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. jliexpensify commented on May 8, 2025

    @jliexpensify
    Contributor

    Probably not a deploy blocker right @robertjchen?

  7. robertjchen commented on May 8, 2025

    @robertjchen
    Contributor

    not a blocker per se, but should be addressed

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 8, 2025
  9. linhvovan29546 commented on May 8, 2025

    @linhvovan29546
    Contributor

    I think this is a regression from #60940

  10. robertjchen commented on May 8, 2025

    @robertjchen
    Contributor

    cc: @ishakakkad @getusha could we confirm if that is the case? 🙏

  11. ishakakkad commented on May 8, 2025

    @ishakakkad
    Contributor

    @robertjchen I will check it out and let you know.

  12. ishakakkad commented on May 8, 2025

    @ishakakkad
    Contributor

    @robertjchen after reverting changes issue is resolved, so looks like this issue due to #60940. But I need to investigate why this issue is only occurred only the case where user create new user.

  13. ishakakkad commented on May 8, 2025

    @ishakakkad
    Contributor

    Changes are reverted #61695 so issue should be fixed now after new deployment

  14. melvin-bot commented on May 13, 2025

    @melvin-bot

    @robertjchen, @jliexpensify Eep! 4 days overdue now. Issues have feelings too...

  15. robertjchen commented on May 13, 2025

    @robertjchen
    Contributor

    Closing in favor of #61637

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions