Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chat – Unable to open any + menu option using Up keys and Enter, when open it first time #40399

Closed
1 of 6 tasks
izarutskaya opened this issue Apr 18, 2024 · 12 comments
Closed
1 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering Hourly KSv2 Reviewing Has a PR in review

Comments

@izarutskaya
Copy link

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: v1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+jp_e_category@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Log in.
  3. Navigate to any chat
  4. Click on + button
  5. Navigate via + menu using Up/Down keys and press Enter

Expected Result:

Chosen menu opens

Actual Result:

Nothing happens, unable to open + menu option using Up keys and Enter, when open it first time

Workaround:

Unknown

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

Bug6453289_1713425271864.Key_menu.mp4

View all open jobs on GitHub

@izarutskaya izarutskaya added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Apr 18, 2024
Copy link

melvin-bot bot commented Apr 18, 2024

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

Copy link

melvin-bot bot commented Apr 18, 2024

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

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Apr 18, 2024
Copy link
Contributor

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

@izarutskaya
Copy link
Author

@kadiealexander I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

@izarutskaya
Copy link
Author

We think this issue might be related to the #vip-vsb.

@izarutskaya
Copy link
Author

Production

bandicam.2024-04-18.10-38-52-779.mp4

@NikkiWines
Copy link
Contributor

NikkiWines commented Apr 18, 2024

Interesting, (h/t to @sonialiap for identifying this) this works the second time you press Enter but not the first, and if you navigate to another option (e.g. press enter the first time for splitting a bill, the second for editing a task) it will remember your first selection, not your second (splitting a bill). Definitely a bug 🐛

Screen.Recording.2024-04-18.at.10.26.16.mov

@shahinyan11
Copy link

shahinyan11 commented Apr 18, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

Chat – Unable to open any + menu option using Up keys and Enter, when open it first time

What is the root cause of that problem?

Here we call the onItemSelected function before setting the value of selectedItemIndex.current

What changes do you think we should make in order to solve the problem?

Here move the selectedItemIndex.current = index code above the onItemSelected function call

selectedItemIndex.current = index;
onItemSelected(selectedItem, index);

What alternative solutions did you explore? (Optional)

@NikkiWines
Copy link
Contributor

Looks like it might be a result of #39201 cc: @roryabraham @WojtekBoman

@WojtekBoman
Copy link
Contributor

I'll prepare a fix for that :)

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Hourly KSv2 labels Apr 18, 2024
@roryabraham roryabraham self-assigned this Apr 18, 2024
@roryabraham roryabraham added Hourly KSv2 and removed Weekly KSv2 labels Apr 18, 2024
@roryabraham
Copy link
Contributor

thanks for identifying the PR that caused this @NikkiWines 🙇🏼

@roryabraham
Copy link
Contributor

verified this is fixed on staging, no payments due, closing it out

@roryabraham roryabraham removed the DeployBlockerCash This issue or pull request should block deployment label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering Hourly KSv2 Reviewing Has a PR in review
Projects
None yet
Development

No branches or pull requests

6 participants