-
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 2023-11-30] [$500] Web - Chat - 'Uh-oh, something went wrong!' is displayed after clicking Chat bubble #31208
Comments
Job added to Upwork: https://www.upwork.com/jobs/~017b417e0df7589f4a |
Triggered auto assignment to @MitchExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Something went wrong when transitioning from OldDot to NewDot What is the root cause of that problem?App is trying to execute a filter operation on array that does not exist: App/src/libs/ReportActionsUtils.ts Lines 463 to 465 in 4f345f8
This results in: What changes do you think we should make in order to solve the problem?Add default value for the function getFirstVisibleReportActionID(sortedReportActions: ReportAction[] = [], isOffline: boolean): string { What alternative solutions did you explore? (Optional)N/A |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Chat - 'Uh-oh, something went wrong!' is displayed after clicking Chat bubble
What is the root cause of that problem?By looking at console error it is evident that problem is in following function
It seems like while calling the function some null/undefined value is being passed down for sortedReportActions param, What changes do you think we should make in order to solve the problem?We can paste a check inside What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
📣 @Juggernaut-98! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@zukilover's proposal works well! 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @deetergp, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Another solid proposal, @zukilover. Thanks! |
📣 @allroundexperts Please request via NewDot manual requests for the Reviewer role ($500) |
📣 @zukilover You have been assigned to this job! |
PR is ready #31294 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.2-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-11-30. 🎊 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:
|
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:
|
Payment summary:
|
Checklist
|
Thank you for the update @allroundexperts 👍 @lanitochka17 Can we add your reproduction steps to the regression tests? |
Upwork offer sent for payment, @zukilover. Lemme know when you accept 👍 Added QA test update request here https://github.com/Expensify/Expensify/issues/343043 |
@MitchExpensify accepted, thank you. |
Paid and contract ended! |
$500 payment approved for @allroundexperts based on this comment. |
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.3.98-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: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
NewDot concierge chat is displayed without error
Actual Result:
A new tab opens and user is brought to the NewDot Expensify, but 'Uh-oh, something went wrong!' page is displayed
Uh-oh, something went wrong!
If the problem persists, reach out to [email protected]
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6271744_1699646759385.2023-11-10_22-00-24.mp4
log.txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: