-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2023-06-29] Web - Group chat - "Invalid email" error message appears when creating a group DM with Concierge #21040
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @arosiclair ( |
https://github.com/Expensify/Web-Expensify/pull/37753 appears to be the root cause for this as well. We're passing empty string as the login for concierge because the client doesn't have it: FWIW, I'm not sure you're supposed to be able to make a group chat with concierge |
Looks like we DO want to be able to create group chats w/ concierge, but not some other expensify emails: #8586 |
as of right now now I'm unable to reproduce in |
Here's some logs from when I reproduced in
We somehow sent a completely empty email in |
So ya technically this is fixed for starting group chats w/ |
This is fixed by #21159, since you can't even start group chats with people if you don't have their logins now. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.29-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-06-28. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
removing blocker as this is fixed for group chats with concierge. if there is a new bug about group dms for different cases then lets spin up a new issue. |
I just tested a few different scenarios of creating group chats on staging and they all seemed to work. |
Let's close this out then? |
Agreed, no payment due here so we can close 👍 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.30-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-06-29. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Group is created successfully
Actual Result:
Invalid email error message appears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.29.0
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
Bug6098712_Recording__1023.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: