-
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 2023-08-28] [$1000] IOU - Workspace avatar shows 'U' avatar before reverting to actual avatar in IOU view #24325
Comments
Triggered auto assignment to @flaviadefaria ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Workspace avatar shows 'U' avatar before reverting to actual avatar in IOU view. What is the root cause of that problem?If we click IOU preview in the money request page, App/src/components/ReportActionItem/MoneyRequestAction.js Lines 101 to 121 in 202f2eb
Because the report's Lines 568 to 583 in 202f2eb
Lines 859 to 862 in 202f2eb
Lines 845 to 857 in 202f2eb
After OpenReport API returns the thread report data, app showes the correct workspace avatar, since the thread has a corrrect policyID .
Therefore, workspace avatar shows 'U' avatar before reverting to actual avatar in IOU view. What changes do you think we should make in order to solve the problem?We can set the optimistic child thread's lodashGet(props.iouReport, 'policyID', CONST.POLICY.OWNER_EMAIL_FAKE), What alternative solutions did you explore? (Optional)None. |
Job added to Upwork: https://www.upwork.com/jobs/~01698449a42b0e216c |
Current assignee @flaviadefaria is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
Hi. I can not see the proposal of @situchan. But how was he assigned to this issue? |
1 similar comment
Hi. I can not see the proposal of @situchan. But how was he assigned to this issue? |
@kaomoua he is a C+ member so he only going to review our proposal. you need to post the root cause and |
@pradeepmdk You mean this issue is still available? |
@StevenKKC thanks for your proposal. Please avoid code diff but explain in plain English |
@kaomoua as a new contributor, please review our contributing guidelines. As this GH has |
#16108 |
@situchan Thanks for your review. I have updated my proposal. |
@kaomoua only the |
@StevenKKC your root cause is correct. Does your solution work on paid IOU report as well? |
Contributor details The bug seems to be a relatively simple issue. It appears to be a remnant of a previous state and is being caused by a delay in state updating. The state should be cleared during the transition, or the state update should be optimized so that the transition isn't noticeable. There are several ways to accomplish this, such as handling it within the click action itself, forcing the dismounting and remounting of the screen, or creating a new instance of the screen. With my in-depth understanding of these processes and strong technical abilities, I am well-equipped to tackle this issue, ensuring a seamless user experience. |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@situchan I have tested on paid IOU report and works as well. |
@StevenKKC's proposal looks good to me. Fixing optimistic data is the only solution. |
Triggered auto assignment to @cristipaval, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
🎯 ⚡️ Woah @situchan / @StevenKKC, great job pushing this forwards! ⚡️ The pull request got merged within 3 working days of assignment, so this job is eligible for a 50% #urgency bonus 🎉
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 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-08-28. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
@flaviadefaria Could you please process payment? |
This is minor UI bug and offline test is already in PR checklist. So no regression test is needed |
Thanks @situchan |
Payment is as follow:
|
@StevenKKC has been paid. I'll switch this to weekly and close when @situchan has been paid. |
@flaviadefaria I am still using upwork. Already accepted offer made by Melvin - #24325 (comment) |
@situchan I just paid you in UW. Closing this as completed. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing PR #23043
Action Performed:
Expected Result:
The workspace avatar shows the correct avatar
Actual Result:
The workspace avatar shows 'U' avatar before reverting to the actual avatar.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.52.1
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6159056_20230809_224632.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: