Repository navigation
Web - Task - Console error when assining task to non-existent user with gmail #33989
Description
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:
- Go to https://staging.new.expensify.com/
and log in - Click on FAB > Assign Task
- Enter a title
- 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
Activity
github-actions commentedon Jan 5, 2024
👋 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:
melvin-bot commentedon Jan 5, 2024
Triggered auto assignment to @marcaaron (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.lanitochka17 commentedon Jan 5, 2024
Production:
Recording.90.mp4
abzokhattab commentedon Jan 5, 2024
Seems to be a backend issue.
Also i cannot reproduce it on main
marcaaron commentedon Jan 5, 2024
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.