Skip to content

[Due for payment 2025-10-15] [$250] Invoice - Unexpected error shown after send invoice #70004

Closed

Description

@jponikarchuk

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: v9.2.2-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: #68311
Email or phone of affected tester (no customers): ndk.2303+new170@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 Home/Chrome
App Component: Money Requests

Action Performed:

Preconditions: Submit 1 IOU to an account that you have not interacted with.

  1. Open https://staging.new.expensify.com/
  2. Create a new workspace
  3. Set the new workspace as default (if needed)
  4. Enable Invoice
  5. Click on FAB
  6. Click on Send Invoice
  7. Send an invoice to account from precondition

Expected Result:

User can send invoice to any account successully and can open the invoice report

Actual Result:

An unexpected error shown when send invoice.
Invoice is sent directly to 1:1 DM instead of Invoice report conversation

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021965159095854199023
  • Upwork Job ID: 1965159095854199023
  • Last Price Increase: 2025-09-24
  • Automatic offers:
    • dominictb | Reviewer | 108945077
    • gijoe0295 | Contributor | 108945082
Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 6, 2025
  2. melvin-bot commented on Sep 6, 2025

    @melvin-bot

    Triggered auto assignment to @kadiealexander (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 Sep 6, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 6, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 6, 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. marcaaron commented on Sep 8, 2025

    @marcaaron
    Contributor

    Seems we are getting 403 Invalid invoice receiver error. The param is sent receiverEmail: '' as empty string. Seems like a frontend issue to me.

  7. 44 remaining items

  8. kadiealexander commented on Oct 16, 2025

    @kadiealexander
    Contributor

    Reassigning as I'm OOO until the 29th.

  9. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 16, 2025
  10. melvin-bot commented on Oct 16, 2025

    @melvin-bot

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

  11. abekkala commented on Oct 16, 2025

    @abekkala
    Contributor

    @kadiealexander posting PAYMENT SUMMARY as I don't see one yet??

    PAYMENT SUMMARY FOR OCT 15

  12. abekkala commented on Oct 16, 2025

    @abekkala
    Contributor

    @gijoe0295 payment sent and contract ended - thank you! 🎉

  13. abekkala commented on Oct 17, 2025

    @abekkala
    Contributor

    @dominictb bumping this one (checklist) so I can issue payment and close this one out. thanks!

  14. dominictb commented on Oct 19, 2025

    @dominictb
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/54138/files#r2443285244

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

      NA. We already have regression tests for the invoice flow in TestRail.

  15. abekkala commented on Oct 20, 2025

    @abekkala
    Contributor

    @dominictb payment sent via Upwork and contracted closed - thanks! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions