Skip to content

[Due for payment 2025-10-30] Expense sent from self DM to workspace chat disappears from both chats #72536

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: v9.2.30-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72179
Email or phone of affected tester (no customers): applausetester+dp345@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Sequoia 15.6 / Safari
App Component: Other

Action Performed:

Precondition:
Create and Log in with Expensifail account.
Account has self DM.

  1. Create a workspace
  2. Go to workspace chat
  3. Create an expense
  4. Go to self DM
  5. Create a scan expense in self DM
  6. Click Submit it to someone
  7. Select workspace chat
  8. Click Create expense
  9. Open the expense report
  10. Open any expense row
  11. Click Report field. Verify no new report is created after submitting scan expense from self DM to workspace chat
  12. Go to a different report and then back to workspace report

Expected Result:

No new report is created.
The scanned expense from self DM appears as a second row in the existing expense report in workspace chat and remains visible.

Actual Result:

No new report is created, but after some time, expense originally from DM disappears both from the workspace chat and self DM.
The expense remains listed under Reports \ Expenses, indicating it belongs to the workspace report — however, when the report is opened, only the one original expense is displayed there.

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

Bug6974198_1760417907092.9_42_PM_2025-10-13.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @heyjennahay

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 14, 2025
  2. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    Triggered auto assignment to @heyjennahay (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. mountiny commented on Oct 14, 2025

    @mountiny
    Contributor

    cc @thelullabyy @chuckdries @truph01 this was found during testing #72179 can you take a look if this is related/ enabled by your PR and follow up accordingly? Thanks!

  4. truph01 commented on Oct 14, 2025

    @truph01
    Contributor

    @thelullabyy, Please help check if it is related to our PR

  5. chuckdries commented on Oct 14, 2025

    @chuckdries
    Contributor

    Doesn't seem related to that PR. The expense is moved to the correct report initially, then gets moved (sort of - it claims it's still in the workspace report, but shows up in the wrong chat) after a few moments. Seems like a concierge autocategorization or smartscan bug.

  6. chuckdries commented on Oct 14, 2025

    @chuckdries
    Contributor

    It also happens when you manually categorize a manual expense 🤔. I'll dig a little deeper

  7. chuckdries commented on Oct 14, 2025

    @chuckdries
    Contributor

    I think this is actually caused by https://github.com/Expensify/Expensify/issues/555351 whenever you use the "Submit it to someone" button

  8. chuckdries commented on Oct 16, 2025

    @chuckdries
    Contributor

    I'm continuing to look into this. Nothing to report so far

  9. chuckdries commented on Oct 17, 2025

    @chuckdries
    Contributor

    I think I have a fix that works, but I think I'm missing something because it seems like it's been broken for a long time. @mitarachim do you have any way to tell when was the last time someone saw this flow work successfully?

  10. truph01 commented on Oct 18, 2025

    @truph01
    Contributor

    @chuckdries From my side, in step 8 - Click Create expense, it calls AddTrackedExpenseToPolicy API and this API returns an error:

    "400 Unique Constraints Violation"

  11. chuckdries commented on Oct 20, 2025

    @chuckdries
    Contributor

    Yeah, looks like we're sending an existing reportActionID as moneyRequestPreviewReportActionID rather than generating a new one like we're supposed to. This behavior was introduced by this change: https://github.com/Expensify/App/pull/63738/files#diff-577fcc5f3a5e4930916ff310e61c38edfa093792fe3ab55b9a30d2aecd8811dbR6639

  12. 19 remaining items

  13. truph01 commented on Nov 7, 2025

    @truph01
    Contributor

    Reviewer: @truph01 owed $250 via NewDot

    @heyjennahay I'm not eligible for NewDot payment yet.

  14. melvin-bot commented on Nov 12, 2025

    @melvin-bot

    @truph01 Eep! 4 days overdue now. Issues have feelings too...

  15. melvin-bot commented on Nov 14, 2025

    @melvin-bot

    @truph01 Still overdue 6 days?! Let's take care of this!

  16. chuckdries commented on Nov 24, 2025

    @chuckdries
    Contributor

    @heyjennahay sounds like we need to pay @truph01 some other way

  17. heyjennahay commented on Nov 26, 2025

    @heyjennahay
    Contributor

    @truph01 can you please share your Upwork link so I can send you an offer?

  18. heyjennahay commented on Dec 1, 2025

    @heyjennahay
    Contributor

    Upwork contractor link for my ref truph01

  19. heyjennahay commented on Dec 1, 2025

    @heyjennahay
    Contributor

    @truph01 can you please accept this Upwork offer so I can pay you? https://www.upwork.com/nx/wm/offer/109664264

  20. truph01 commented on Dec 2, 2025

    @truph01
    Contributor

    @heyjennahay I've accepted it. Thanks

  21. heyjennahay commented on Dec 3, 2025

    @heyjennahay
    Contributor

    Great thanks!

    I have paid @truph01 $250 via Upwork and closed the contract. Thanks everyone for your work on this ❤️

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions