App: [BONUS PAYMENT] [$1000] Not able to invite an email when it's a substring of the selected email

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. Go to Settings => Workspaces => Select a Workspace => Members => Invite new members
  2. Search an email [abcde@gmail.com](mailto:%60abcde@gmail.com) and select it
  3. Then search another email [bcde@gmail.com](mailto:%60bcde@gmail.com) which is a substring of the selected email

Expected Result:

We should be able to search the second email [bcde@gmail.com](mailto:%60bcde@gmail.com) and select it after selecting the first email

Actual Result:

We can’t search for the second email [bcde@gmail.com](mailto:%60bcde@gmail.com) after selecting the first email

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.31-3 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

https://github.com/Expensify/App/assets/93399543/67b9411f-593b-4da7-a5b3-7e5da9627133

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~012c7b7da0a7c6f9b3
  • Upwork Job ID: 1674592628144259072
  • Last Price Increase: 2023-06-30

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 33 (20 by maintainers)

Most upvoted comments

Paid, thanks!

BZ checklist:

The PR that introduced the bug has been identified. Link to the PR: The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

https://github.com/Expensify/App/pull/7986#issuecomment-1646589116

Determine if we should create a regression test for this bug. If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

No. Edge case issue. So wouldn’t be beneficial to create a test case for the same.

@deetergp Pending on your approval.