Skip to content

[Due for payment 2025-12-25] Expense - Error submitting expense after reselecting self DM on confirm page #77604

Closed

Description

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

Action Performed:

Precondition:

  • User has workspace chat and self DM.
  1. Go to staging.new.expensify.com
  2. Open FAB > Create expense > Manual.
  3. Enter amount > Next.
  4. On confirm page, click To field.
  5. Select self DM.
  6. On confirm page, click To field.
  7. Select self DM again.
    → On confirm page, Category and Reimbursable field disappear after reselecting self DM.
  8. Click Create expense.
    → Expense is created in another chat instead of self DM. Error shows up, expense is not created.

Expected Result:

In Step 7, on confirm page, Category and Reimbursable field will not disappear after reselecting self DM.
In Step 8, expense will be created in self DM.

Actual Result:

In Step 7, on confirm page, Category and Reimbursable field disappear after reselecting self DM.
In Step 8, expense is created in another chat instead of self DM. Error shows up, expense is not created.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7028365_1765588180491.16.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @johncschuster

Activity

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

    @melvin-bot

    Triggered auto assignment to @johncschuster (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 Dec 13, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 13, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 13, 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. dmkt9 commented on Dec 15, 2025

    @dmkt9
    Contributor

    This is from my PR #74964.
    I have submitted a PR to resolve this regression: #77648

  7. melvin-bot commented on Dec 15, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  8. 2 remaining items

  9. melvin-bot commented on Dec 15, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  10. MarioExpensify commented on Dec 15, 2025

    @MarioExpensify
    Contributor

    Offending PR was reverted.

  11. amyevans commented on Dec 15, 2025

    @amyevans
    Contributor

    Requested a retest from Applause here

  12. m-natarajan commented on Dec 15, 2025

    @m-natarajan

    Not repro, Mac 15.4.1 Safari, iPhone 13 iOS 18.6.2, Pixel 5 Android 14 v9.2.78-2

    Recording.1091.1.mp4
    ScreenRecording_12-15-2025.13-39-38_1.1.mp4
    screen-20251215-105302.1.mp4
  13. amyevans commented on Dec 15, 2025

    @amyevans
    Contributor

    Thank you!

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 18, 2025
  15. changed the title [-]Expense - Error submitting expense after reselecting self DM on confirm page[/-] [+][Due for payment 2025-12-25] Expense - Error submitting expense after reselecting self DM on confirm page[/+] on Dec 18, 2025
  16. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  17. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.81-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-12-25. 🎊

  18. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    @MarioExpensify @johncschuster The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions