-
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
[$500] Web - Chat - Console error "Uncaught TypeError" shows up when sending a message #30935
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @robertjchen ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Console error shows when sending a message What is the root cause of that problem?
We should not use React.createRef in a function component because it recreates a new ref every time it is rendered
This is the root cause Note: Why does this bug appears recently? Even though Let's take a look at this component, Below is the ref callback function App/src/components/FlatList/MVCPFlatList.js Lines 147 to 156 in da2c79e
As you can see, we do nothing if I don't think the logic of What changes do you think we should make in order to solve the problem?Simply updating the above code to
would solve the issue Or we can remove the Resultbandicam.2023-11-07.10-04-12-297.mp4What alternative solutions did you explore? (Optional) |
@s-alves10 Hm, looks like that change went in 3 months ago. Any idea why it would be erroring now and not earlier? 🤔 |
ProposalI added the answer to your question #30935 (comment) |
Job added to Upwork: https://www.upwork.com/jobs/~0189b4f1ab639c484e |
Perfect, thanks for the explanation- let's move forward with your proposal. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @robertKozik ( |
📣 @s-alves10 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Hm, I'm confused- what's the expected behavior here? |
I think @s-alves10 was just referring to the fact that Melvin never added the |
Could you please check on the payment status? The PR was merged into production 3 weeks ago |
@robertjchen Pay day for this issue would be 22 Nov. |
Ah, I see it now- #30962 was the fix but this issue was not properly automated for compensation. Will handle this, apologies for the delay. |
Triggered auto assignment to @puneetlath ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
Is the original offer on Upwork still valid? 🤔 |
@robertjchen Yes. I accepted the original offer. Thanks |
Offer isn't available anymore for me. |
@s-alves10 has been paid. @Ollyws new offer is here. Please ping me here when you've accepted it. |
@puneetlath Accepted, thanks! |
All paid. Thanks y'all! |
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.96.0
Reproducible in staging?: y
Reproducible in production?: n
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:
Issue found when executing PR #29561
Action Performed:
Expected Result:
No console error shows up.
Actual Result:
Console error "Uncaught TypeError" shows up.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6266672_1699316082231.20231107_074315.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: