[Search v1] Tracked expenses show with _FAKE_ on the Search page

[trjExpensify]

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: v1.4.72-1
Reproducible in staging?: Y
Reproducible in production?:
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: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1715353965643159?thread_ts=1715336686.106629&cid=C036QM0SLJK

Action Performed:

1. Go to global create > Track expense
2. Track an expense to the selfDM
3. Go to avatar > Troubleshoot > New search page
4. Observe the tracked expense with the _Fake_ To/From fields in the table on the Search page

Expected Result:

The From: should be the account holder (i.e Tom James and the To: should be the name of the selfDM chat (i.e Tom James (You).

Actual Result:

FAKE to/from fields.

Workaround:

N/A

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01784dd4287018110a
• Upwork Job ID: 1788993640843829248
• Last Price Increase: 2024-05-10

Issue Owner

Current Issue Owner: @luacmartins

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01784dd4287018110a

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @fedirjh (Internal)

[trjExpensify]

@luacmartins is going to look at this later in the week.

[luacmartins]

Gonna work on this tonight!

[trjExpensify]

Gonna work on this tonight!

Why did yah move this into Hot Picks? 🤔

[luacmartins]

Just wanted to check that you're paying attention to these 😉 Jk jk I moved it by mistake along with the other issues when looking for volunteers.

[luacmartins]

Looking at this now

[trjExpensify]

Just wanted to check that you're paying attention to these 😉 Jk jk I moved it by mistake along with the other issues when looking for volunteers.

Hahah.. 4D chess, huh? Just you wait... 😂

[luacmartins]

PR in review.

[melvin-bot]

@trjExpensify, @luacmartins, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick!

[trjExpensify]

AuthPR deployed to prod. Is that it here or is there more to come?

[luacmartins]

That was the only PR needed for the track case. @trjExpensify could you test again and see if the issue is fixed or there are other __FAKE__ edge cases?

[trjExpensify]

Track is looking good!

[luacmartins]

We can close this issue then since it's all internal and PR is deployed