[$175] Chat - "Latest messages" pill remains visible after sending a message

Open
#106,015 25 comments 1 reaction 2 assignees View on GitHub

Maintainers usually reply within 1 day

@NicolasBonet is already working on this.

Since Nov 5, 2026.

Assessment

This issue has not been assessed yet.

Description

Bug Daily External

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.32-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://github.com/Expensify/App/pull/104242
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5.1 Safrai, iPhone 13 iOS 26.6
App Component: Chat Report View

Action Performed:

  1. Go to https://staging.new.expensify.com
  2. Open a chat from a deep link to an old message
  3. Send a message. Verify the list jumps to the newest messages and your message is visible.

Expected Result:

The "Latest messages" pill should disappear after sending a message and the chat jumps to the newest messages.

Actual Result:

"Latest messages" pill remains visible after sending a message and jumping to the newest messages

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

https://github.com/user-attachments/assets/68841592-06ec-4e66-9c6b-4fff83cf61f2

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7305231

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @NicolasBonet
Dominant language
TypeScript
Stars
5k
Forks
4k
Avg merge
3d 7h
Merged PRs (30d)
561

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Expensify/App

All issues in Expensify/App

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.