Console error appears when pressing enter by not selecting suggested mention

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Open any chat
2. type @ and an email to get only one item on the suggestion list
3. Press the down key on your keyboard to deselect the item from the list
4. Press Enter

Expected Result

No error appears on the console

Actual Result

Uncaught TypeError: Cannot read properties of undefined (reading 'alternateText') Error appears on the console

Workaround:

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

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.14.8
Reproducible in staging?: y
Reproducible in production?: y
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

Screen.Recording.2023-05-15.at.10.29.08.PM.mov

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

View all open jobs on GitHub

[melvin-bot]

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

[mountiny]

cc @getusha @perunt

[perunt]

thanks for creating the issue, let see if @getusha will confirm the bug

[getusha]

The issue is not reproducible on that PR but the change

this.props.onFocusedIndexChanged(0);

is not fixing the issue removed it and still the same.

[sophiepintoraetz]

I'm not able to produce this bug on staging - despite pressing the down arrow, it's not deselecting.

[sophiepintoraetz]

Raised here but I don't think this can be reliably reproduced.

[sophiepintoraetz]

Okay, closing this one out - we can reopen if we are able to reproduce/it resurfaces.

[getusha]

Am i eligible for reporting bonus?

[mountiny]

@getusha usually if the bug was not reproducible and we havent fixed it intentionally then we dont pay for reporting.

[getusha]

@mountiny
Just commented here because i've seen some similar instances like this one #18217 (comment)

[mountiny]

Its case by case for sure, in this case we had lots of features quickly rolling out and some of the bugs had fixes up as the issues were reported as we knew about them. So its a thin line for sure but in general we pay out for a bug if the report has been what sparked the solution. In this case, the bug just disappeared with some change so even if you wouldnt report it, it would get fixed if that makes sense