You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Chat - The main IOU disappears from chat report even if there are threaded replies #56650
Version Number: 9.0.96-0 Reproducible in staging?: Yes Reproducible in production?: Yes Issue reported by: Applause Internal Team App Component: Money Requests
Action Performed:
Navigate to staging.new.expensify.com
Create an expense with an account
Go inside the expense report and send a comment
Reply in thread of the sent comment
Delete the IOU
Create another Manual Expense
Go back through the header subtitle
Navigate into the expense report by clicking on the report preview
Go back to the main chat by clicking on the header subtitle
Expected Result:
A deleted message appears since there are threaded replies and the amount on the header of the expense report on step 8 will show the correct amount not 0.0
Actual Result:
The IOU disappears from the main chat and no Deleted message comment appears. The amount on step 8 shows the correct one instead of 0.0
@anmurali 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!
Oh that is not the same issue, we are now completely deleting the report even if it has comments. The bug new bug is that the local DB still has the report, so when you go back you can still see it.
I guess we can update the optimistic data to delete all the data? @OlimpiaZurek
I couldn't reproduce this behavior (tested on v9.1.22-5). It seems that the report is cleared locally as expected. @IuliiaHerets If it's still reproducible on your end, could you please share the Onyx state? It would make debugging easier. Thanks!
If the issue is still reproducible, it might be better to create a new issue since the current one is focused on the reappearing IOU rather than it disappearing. Keeping this issue open could be confusing given the mismatch between the description and the actual problem.
Reacted by Joseph Kaufman, Rodrigo Lino da Costa and Pujan Shah
Activity
melvin-bot commentedon Feb 11, 2025
Triggered auto assignment to @anmurali (
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.melvin-bot commentedon Feb 14, 2025
@anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Feb 18, 2025
@anmurali 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Feb 20, 2025
@anmurali Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
melvin-bot commentedon Feb 24, 2025
@anmurali 12 days overdue now... This issue's end is nigh!
melvin-bot commentedon Feb 25, 2025
@anmurali 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!
53 remaining items
rlinoz commentedon Mar 24, 2025
Im not 100% sure, but I think we should be good, I will test it properly once it is deployed
joekaufmanexpensify commentedon Mar 24, 2025
Sweet, thank you!
rlinoz commentedon Mar 25, 2025
Yeah, this is not reproducible anymore 🎉
IuliiaHerets commentedon Apr 1, 2025
QA team can reproduce this issue in the latest build - v9.1.21-1. Reopen
20250401_123355.mp4
rlinoz commentedon Apr 1, 2025
Oh that is not the same issue, we are now completely deleting the report even if it has comments. The bug new bug is that the local DB still has the report, so when you go back you can still see it.
I guess we can update the optimistic data to delete all the data? @OlimpiaZurek
OlimpiaZurek commentedon Apr 2, 2025
Sounds likely, but I’ll check and confirm.
OlimpiaZurek commentedon Apr 2, 2025
I couldn't reproduce this behavior (tested on v9.1.22-5). It seems that the report is cleared locally as expected. @IuliiaHerets If it's still reproducible on your end, could you please share the Onyx state? It would make debugging easier. Thanks!
If the issue is still reproducible, it might be better to create a new issue since the current one is focused on the reappearing IOU rather than it disappearing. Keeping this issue open could be confusing given the mismatch between the description and the actual problem.
joekaufmanexpensify commentedon Apr 3, 2025
Yep, makes sense to me. Let's see if it can still be reproduced. If so, let's open a new issue as seems like a different bug.
joekaufmanexpensify commentedon Apr 4, 2025
@IuliiaHerets closing this for now. Please create a new issue if you can still reproduce this. Thank you!