[HOLD for payment 2023-11-07] [$1000] Appropriate Message is not shown when inviting the secondary contact to members.

[kavimuru]

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. Create a Secondary contact for user A.
2. Open an account Using User B
3. Go to workspace then Members
4. Click the invite button.
5. Now, write the secondary contact of user A.
6. Click on Next and then Invite.
7. Notice that a message appears on the Members list page saying "Member not found. To invite a new member to the workspace, please use the Invite button above." This message should appear when searching for a member that is not in the list.

Expected Result:

The user is added to the policy members, and a success message appears indicating that it is a secondary contact

Actual Result:

The user is not added to the policy members, and a message saying "Member not found" appears.

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.32-5
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

Recording.5181.mp4

Member.Error-1.1.mp4

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0168b338ffdb8d8f7c
• Upwork Job ID: 1677000650172874752
• Last Price Increase: 2023-07-06

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

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

[johncschuster]

Expected Result:
A message appears indicating that it is a secondary contact

I'm not sure this is the expected result. If a user's secondary login email is invited to a workspace, I would think their account would be added as a workspace member and no prompt will be shown.

I'm buddy checking this in Slack

[johncschuster]

No response in #product. I'm going to cross-post the thread and bump it.

[johncschuster]

Meh, I think #product is the right room for this discussion. I've bumped the thread.

[melvin-bot]

@johncschuster Huh... This is 4 days overdue. Who can take care of this?

[johncschuster]

Ok, I've gotten no traction from the product room. I've just asked the bug reporter to clarify one part of the behavior.

Are you saying that the user has been successfully added to the policy members but the message says they have not been found?

[johncschuster]

Ok! I've clarified the Expected and Actual results section of the OP. Triaging!