[$500] [HOLD for payment 2023-11-09] Error thrown when left and right arrow keys pressed

[rlinoz]

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: 1.3.93-0
Reproducible in staging?: Yes
Reproducible in production?: No
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: @situchan
Slack conversation:

Action Performed:

Break down in numbered steps

1. Go to a conversation in ND
2. Open the web console
3. Type a few things
4. Move the cursor using the arrow keys (left and right)

Expected Result:

The console should have no errors associated with using the arrow keys

Actual Result:

The error Uncaught TypeError: Cannot convert undefined or null to object appears.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Yes

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

Details

279105210-d461436a-c31d-4961-8306-0a89e400e319.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01cd1222fab2da90a5
• Upwork Job ID: 1722643867637014528
• Last Price Increase: 2023-11-09

[melvin-bot]

Triggered auto assignment to @zanyrenney (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[rlinoz]

Hey @zanyrenney I will be working on this

[situchan]

Happy to review as C+ if needed

[rlinoz]

That would be great

[situchan]

@rlinoz thanks. Can you please assign me to the issue so that correct C+ is assigned as reviewer in PR?

[NikkiWines]

Adding the deploy blocker label since this is currently on staging only