Web - Task - Console error when assining task to non-existent user with gmail

[lanitochka17]

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.4.22-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:

Issue found when executing PR #29730

Action Performed:

1. Go to https://staging.new.expensify.com/
   and log in
2. Click on FAB > Assign Task
3. Enter a title
4. Assign the task to a non-existent user with a Gmail account

Expected Result:

No console error is displayed after assigning a task

Actual Result:

The console error is displayed after the task is assigned to a non-existent user with Gmail account

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• Windows: Chrome
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6332659_1704412406263.Recording__86.mp4

View all open jobs on GitHub

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[lanitochka17]

Production:

Recording.90.mp4

[abzokhattab]

Seems to be a backend issue.

Also i cannot reproduce it on main

[marcaaron]

The console error is displayed after the task is assigned to a non-existent user with Gmail account

I'm not sure this is actually any problem. I've seen this happen from time to time. And it should not affect the feature we implemented in the PR that was tested.