[$250] Android - Notifications - No notifications received for messages on 1:1 conversation.

[jponikarchuk]

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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-134/folder/12015334/39318180/797465896
Email or phone of affected tester (no customers): ibellicotest+1388@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 10 / Chrome
App Component: Notifications

Action Performed:

Prerequisite: Have two accounts opened on two different devices or environments.

1. Open the Expensify app.
2. Log in as User A.
3. On another account, as User B, create a chat with User A.
4. Send some messages to the chat.
5. As User A, note that no notification is displayed when new messages are received.

Expected Result:

When receiving new messages on an individual chat, a notification should be automatically displayed.

Actual Result:

No notification is received, when new messages are received in an individual chat.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021947717723760350194
• Upwork Job ID: 1947717723760350194
• Last Price Increase: 2025-07-22

[melvin-bot]

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

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

[melvin-bot]

Triggered auto assignment to @inimaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[inimaga]

Perhaps caused by #66179 as the only PR that touched notifications? cc: @arosiclair @allgandalf @MarioExpensify