-
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
[$500] Android - Notifications - Notifications not cleared after opening chat #33454
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01fc6f6adb93b4c53b |
Triggered auto assignment to @kevinksullivan ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
If the issue is specific to a particular app, clearing its cache may help. Go to your device settings, find the app in question, and clear its cache. |
📣 @LekeMarkaj! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@kevinksullivan, @sobitneupane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@kevinksullivan, @sobitneupane Huh... This is 4 days overdue. Who can take care of this? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@kevinksullivan, @sobitneupane Still overdue 6 days?! Let's take care of this! |
@kevinksullivan, @sobitneupane 10 days overdue. Is anyone even seeing these? Hello? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@kevinksullivan @sobitneupane this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@kevinksullivan, @sobitneupane 12 days overdue now... This issue's end is nigh! |
This issue has not been updated in over 14 days. @kevinksullivan, @sobitneupane eroding to Weekly issue. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@kevinksullivan @sobitneupane this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@kevinksullivan, @sobitneupane Eep! 4 days overdue now. Issues have feelings too... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@kevinksullivan @sobitneupane this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Current assignee @sobitneupane is eligible for the Internal assigner, not assigning anyone new. |
@kevinksullivan, @sobitneupane Still overdue 6 days?! Let's take care of this! |
@kevinksullivan Is this still reproducible? I don't have android device with me now, so I won't be able to test it. |
@lanitochka17 are you able to reproduce this? |
Issue is still reproducible on IOS screen-20240125-114439.mp4 |
@kevinksullivan, @sobitneupane Huh... This is 4 days overdue. Who can take care of this? |
@kevinksullivan, @sobitneupane 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@kevinksullivan, @sobitneupane 10 days overdue. I'm getting more depressed than Marvin. |
@kevinksullivan, @sobitneupane 12 days overdue now... This issue's end is nigh! |
This issue has not been updated in over 14 days. @kevinksullivan, @sobitneupane eroding to Weekly issue. |
Hm @sobitneupane catching up here. Should this be marked internal? |
@kevinksullivan I could not reproduce the issue. I tested it on IOS 17. |
Alright, going to close out then. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.15-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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #33254
Action Performed:
Expected Result:
The notifications are cleared every time the user opens the chat (step 6 and 9)
Actual Result:
The notifications are not cleared even though messages are read
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6323068_1703183945773.video_2023-12-21_13-38-21.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: