Skip to content

[HOLD for payment 2025-01-15] [$250] Notification displays the @expensify.sms domain in the title alongside the phone number. #53877

@m-natarajan

Description

@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: 9.0.73-6
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @jayeshmangwani
Slack conversation (hyperlinked to channel name): expensify_bugs

Action Performed:

  1. Log in with a phone number as User A.
  2. Log in with any other account as User B.
  3. Send a message from User A to User B.
  4. On User B's device, the notification includes [@expensify.sms](mailto:@expensify.sms)` along with the phone number.

Expected Result:

Notification should display only the sender's phone number.

Actual Result:

Notification includes both the @expensify.sms domain and the sender's phone number.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • 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/~021866600416959560133
  • Upwork Job ID: 1866600416959560133
  • Last Price Increase: 2024-12-10
  • Automatic offers:
    • truph01 | Contributor | 105376447
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @sakluger

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions