-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2023-06-05] [$1000] Assign task- 404 error in the console appears when create a task #19134
Comments
Triggered auto assignment to @conorpendergrast ( |
Bug0 Triage Checklist (Main S/O)
|
@thienlnam I think this should be over to you! I'll label it Internal to get the ball rolling, and will also then assign you too |
Job added to Upwork: https://www.upwork.com/jobs/~012e1b763b4e7b70a1 |
If I'm wrong, let me know! |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @thesahindia ( |
The error is with AuthenticatePusher, not sure why that is showing up. The EditTask command should now be on production and so that error shouldn't be happening anymore |
I think we can have this external for someone to investigate |
Triggered auto assignment to @laurenreidexpensify ( |
Current assignee @thesahindia is eligible for the External assigner, not assigning anyone new. |
Current assignee @thienlnam is eligible for the External assigner, not assigning anyone new. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Assign task- 404 error in the console appears when create a task What is the root cause of that problem?404 error is come from this API to authorize Pusher when our App need to subscribe to a socket channel. I suspect the API to create Task (+ report) is not finished yet, then we navigate to taskReport in this line App/src/pages/home/report/ReportActionsView.js Lines 230 to 233 in 7378626
=> Can cause 404 error because the create Task API is not finished yet (report is not created yet) Screenshots when navigate to a newly chatReport and a newly taskReport
What changes do you think we should make in order to solve the problem?To solve this problem we need to ensure the taskReport is created successfully before subscribe to its private channels More details: App/src/pages/home/report/ReportActionsView.js Lines 225 to 229 in 7378626
That means when build optimisticTaskReport data, we need to add pendingFields.createChat with CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD (and isOptimisticReport: true so it won't trigger OpenReport API when it's not ready).
pendingFields: {
createChat: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
},
isOptimisticReport: true, And reset those fields in We used this trick in some other places: |
Unassigning @laurenreidexpensify as I'm already assigned as BugZero |
I don't think I will be able to review this today. I have too much on my plate at the moment. @conorpendergrast, can you please reassign? |
@aimane-chnaif @thienlnam bump for code review |
PR reviewed and on Staging |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.19-7 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-06-05. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
Argh, Upwork isn't letting me hire on the existing job. I'll have to create new ones - tomorrow! |
Looks like this was merged in less than 3 business days, so adding a 50% urgency bonus for C and C+ |
@aimane-chnaif contract sent via Upwork |
@conorpendergrast Here is my Upwork profile |
@conorpendergrast Did you send contract to me via Upwork? |
I will shortly send the contract, yes! |
@aimane-chnaif paid |
@conorpendergrast I accepted the offer |
@phuchoang23 Paid! |
Alright, just the BugZero checklist here |
@conorpendergrast Thanks 👍 |
@aimane-chnaif Bump on the BugZero checklist here please! |
This bug was introduced while implementing new feature of create task. |
Got it. Sounds like we're all done. Closing, thanks all! |
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:
No errors in console
Actual Result:
404 error in the console appears
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.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
Notes/Photos/Videos: Any additional supporting documentation
Bug6058823_Recording__608.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: