[Pending / Scanning] Message containing a report says it is from the workspace name instead of the cardholder's name

[m-natarajan]

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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: @kevinksullivan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726081403491199

Action Performed:

1. Get assigned a >$0 limit on cardtest.expensify.com domain
2. Navigate to NewDot in your test account, and go to Settings > Wallet > Expensify Card > Reveal details (on virtual card)
3. Navigate to this paypal link and select “buy” on the first button on that screen, and use your virtual card details to make the purchase.
4. Check workspace chat

Expected Result:

Cardholder's name displayed in report

Actual Result:

Message containing a report says it is from the workspace name. Same issue observed for IOUs as well

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

View all open jobs on GitHub

[melvin-bot]

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

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[kevinksullivan]

Discussing broader expected behavior here

https://expensify.slack.com/archives/C036QM0SLJK/p1726064302069299

[grgia]

[grgia]

Pasting from slack:

Seems the issue might is from this line here, which is causing the second part of this line to always be true

 const isWorkspaceActor = isInvoiceReport || (ReportUtils.isPolicyExpenseChat(report) && (!actorAccountID || displayAllActors));

[grgia]

https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L7463-L7464

[grgia]

The actor account ID in onyx is correct, but we're using the wrong data here

[grgia]

https://www.figma.com/design/qQIIaxVUdtggrh8eg8bI5B/Brand-Guidelines-%26-Product-UI?node-id=10519-54496&t=lpYB1Q5Xz7YQzEYW-4

[grgia]

Question posted here

[miljakljajic]

I am heading out on parental leave - seems like this is being handled entirely internally, so I won't assign another BZ team member. @grgia stick someone else on it if I'm wrong!

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.