-
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 2024-11-29] [$250] mWeb - Inbox- When creating WS via FAB and using device back button, rest of chats disappear #51658
Comments
Triggered auto assignment to @abekkala ( |
@abekkala 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 |
ProposalPlease re-state the problem that we are trying to solve in this issue.After create a new workspace from FAB and go back, the LHN only shows 1 chat. What is the root cause of that problem?The LHN actually has all the chats, but they are all overlapping each other. Normally, each item has a translateY value. But when the issue happens, all the translate are 0. It's handled by The values (x & y) are coming from When an item is updated, it will update the layout manager with the new item size and then trigger a re-render of the list, only if it's still mounted (tracked by In our case, when we create the new workspace from FAB, there are a few things happened:
When going back, the list will render each item with the saved size first, 0, so all x and y are 0. Then, each item will trigger a size update to the real size, but when trying to re-render the list, it fails because What changes do you think we should make in order to solve the problem?Set What alternative solutions did you explore? (Optional)I think the reason we check for mounted status is because we debounce the
|
@abekkala Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@abekkala Still overdue 6 days?! Let's take care of this! |
@lanitochka17 is this due to focus mode? |
@abekkala Preferences were set as "Most Recent" at that moment |
@abekkala 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! |
@abekkala Eep! 4 days overdue now. Issues have feelings too... |
Job added to Upwork: https://www.upwork.com/jobs/~021856428632364438612 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk ( |
Hey @bernhardoj, Thanks for the proposal, it makes sense to me, I can reproduce the issue across all browser-related platforms (web, desktop, mWeb Android, mWeb iOS). However, I wasn’t able to test your solution—I modified the |
You need to change the |
Thanks for clarifying, @bernhardoj. Your proposal makes sense to me and tested well in a quick test: before_changemain.movafter_changeproposal.movHowever, I’m not 100% sure about potential regressions or side effects. We’ll need to do more thorough testing in the next step. Have you thought about the best way to proceed? How should we implement this change so others can test it properly? Does that make sense? Thanks again! |
Sorry, I don't quite get this one. I don't think there is any difference with other cases of adding patches and upstream PR. |
Ok, thanks for clarifying :D With that, I think we can proceed with @bernhardoj’s proposal. 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @brunovjk 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
Thanks for your proposal @bernhardoj ! |
PR is ready. Added the upstream PR link on the PR. cc: @brunovjk |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-5 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-11-29. 🎊 For reference, here are some details about the assignees on this issue:
|
@brunovjk @abekkala @brunovjk The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
PAYMENT SUMMARY NOV 29
|
Requested in ND. |
$250 approved for @bernhardoj |
BugZero Checklist:
Bug classificationSource of bug:
Where bug was reported:
Who reported the bug:
Regression Test Proposal
Do we agree 👍 or 👎 |
@brunovjk payment sent and contract ended - thank you! 🎉 |
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: 9.0.55-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5141100&group_by=cases:section_id&group_order=asc&group_id=229067
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
When the user creates a new workspace via FAB and returns to inbox using device back button, all the chats should be visible
Actual Result:
When creating a new workspace via FAB, and returning to inbox using device back button, the rest of the chats disappear and only the workspace chat is visible until navigating to a different category and returning
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6649332_1730206763889.WS_FAB.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abekkalaThe text was updated successfully, but these errors were encountered: