Thread - Expense preview does not show up in thread

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.80-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #42554

Action Performed:

Precondition:

• Submission frequency (Delayed submissions) is set to Manually on the workspace
• Workspace chat has no unsettled expense

1. Go to staging.new.expensify.com
2. Go to workspace chat
3. Create a manual expense
4. Go to transaction thread
5. Send a message
6. Right click on the message > Reply in thread

Expected Result:

Expense preview will appear in thread

Actual Result:

Expense preview does not appear in thread

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

Add any screenshot/video evidence

Bug6504186_1717694289507.20240607_011632.mp4

View all open jobs on GitHub

[melvin-bot]

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

[lanitochka17]

@joekaufmanexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[joekaufmanexpensify]

@lanitochka17 I think this is expected as of now. We fixed this bug here. but then that PR got reverted today, 30 minutes before you opened this issue.

Once we re-merge it, this should work again. If it does not, please re-open this issue and I will investigate further!