-
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
Chat- Unexpected error when requesting money in Workspace chat #19035
Comments
Triggered auto assignment to @tjferriss ( |
Bug0 Triage Checklist (Main S/O)
|
@luacmartins Can you take a look at this? I believe it's happening because a workspace doesn't have an email... so what should happen here? |
@marcaaron is already addressing it here |
Talked here: https://expensify.slack.com/archives/C07J32337/p1684258261571739 NAB for the NewDot deploy. |
I'm not able to reproduce this issue on staging. I also see the related PR has been merged to production. So are we OK to close this or does it warrant further investigation? |
Pretty sure Marc got to this one. 👍 |
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 #18783
Action Performed:
Expected Result:
There is NO unexpected error when requesting money in Workspace chat
Actual Result:
Unexpected error when requesting money in Workspace chat
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.14.6
Reproducible in staging?: Yes
Reproducible in production?: No
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
Bug6057384_Recording__2442.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: