-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-04-23] [Due for payment 2025-03-31] [$250] Room - Empty background shown when user is invited to private room after navigating to link. #57769
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
Comments
Triggered auto assignment to @adelekennedy ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.When the user lands on the private room when being invited after navigating to share link, the conversation background is displayed empty and room description is not seen. What is the root cause of that problem?In the report screen, fetchReport is only triggered if one of these dependencies changes: App/src/pages/home/ReportScreen.tsx Line 503 in ad7462d
When a user opens a room they are not a member of, and the admin then invites them, only the INVITETOROOM action is available. This results in "the conversation background being displayed empty and the room description not being visible."
What changes do you think we should make in order to solve the problem?We should trigger the fetchReport again after user is invited to the room by adding this useEffect: const prevReportActions = usePrevious(reportActions);
useEffect(() => {
if (prevReportActions.length === 0 && reportActions.length > 0) {
fetchReport();
}
}, [prevReportActions, reportActions, fetchReport]); What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~021897444059265921571 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 ( |
@daledah 's proposal here looks good to me. |
Triggered auto assignment to @techievivek, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@hungvu193 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
All yours @techievivek |
@techievivek Could you help review this issue when you have a moment? |
Not overdue. Waiting for assignment |
📣 @daledah 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Sorry for the delay, just assigned it to you @daledah |
Sorry for the late reply. I think you're correct, because this happens during regression period. @daledah can you please raise a PR to fix it? |
@adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@daledah bump on the fix PR! Once that is raised I think we can move forward with the reduce payment |
I'll raise PR today |
@daledah updates here? |
Sorry for the delay. I'm working on this issue. Will raise a PR in a few hours. The suggested change here doesn't work for me so I'm looking for a new solution |
@hungvu193 @martasudol After a while I realized that the extra Screen.Recording.2025-04-10.at.11.49.28.mp4Looking at the logs we can see that logics here are called twice. So I think we should handle this bug in a different issue. |
@martasudol Ah yes I forgot to reload the web before recording. Here's the corrected version: Screen.Recording.2025-04-10.at.12.54.33.mp4 |
Got it, thanks! Nagranie.z.ekranu.2025-04-10.o.08.29.00.movI've added logs in both effects and both of them are triggered once opening a report. |
@martasudol Thanks for the help! I've raised a fix PR here. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.28-15-staging 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 2025-04-23. 🎊 For reference, here are some details about the assignees on this issue:
|
@hungvu193 @adelekennedy @hungvu193 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 |
$125 approved for @hungvu193 |
Uh oh!
There was an error while loading. Please reload this page.
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.1.8-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Chat Report View
Action Performed:
Prerequisite: Have two different accounts opened in two different devices or environments.
Expected Result:
When the user is navigated to the private room after the "It´s not here" page disappears, the conversation background and description, should be visible
Actual Result:
When the user lands on the private room when being invited after navigating to share link, the conversation background is displayed empty and room description is not seen.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6760948_1741102817758.Share_Link.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @adelekennedyThe text was updated successfully, but these errors were encountered: