-
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 for payment 2024-07-17] report.errorFields.notFound is being cleared incorrectly #43357
Comments
Triggered auto assignment to @puneetlath ( |
|
Makes sense @arosiclair. Will you raise a PR? |
Yup this is just low priority for me atm. I'll get to it soon |
PR's are ready just have to wait for the Auth PR to be deployed before posting the App PR. ETA is end of next week. |
Is there any App aspect to this? Or it's al back-end? |
Yeah we're removing App code in this PR. |
Already part of #newdot-quality here |
@puneetlath @arosiclair 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! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 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 2024-07-17. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-8 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 2024-07-22. 🎊 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:
|
@shubham1206agra friendly reminder about the checklist so we can pay tomorrow. |
Payment Summary
BugZero Checklist (@puneetlath)
|
@puneetlath, @arosiclair, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too... |
@shubham1206agra bump on the checklist. |
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:
|
@shubham1206agra I sent you an offer: https://www.upwork.com/nx/wm/offer/103254802 Please ping me here when you've accepted. |
Regression test update: https://github.com/Expensify/Expensify/issues/415177 |
@puneetlath Accepted |
Paid, thanks! |
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: Latest
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): N/A
Logs: N/A
Expensify/Expensify Issue URL: N/A
Issue reported by: @arosiclair
Slack conversation: #35671 (comment)
Action Performed:
Expected Result:
The not found error is cleared by an update from the backend
Actual Result:
We're clearing the error using a side effect in ReportScreen here.
Workaround:
N/A
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
N/A
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @puneetlathThe text was updated successfully, but these errors were encountered: