Skip to content

Expense - Duplicate transaction threads with RBR in LHN when sending expense to each other #43252

Description

@izarutskaya

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: 1.4.80-9
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4601025
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition:

  • User A and B have no chatted before.
  • Both accounts must be new.
  1. Go to staging.new.expensify.com
  2. [User A] Go offline.
  3. [User A] Submit an expense to User B.
  4. [User B] Submit an expense with the same amount to User A.
  5. [User A] Go online.

Expected Result:

User A will not have two same transaction threads with RBR on LHN.

Actual Result:

User A receives two same transaction threads with RBR on LHN (not the main chat).

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6504507_1717721951733.20240607_085343.mp4

View all open jobs on GitHub

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Fields

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