-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD] [$250] Chat - "1 New message" badge does not display when user is on the older messages and a new message arrives #9437
Comments
Triggered auto assignment to @nkuoch ( |
Triggered auto assignment to @adelekennedy ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @marcochavezf ( |
@marcaaron @marcochavezf I don't remember exactly but we were closing any notification related issues right? |
Yep, thanks @rushatgabhane (not closing but they are on hold for now) |
We will look at open PRs when you are hired for a job. Guidelines here. |
Proposal
|
Issue is related to |
Please propose solutions to issues that have the |
Issue not reproducible during KI retests. (First week) |
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:
Expected Result:
"1new message" badge appears in account A
Actual Result:
No badge appears even if the user A is somewhere in the top of the messages
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: v1.1.76-5
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+ihchat4@applause.expensifail.com / Yulia1986Gerets
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5608305_Recording__794.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: