App: Message didn’t show up in #social as unread in LHN, but I got the email notification. ie. LHN is not updating from posts in #social til it's clicked on
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: Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: @JmillsExpensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704231385914329
Action Performed: (Updated by @mallenexpensify on Jan 17)
Precondition: must have access to #social channel in NewDot on the Expensify Chat workspace (hence why this needs to be internal, Matt A hasn’t been able to reproduce in other rooms)
- Have focus on a report that isn’t #social
- Have others post to #social or just wait 15 mins for chats to come in, which is usually pretty frequently
Expected Result:
New chats to show in LHN for the #social room
Actual Result:
New chat don’t show in LHN until the chat is clicked on, then chats load in the main #social report and LHN updates.
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
Add any screenshot/video evidence
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01059dcd731dd4aa05
- Upwork Job ID: 1747761033220931584
- Last Price Increase: 2024-01-17
About this issue
- Original URL
- State: closed
- Created 6 months ago
- Comments: 43 (37 by maintainers)
ooooh, i got a notification and #social updated in LHN. I unsure if it’s consistent though so will keep checking/testing
Confirming I have notifications set to immediately too
Apparently it is not fixing it completely. In my local testing of the PR, the command doesn’t crash anymore, but I still don’t get the pusher events. I haven’t investigated why the pusher events are still getting lost.
I think the bug makes you miss the message itself and the latest visible message in the LHN (both updates come from the pusher when someone sends a message).
Are you referring to “messages”? are you saying that they sent a message in social that failed to be posted?