-
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
[$250] Onboarding - Infinite skeleton on concierge chat page when deleting a task and going back #40918
Comments
Triggered auto assignment to @CortneyOfstad ( |
@CortneyOfstad FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
Sorry, I was OoO when this was assigned — reviewing everything now! |
Was able to recreate this, as shown below: 2024-04-29_10-28-05.mp4 |
Job added to Upwork: https://www.upwork.com/jobs/~01d84dc757a6672e78 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 ( |
Posted on slack to attract proposals |
Thank you @eh2077!! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Encountering an infinite skeleton issue when attempting to delete a workspace and then returning to Expensify Concierge. What is the root cause of that problem?The problem originates from the completeOnboarding function in src/libs/actions/Report.ts. This function creates task objects from the concierge without assigning a parentReportActionID, leading to object issues when deleting these tasks in the deleteTask function in src/libs/actions/Task.ts. Consequently, when a user deletes one of these tasks created by What changes do you think we should make in order to solve the problem?The solution involves adding the parameter App/src/libs/actions/Report.ts Lines 3049 to 3074 in 64695c8
currentTask.parentReportActionID = taskReportAction.reportAction.reportActionID or for better readability code: const parentReportActionID = taskReportAction.reportAction.reportActionID
currentTask.parentReportActionID = parentReportActionID What alternative solutions did you explore? (Optional)We also can create a map specifically to assign it to the tasksData. Like this: tasksData = tasksData.map((taskData, index) => {
taskData.currentTask.parentReportActionID = taskData.taskReportAction.reportAction.reportActionID;
return taskData;
}); |
📣 @vradriano! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@vradriano Thanks for your proposal! I'm not following your root cause analysis. Can you investigate why we have issue for onboarding tasks but normal tasks work fine? |
Proposal[Updated] #40918 (comment) |
@eh2077 I apologize for the initial analysis misunderstanding. I misunderstood the problem at first, but I hope everything is clear now. Normal tasks are functioning as expected because the function that creates the task object includes code similar to this, ensuring the reportActionID is assigned to the task object. |
Re-reviewing the proposal! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Current assignee @cristipaval is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
@eh2077 I was initially hesitant to write a big proposal, so I decided to remove it. Now, as you stated, I've added it again to make it clear. About my PR, if i don't face any issue, i will create it today (May 7th). It's my first one, and i promise will do better in the future. Thanks for the suggestion and for your help. |
@vradriano Please only open the PR after you're assigned by the internal engineer. Let's wait for @cristipaval 's review. |
@CortneyOfstad @cristipaval @eh2077 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! |
@cristipaval Friendly bump! This is waiting for your review #40918 (comment) |
Thanks for bumping me! |
📣 @eh2077 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @vradriano You have been assigned to this job! |
Hi, i'm going to create the pull request for review today (May 9) if i don't encounter any issues. UPDATE: I'm setting the native apps to run the tests, so it can take time. |
Sounds good — thanks @vradriano! |
Deployed to staging 7 hours ago! |
We're in a merge freeze until Wednesday, so it will be a bit before this is launched to production |
Merge freeze is planned to end today 🤞 |
Hi @CortneyOfstad, I hope you're well. Since the PR was merged to production #42022 (comment), could i get an update on it? |
@CortneyOfstad can i have an update on this? |
@vradriano sorry about that! I am not sure why the reviewing label was not automatically removed, so I am getting that adjusted now. Will begin processing payment ASAP. |
@vradriano I am having trouble finding your Upwork profile — can you link it here, so I can send you a proposal for payment? Thanks! |
@CortneyOfstad No problem. Here is my profile on Upwork: https://www.upwork.com/freelancers/~0153de4aa593214c8f |
Thank you! I just sent you an offer — let me know once you accept and I'll get that paid ASAP! |
I accepted the proposal. I'm not sure if it was the correct way, but it's done. |
Payment Summary@eh2077 — paid $250 via Upwork |
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-0
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:
Slack conversation:
Issue found when executing PR #39687
Action Performed:
Expected Result:
Concierge chat loads without any problem
Actual Result:
Infinite skeleton loading screen is seen
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460267_1713964177563.bandicam_2024-04-24_15-55-10-302.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: