App: [HOLD #8503][$1000] Desktop - Chat Switcher is slow and doesn't recognize keystrokes

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Type a message in a chat
  2. Type command+k to open chat switcher
  3. Immediately start typing the name of a person you already have chats with

Expected Result:

The characters you type show up in search

Actual Result:

Many characters are missed. ie. I typed lauren quickly and only the n showed.

Workaround:

Unknown

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.73.0 Reproducible in staging?: n/a Reproducible in production?: n/a 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 Notes/Photos/Videos: Any additional supporting documentation

n/a

Expensify/Expensify Issue URL: Issue reported by: @mallenexpensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695286362554219

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~011dba4ca10589e48c
  • Upwork Job ID: 1707643423922569216
  • Last Price Increase: 2023-10-17

About this issue

  • Original URL
  • State: open
  • Created 9 months ago
  • Comments: 103 (82 by maintainers)

Most upvoted comments

I am going to be OOO soon. I will keep assigned here as held on Fabric update but if this requires C+ attention, please reassign.

Sorry @0xmiroslav , was testing auto-assigner automation

I’m going to assign to myself, remove others and make it a monthly. Then, drop into an ideal nav room when the time is right, to insure it’s being considered. Thx @mountiny and @cubuspl42

Summing up: we know that reducing the ANIMATED_TRANSITION used to help with our bug. After the optimization (https://github.com/Expensify/App/issues/30261), maybe reducing it less will make things right here?

At the same time, I’m aware that even touching ANIMATED_TRANSITION is somewhat risky, as we rely on it in many places. This makes our issue tricky.

I’m bumping this to weekly for now, since there’s a discussion going on.

@studentofcoding You can update your proposal, as stated in the contributing guidelines.

Posted again to try to get 👀 cuz I’d love to see this bug fixed, I run into it a dozen or more times a day. https://expensify.slack.com/archives/C05LX9D6E07/p1696870380595049?thread_ts=1696418872.247919&cid=C05LX9D6E07