Skip to content

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

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions