Skip to content

[$250] Chat - Error message reappears after sending another message #44824

Closed

Description

@izarutskaya

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: v9.0.4-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: https://expensify.testrail.io/index.php?/tests/view/4693768
Email or phone of affected tester (no customers): vdargentotest+web070324@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Go to any chat.
  2. Send a corrupted PDF file (there is one attached to this report).
  3. Verify an error message appears.
  4. Dismiss the error message by clicking on the "x" icon.
  5. Send another message.
  6. Verify the error message that was already dismissed reappears.

Expected Result:

The error message should not reappear.

Actual Result:

The error message reappears after sending another message.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6532542_1720046830416.bandicam_2024-07-03_18-41-01-357.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0167c1b57ade6a9fb4
  • Upwork Job ID: 1810456336736930787
  • Last Price Increase: 2024-07-15
  • Automatic offers:
    • alitoshmatov | Reviewer | 103158918
    • nyomanjyotisa | Contributor | 103158919
Issue OwnerCurrent Issue Owner: @VictoriaExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 4, 2024
  2. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @VictoriaExpensify (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. izarutskaya commented on Jul 4, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #vip-vsb

  4. VictoriaExpensify commented on Jul 5, 2024

    @VictoriaExpensify
    Contributor

    I haven't had a chance to look at this, will come back to it on Monday

  5. nyomanjyotisa commented on Jul 7, 2024

    @nyomanjyotisa
    Member

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Error message reappears after sending another message

    What is the root cause of that problem?

    There is an error when uploading attachment:
    image

    This happens because we directly assigning the file object (which contains non-clonable properties) to attachmentInfo which we use on optimisticData

    This cause an error because we cannot store non-cloneable properties on IndexedDB

    This make the reportActions_ onyx data not stored on IndexedDB

    What changes do you think we should make in order to solve the problem?

    const attachmentInfo = file ?? {};

    Change this code to const attachmentInfo = file ? {...file} : {}; by this changes we create a shallow copy of the file object. This shallow copy contains only the properties of the file object, excluding any non-clonable properties

    RESULT

    New-Expensify.13.mp4

    What alternative solutions did you explore? (Optional)

  6. melvin-bot commented on Jul 8, 2024

    @melvin-bot

    @VictoriaExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 8, 2024
  8. melvin-bot commented on Jul 8, 2024

    @melvin-bot
  9. changed the title [-] Chat - Error message reappears after sending another message[/-] [+][$250] Chat - Error message reappears after sending another message[/+] on Jul 8, 2024
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 8, 2024
  11. melvin-bot commented on Jul 8, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

  12. 23 remaining items

  13. nyomanjyotisa commented on Jul 17, 2024

    @nyomanjyotisa
    Member
  14. nyomanjyotisa commented on Jul 23, 2024

    @nyomanjyotisa
    Member

    bump for PR review @alitoshmatov

  15. cead22 commented on Aug 6, 2024

    @cead22
    Contributor

    The PR was closed because the issue got fixed elsewhere. That said, contributors should still receive payement. @VictoriaExpensify can you handle that please?

  16. mallenexpensify commented on Aug 6, 2024

    @mallenexpensify
    Contributor

    @VictoriaExpensify both @nyomanjyotisa and @alitoshmatov are due compensation here. Per the internal SO

    If a contributor has been hired for a job and we decide to close the job before it is successfully completed, full payment is due for C+ and the contributor. One caveat here might be if the hired contributor wasn't working on their PR with urgency. If you're unsure, post in #bug-zero.

  17. melvin-bot commented on Aug 12, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @cead22, @VictoriaExpensify, @alitoshmatov, @nyomanjyotisa eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  18. ahmedGaber93 commented on Aug 19, 2024

    @ahmedGaber93
    Contributor

    We have the same issue after uploading workspace avatar here #47150. Is it should fix here? Asking because we have an accepted proposal here, but nothing there.
    @cead22 @alitoshmatov @nyomanjyotisa

  19. alitoshmatov commented on Aug 27, 2024

    @alitoshmatov
    Contributor

    It does look like both are similar, not sure if our solution would have solved this though. @nyomanjyotisa Can you look into #47150 issue

  20. ahmedGaber93 commented on Sep 2, 2024

    @ahmedGaber93
    Contributor
  21. alitoshmatov commented on Sep 3, 2024

    @alitoshmatov
    Contributor

    #47150 (comment) They decided to handle the issue there.

    Next step for this issue is to handle payment and close the issue

    cc: @VictoriaExpensify

  22. mallenexpensify commented on Sep 4, 2024

    @mallenexpensify
    Contributor

    @VictoriaExpensify plz pay both @alitoshmatov and @nyomanjyotisa since @nyomanjyotisa was hired and raised a PR, only for the bug to fixed magically (right?) Carlos commented here too

  23. VictoriaExpensify commented on Sep 11, 2024

    @VictoriaExpensify
    Contributor

    Payment Summary:
    Contributor: @nyomanjyotisa paid $250 via Upwork
    Contributor+: @alitoshmatov paid $250 via Upwork

    Upwork Job

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.ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions