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
[HOLD #8267] Web - Read messages are marked unread after a while #3981
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.
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.
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?
@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
- Do you have an estimate of how much time it passes from reading the
message to the unread status?
For me, it seems to happen more often when I go to the e.cash tab, sit for
1-2 seconds (and read the most recent message), then go to another tab
quickly. I suspect this is the cause of the issue.
- 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?
There should only be one tab open when it's happened to me. I very rarely
use mobile and web at the same time, so I don't think this would be the
cause of it.
- Does this happen with the same chat each time or are several chats
affected?
It's always one chat affected at a time, but not always the same chat, no.
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
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?
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.
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
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.
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?
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
Activity
MelvinBot commentedon Jul 12, 2021
Triggered auto assignment to @thienlnam (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.MelvinBot commentedon Jul 12, 2021
Triggered auto assignment to @jboniface (
External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.jboniface commentedon Jul 12, 2021
Since this hasn't been reproduced, I am hesitant to post the job
isagoico commentedon Jul 12, 2021
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:
cead22 commentedon Jul 12, 2021
@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
tgolen commentedon Jul 12, 2021
iwiznia commentedon Jul 13, 2021
It varies, I don't think the time is a determining factor here.
Nope
Same as Tim, only one at a time, but not the same one each time
Already did, this is not it. If it was, then the unread would not go away when I re-read the chat
isagoico commentedon Jul 13, 2021
Thanks for the extra info! 🙇 No luck yet on being able to repro the issue yet. Will update if I find something.
141 remaining items
mallenexpensify commentedon Feb 22, 2022
@johnmlee101 can you go ahead and do this plz
mallenexpensify commentedon Mar 21, 2022
@johnmlee101 can you please help with the above and split the assignments into two parts?
johnmlee101 commentedon Mar 22, 2022
Sorry, just saw this update now! On it
johnmlee101 commentedon Mar 22, 2022
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.
[-]Web - Read messages are marked unread after a while[/-][+][HOLD #8267] Web - Read messages are marked unread after a while[/+]mallenexpensify commentedon Mar 25, 2022
Put on hold pending #8267 (internal), updated title, removed
Help Wantedlabel (don't forget to add back when take off hold)johnmlee101 commentedon Mar 31, 2022
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.
mallenexpensify commentedon May 4, 2022
From @stitesExpensify 8 days ago
Should we take off hold? And/or, is this related to Offline First?
stitesExpensify commentedon May 4, 2022
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?
mallenexpensify commentedon May 4, 2022
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
iwiznia commentedon May 5, 2022
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