Chat- Summited expenses disappear after sending the second expense
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v9.0.72-1 Reproducible in staging?: Yes Reproducible in production?: Yes Email or phone of affected tester (no customers): [email protected] Issue reported by: Applause Internal Team
Action Performed:
Prerequisite: Have two accounts logged in different devices or environments.
- Navigate to https://staging.new.expensify.com
- From a different environment or device, start a chat with user A.
- User B, create one expense and submit it to User A.
- Switch to user A account and verify that the expense is displayed correctly.
- Switch to user B account and send a second expense.
- Switch to user A again, and verify that now, the two expenses are displayed on chat
Expected Result:
The total amount in the preview component is reflective of the two expense requests combined
Actual Result:
The first expense was disappeared until navigating back to the chat to see the total amount
Workaround:
Unknown
Platforms:
- [x] Android: Standalone
- [x] Android: HybridApp
- [x] Android: mWeb Chrome
- [x] iOS: Standalone
- [x] iOS: HybridApp
- [ ] iOS: mWeb Safari
- [x] MacOS: Chrome / Safari
- [ ] MacOS: Desktop
Screenshots/Videos
https://github.com/user-attachments/assets/25484201-3912-4dff-afe0-3a29c334eb46
Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
Haven't been able to prioritize this, likely tomorrow.
@strepanier03 Eep! 4 days overdue now. Issues have feelings too...
Not reproducible.
@strepanier03 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
I'm also unable to repro this.
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
@strepanier03 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Issue not reproducible during KI retests. (First week)
Thank you @mvtglobally - If you can' repro next testing I'm going to close. I just tried again and still can't repro.
Issue not reproducible during KI retests. (Second week)
Okay, I'm going to close this out as non-reproducible. We can reopen in the future if we need.