[HOLD #42214] Report/expenses don’t show in the workspace chat

[m-natarajan]

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.73-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @garrettmknight
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1715595596241419

Action Performed:

1. Launch the app and login as employee
2. Scan and submit an expense in workspace chat

Expected Result:

Expenses and report are visible in workspace and able to view the expenses in report chat

Actual Result:

The expenses and report aren’t visible in the workspace chat and when viewed the report thread via OldDot report history, the report chat only shows the total and not the expenses/receipts.

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

Expense.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Current assignee @puneetlath is eligible for the DeployBlockerCash assigner, not assigning anyone new.

[github-actions]

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

[Beamanator]

Asking if this is currently reproducible in prod, since this was reported in v1.4.72-1 in slack

[Beamanator]

@garrettmknight confirmed the bug exists in prod but not in staging (see slack) so this shouldn't be a deploy blocker

[melvin-bot]

@puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[JmillsExpensify]

Still experiencing this bug

[melvin-bot]

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

[puneetlath]

I haven't seen this lately. @JmillsExpensify you're still actively experiencing it?

[melvin-bot]

@puneetlath this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

@puneetlath Huh... This is 4 days overdue. Who can take care of this?

[puneetlath]

Asked here: https://expensify.slack.com/archives/C049HHMV9SM/p1717027756037069?thread_ts=1715595596.241419&cid=C049HHMV9SM

[puneetlath]

Unclear whether it is still happening. Waiting on more reports.

[puneetlath]

Seems to most likely be the same issue as #42214 so I'm going to put it on hold for that.

[puneetlath]

Still on hold.

[puneetlath]

This seems to be resolved. Going to close it out.