-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Retest] Notification - Duplicated notification received with numbers instead sender name #40943
Comments
Triggered auto assignment to @strepanier03 ( |
I don't have any iOS devices to test this with, looking for a hand to do so. |
@strepanier03 Huh... This is 4 days overdue. Who can take care of this? |
@strepanier03 Still overdue 6 days?! Let's take care of this! |
Still need to test this, my bad. Been underwater with other tasks and bugs that stop a customer/us from using newdot. |
I was able to test this, but one of my devices is virtual with browser stack, I couldn't repro though. Asking for a restest because I might need two physical devices. |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@strepanier03 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Issue not reproducible during KI retests. (First week) |
@strepanier03 Huh... This is 4 days overdue. Who can take care of this? |
@strepanier03 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Thank you for the update, will continue to monitor. |
@strepanier03 Eep! 4 days overdue now. Issues have feelings too... |
In retesting still. |
Issue not reproducible during KI retests. (Second week) |
@strepanier03 Eep! 4 days overdue now. Issues have feelings too... |
Thank you @mvtglobally - I appreciate the retesting. |
Issue not reproducible during KI retests. (Third week) Good to close? |
Issue not reproducible during KI retests. (Fourth week) |
@strepanier03 Still overdue 6 days?! Let's take care of this! |
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: 1.4.65-4
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/4509328&group_by=cases:section_id&group_order=asc&group_id=295000
Email or phone of affected tester (no customers): applausetester+omq1@applause.expensifail.com
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The user should receive notifications with correct information
Actual Result:
User received two notifications when one message was sent. The duplicated notification displayed numbers instead of the sender's name
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460642_1713985508069.RPReplay_Final1713985451.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: