Skip to content

[$250] Chat - The main IOU disappears from chat report even if there are threaded replies #56650

Closed

Description

@IuliiaHerets

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: 9.0.96-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Applause Internal Team
App Component: Money Requests

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Create an expense with an account
  3. Go inside the expense report and send a comment
  4. Reply in thread of the sent comment
  5. Delete the IOU
  6. Create another Manual Expense
  7. Go back through the header subtitle
  8. Navigate into the expense report by clicking on the report preview
  9. 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

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

https://github.com/user-attachments/assets/64933a1f-ec9b-4507-890c-93af1519239d
https://github.com/user-attachments/assets/de409ac5-7c51-4e96-b8d9-1167dbc6af0a

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021895202979936011985
  • Upwork Job ID: 1895202979936011985
  • Last Price Increase: 2025-02-27

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 11, 2025
  2. melvin-bot commented on Feb 11, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Feb 14, 2025

    @melvin-bot

    @anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  4. melvin-bot commented on Feb 18, 2025

    @melvin-bot

    @anmurali 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  5. melvin-bot commented on Feb 20, 2025

    @melvin-bot

    @anmurali Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  6. melvin-bot commented on Feb 24, 2025

    @melvin-bot

    @anmurali 12 days overdue now... This issue's end is nigh!

  7. melvin-bot commented on Feb 25, 2025

    @melvin-bot

    @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!

  8. removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 25, 2025
  9. removed their assignment
    on Feb 25, 2025
  10. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed on Feb 25, 2025
  11. 53 remaining items

  12. rlinoz commented on Mar 24, 2025

    @rlinoz
    Contributor

    Im not 100% sure, but I think we should be good, I will test it properly once it is deployed

  13. joekaufmanexpensify commented on Mar 24, 2025

    @joekaufmanexpensify
    Contributor

    Sweet, thank you!

  14. rlinoz commented on Mar 25, 2025

    @rlinoz
    Contributor

    Yeah, this is not reproducible anymore 🎉

  15. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Mar 25, 2025
  16. IuliiaHerets commented on Apr 1, 2025

    @IuliiaHerets
    Author

    QA team can reproduce this issue in the latest build - v9.1.21-1. Reopen

    20250401_123355.mp4
  17. rlinoz commented on Apr 1, 2025

    @rlinoz
    Contributor

    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

  18. OlimpiaZurek commented on Apr 2, 2025

    @OlimpiaZurek
    Contributor

    Sounds likely, but I’ll check and confirm.

  19. OlimpiaZurek commented on Apr 2, 2025

    @OlimpiaZurek
    Contributor

    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.

  20. joekaufmanexpensify commented on Apr 3, 2025

    @joekaufmanexpensify
    Contributor

    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.

  21. joekaufmanexpensify commented on Apr 4, 2025

    @joekaufmanexpensify
    Contributor

    @IuliiaHerets closing this for now. Please create a new issue if you can still reproduce this. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions