[PAID] [$1000] Setting- Avatar displayed in grey color for a few seconds for a non-existing account when invite for new member

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #13216

Action Performed:

1. Navigate to staging.new.expensify.com
2. Log in with any account
3. Go to Setting - WS - Manage members
4. Tap Invite
5. Type non-existing member and tap Invite

Expected Result:

Avatar should not display in grey color for non-existing account when invite for new member

Actual Result:

Avatar displayed in grey color for a few seconds for non-existing account when invite for new member before it resolves to color

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

Reproducible in staging?: Yes

Reproducible in production?: Yes

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-02-20.at.12.31.44.PM.mov

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01a75090f4d2b9c69e
• Upwork Job ID: 1627768504771768320
• Last Price Increase: 2023-02-20

[melvin-bot]

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

[MelvinBot]

@anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[MelvinBot]

@anmurali Whoops! This issue is 2 days overdue. Let's get this updated quick!

[MelvinBot]

@anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!