-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web - Task - Console error when assining task to non-existent user with gmail #33989
Comments
👋 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:
|
Triggered auto assignment to @marcaaron ( |
Production: Recording.90.mp4 |
Seems to be a backend issue. Also i cannot reproduce it on main |
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. |
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:
and log in
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?
Screenshots/Videos
Add any screenshot/video evidence
Bug6332659_1704412406263.Recording__86.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: