-
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
CRITICAL: [Actionable Whisper] [$250] Submit tracked expense to user you do not have an existing chat with fails #41181
Comments
Triggered auto assignment to @jliexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~01b61241ab3673e9f6 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
Upwork job price has been updated to $500 |
When I test this, I see that after signing out and signing back in the chat and the IOU does exist. It crashes the first time I try to open the IOU, but after refresh it works fine. Additionally, this only seems to happen for new users / users we do not have existing chats for - so My current theory is that we're missing some pusher updates on the creation on the chat report / there is a mismatch of an optimistic ID and what something is created with. Opening up externally to see if there's maybe another issue that I'm not seeing here |
We'll also need to start passing an email down via the ConvertTrackedExpenseToRequest command so we can create the account if it doesn't exist |
Upon closer inspection, I think this is related to the lack of personal details when we're chatting with someone we don't have the details for yet |
ProposalPlease re-state the problem that we are trying to solve in this issue.After using Actionable Whisper to "Submit it [a tracked expense] to someone"... In chat report:
In IOU report:
What is the root cause of that problem?The work that would usually be done by an OpenReport API write is not done when ConvertTrackedExpenseToRequest creates a new chat. What changes do you think we should make in order to solve the problem?Make the ConvertTrackedExpenseToRequest mutation also submit data to create the chat like OpenReport does. Ensure optimistic and server get all the right data. |
There is a problem only solvable on the server-side. Problem Solution |
@eVoloshchak, @thienlnam, @jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Hi @thienlnam, based on this comment - should we make this |
Yes this should be internal, I've fixed the flow for users that don't exist yet - now I just need to fix the IOU getting removed |
Current assignee @eVoloshchak is eligible for the Internal assigner, not assigning anyone new. |
Issue not reproducible during KI retests. (First week) |
@eVoloshchak, @thienlnam, @jliexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Still working on the IOU disappearing |
@eVoloshchak, @thienlnam, @jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@eVoloshchak, @thienlnam, @jliexpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
We're good here! |
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: v1.4.67-0
Reproducible in staging?: Y
Reproducible in production?: Y
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:
Slack conversation:
Action Performed:
Expected Result:
Describe what you think should've happened
The flow should work as expected, you should see the IOU in the chat between you, and be able to modify it normally
Actual Result:
Describe what actually happened
The chat disappears, and the request is flashing
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Start a chat with the user first, before performing the steps
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Failure case:
Screen.Recording.2024-04-28.at.3.37.59.PM.mov
Success case with existing chat:
Screen.Recording.2024-04-28.at.3.38.39.PM.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: