[$250] After sending a custom subject line message via New Expensify, it shows up in sender's (Gmail) inbox and looks like sender and receiver are same

[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: @jamesdeanexpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726009677714319

Action Performed:

1. Send a custom subject line message

Expected Result:

Message and email sent to receiver

Actual Result:

After sending a custom subject line message via New Expensify, it shows up in sender's (Gmail) inbox and looks like sender and receiver are same

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021836887193135972228
• Upwork Job ID: 1836887193135972228
• Last Price Increase: 2024-09-26

Issue Owner

Current Issue Owner: @hungvu193

[melvin-bot]

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

[melvin-bot]

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

[JmillsExpensify]

Not sure if this is really a bug.

[trjExpensify]

I can repro this. I shouldn't receive an email for my own custom subject comment I send.

[JmillsExpensify]

Ah but isn't this simply because we are marking your own messages as unread for you? That's already being worked on.

[JmillsExpensify]

Basically what I mean is, isn't this the same fundamental issue we're seeing with all Guide/sales/product reach outs, which also use the header and are marked as unread and notify the user sending the message.

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)

[JmillsExpensify]

I chatted with Tom offline, and we agreed to get some feedback from the community on the root cause.

[melvin-bot]

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

[hungvu193]

No proposals yet, thought it's BE issue

[hungvu193]

I think it's BE issue, can you please add Internal label? @JmillsExpensify

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@JmillsExpensify @hungvu193 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

@JmillsExpensify, @hungvu193 Huh... This is 4 days overdue. Who can take care of this?

[JmillsExpensify]

Still waiting on internal

[melvin-bot]

@JmillsExpensify, @hungvu193 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

@JmillsExpensify, @hungvu193 10 days overdue. I'm getting more depressed than Marvin.

[JmillsExpensify]

Still waiting on internal.

[JmillsExpensify]

cc @jasperhuangg since you'll soon be touching this part of the codebase, in case you want to fix this at the same time.