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 for payment 2023-10-18] [$1000] Desktop - RBR - Deleted error notifications reappear after reloading #27315
The root cause of this problem appears to be related to how the clearReportActionErrors function handles the deletion of error notifications and the associated report actions. The existing code may not correctly update the state or store data, leading to the reappearance of error notifications upon reloading the application. This issue is specifically observed in the src/libs/actions/ReportActions.js file.
What changes do you think we should make in order to solve the problem?
To address the issue of deleted error notifications reappearing after reloading in the Desktop application, I propose the following changes to the clearReportActionErrors function:
This code snippet effectively replaces null with false to remove the association of the error with the report action, ensuring that deleted error notifications do not reappear after a reload.
Please review and let me know if any further information or changes are needed.
📣 @programmerkenzi! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.80-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-18. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@situchan] The PR that introduced the bug has been identified. Link to the PR:
[@situchan] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@situchan] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@situchan] Determine if we should create a regression test for this bug.
[@situchan] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@bfitzexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Contributor: @shubham1206agra is owed $1500 for work completed and urgency bonus - paid via Upwork ✅
C+: @situchan is owed $1500 for work completed and urgency bonus - paid via Upwork ✅
Activity
melvin-bot commentedon Sep 13, 2023
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Sep 13, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)[-]Desktop - RBR - Deleted error notifications reappear after reloading[/-][+][$500] Desktop - RBR - Deleted error notifications reappear after reloading[/+]melvin-bot commentedon Sep 14, 2023
Job added to Upwork: https://www.upwork.com/jobs/~0109ee3a6201dbf246
melvin-bot commentedon Sep 14, 2023
Current assignee @bfitzexpensify is eligible for the External assigner, not assigning anyone new.
melvin-bot commentedon Sep 14, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan (
External)programmerkenzi commentedon Sep 15, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Desktop, Web, iOS (Safari/Chrome), Android/Chrome - RBR - Deleted error notifications reappear after reloading
What is the root cause of that problem?
The root cause of this problem appears to be related to how the clearReportActionErrors function handles the deletion of error notifications and the associated report actions. The existing code may not correctly update the state or store data, leading to the reappearance of error notifications upon reloading the application. This issue is specifically observed in the
src/libs/actions/ReportActions.jsfile.What changes do you think we should make in order to solve the problem?
To address the issue of deleted error notifications reappearing after reloading in the Desktop application, I propose the following changes to the
clearReportActionErrorsfunction:src/libs/actions/ReportActions.jsThis code snippet effectively replaces null with false to remove the association of the error with the report action, ensuring that deleted error notifications do not reappear after a reload.
Please review and let me know if any further information or changes are needed.
melvin-bot commentedon Sep 15, 2023
📣 @programmerkenzi! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
programmerkenzi commentedon Sep 15, 2023
Contributor details
Your Expensify account email: contact@kenzichen.com
Upwork Profile Link: https://www.upwork.com/fl/kenzichen
50 remaining items
[-][$1000] Desktop - RBR - Deleted error notifications reappear after reloading[/-][+][HOLD for payment 2023-10-18] [$1000] Desktop - RBR - Deleted error notifications reappear after reloading[/+]melvin-bot commentedon Oct 11, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 11, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.80-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-18. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
melvin-bot commentedon Oct 11, 2023
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
bfitzexpensify commentedon Oct 18, 2023
Payment summary:
Contributor: @shubham1206agra is owed $1500 for work completed and urgency bonus - paid via Upwork ✅
C+: @situchan is owed $1500 for work completed and urgency bonus - paid via Upwork ✅
bfitzexpensify commentedon Oct 18, 2023
@situchan a reminder to complete the BZ checklist when you get a moment - thanks!
situchan commentedon Oct 18, 2023
I think bug existed for long time but just not caught earlier as edge case.
Also this was caught by Applause team, no need another regression test.
bfitzexpensify commentedon Oct 19, 2023
Cool, agreed. We're all done here then, closing this one out - thanks everyone!