Skip to content

[HOLD #8267] Web - Read messages are marked unread after a while #3981

Closed

Description

@isagoico

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Open an unread chat
  2. Navigate to other chats and use the app for a little while

Expected Result:

Unread chat should stay marked as unread.

Actual Result:

The chat that was opened earlier is marked as unread. Explained by @iwiznia:

I can't reliably reproduce this, but happens several times a day in web. I get a new message, I read it, come back later and the message is back to unread.

Workaround:

None needed. It's just confusing to the user to see a chat marked as unread when it was opened before.

Platform:

Where is this issue occurring?

Web ✔️
iOS
Android
Desktop App ✔️
Mobile Web

Version Number: 1.0.77-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

I haven't been able to reproduce this yet on my side. Will update here if I find any more information about this.

Expensify/Expensify Issue URL:

View all open jobs on Upwork


From @iwiznia https://expensify.slack.com/archives/C01GTK53T8Q/p1626078601100700

I can't reliably reproduce this, but happens several times a day in web. I get a new message, I read it, come back later and the message is back to unread.

Activity

  1. MelvinBot commented on Jul 12, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 12, 2021
  3. MelvinBot commented on Jul 12, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @jboniface (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  4. jboniface commented on Jul 12, 2021

    @jboniface

    Since this hasn't been reproduced, I am hesitant to post the job

  5. removed their assignment
    on Jul 12, 2021
  6. isagoico commented on Jul 12, 2021

    @isagoico
    Author

    Looks like @tgolen @stitesExpensify and @cead22 were able to reproduce this issue too 🤔 @iwiznia I know this is a long shot but I have some questions that could help me get solid repro steps:

    • Do you have an estimate of how much time it passes from reading the message to the unread status?
    • Are there other tabs opened with e.cash active? Or other devices logged in with the same account that were being used at the same time?
    • Does this happen with the same chat each time or are several chats affected?
  7. cead22 commented on Jul 12, 2021

    @cead22
    Contributor

    @iwiznia also check that you don't have policy rooms with unread messages (eg, #announce) -- Cole let me know recently that this could be another cause of 3.cash showing the unread indicator

  8. tgolen commented on Jul 12, 2021

    @tgolen
    Contributor
  9. iwiznia commented on Jul 13, 2021

    @iwiznia
    Contributor

    Do you have an estimate of how much time it passes from reading the message to the unread status?

    It varies, I don't think the time is a determining factor here.

    Are there other tabs opened with e.cash active? Or other devices logged in with the same account that were being used at the same time?

    Nope

    Does this happen with the same chat each time or are several chats affected?

    Same as Tim, only one at a time, but not the same one each time

    @iwiznia also check that you don't have policy rooms with unread messages (eg, #announce) -- Cole let me know recently that this could be another cause of 3.cash showing the unread indicator

    Already did, this is not it. If it was, then the unread would not go away when I re-read the chat

  10. isagoico commented on Jul 13, 2021

    @isagoico
    Author

    Thanks for the extra info! 🙇 No luck yet on being able to repro the issue yet. Will update if I find something.

  11. 141 remaining items

  12. mallenexpensify commented on Feb 22, 2022

    @mallenexpensify
    Contributor

    Should I go ahead and split these assignments into two parts? One for the front-end changes in this repo and one for the back-end internal development?

    @johnmlee101 can you go ahead and do this plz

  13. mallenexpensify commented on Mar 21, 2022

    @mallenexpensify
    Contributor

    @johnmlee101 can you please help with the above and split the assignments into two parts?

  14. johnmlee101 commented on Mar 22, 2022

    @johnmlee101
    Contributor

    Sorry, just saw this update now! On it

  15. johnmlee101 commented on Mar 22, 2022

    @johnmlee101
    Contributor

    This issue is responsible for adding the two API end points needed.
    #8267

    Once those endpoints exist, then we'll go ahead and come back to this issue to make sure we're properly using the new API endpoint to update the read/unread markers (which can be done externally). This step will be combined with the deprecation of the API command and we'll revisit once things are all moved over.

  16. changed the title [-]Web - Read messages are marked unread after a while[/-] [+][HOLD #8267] Web - Read messages are marked unread after a while[/+] on Mar 25, 2022
  17. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 25, 2022
  18. mallenexpensify commented on Mar 25, 2022

    @mallenexpensify
    Contributor

    Put on hold pending #8267 (internal), updated title, removed Help Wanted label (don't forget to add back when take off hold)

  19. johnmlee101 commented on Mar 31, 2022

    @johnmlee101
    Contributor

    I will be keeping this on hold as we'll be pursuing a potential high-level refactor of this logic to simplify and inevitably fix these issues as put through our proposal process.

  20. mallenexpensify commented on May 4, 2022

    @mallenexpensify
    Contributor

    From @stitesExpensify 8 days ago

    Web PR is on prod, unsure why it didn't get posted here, but that means this is done!

    Should we take off hold? And/or, is this related to Offline First?

  21. stitesExpensify commented on May 4, 2022

    @stitesExpensify
    Contributor

    I think that this issue might be fixed? My PR made it so that we can never set the lastRead backwards unless manually done by the user, that should fix this issue right?

  22. mallenexpensify commented on May 4, 2022

    @mallenexpensify
    Contributor

    Since it doesn't sound like it's easy to reliably reproduce, it's hard to test. @iwiznia any idea of this has happened to you the past week?!?! If not, I'm down to close this then reopen if/when needed

  23. iwiznia commented on May 5, 2022

    @iwiznia
    Contributor

    I don't know, since the unread message indicator is totally broken for me right now. Let's close, since Marc is revamping all this soon anyway

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions