You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-08-22] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview #67846
Prerequisite: Account has at least two workspaces.
Open the Expensify app.
Open any workspace chat.
Submit a manual expense to it.
Turn off internet connection.
Open the just created expense.
Tap on "More" and select "Change Workspace"
Select any workspace to send the expense to.
Note that expense report, now shows the avatar of the new workspace.
Navigate to the workspace where the report was moved.
Note that report preview, still shows the avatar of the previous workspace.
Turn on internet connection.
Note that avatar changes to the correct one now.
Expected Result:
When moving a report to another workspace, the avatar of the new workspace should be visible on the report preview.
Actual Result:
When moving a report to a different workspace while offline, report preview still shows the avatar of the previous workspace. Correct avatar appears after recovering internet connection.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Report - When moving report to another WS offline, previous avatar is still shown on preview[/-][+] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/+]on Aug 5, 2025
changed the title [-] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/-][+][Due for payment 2025-08-22] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/+]on Aug 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.94-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@grgia@johncschuster 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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
github-actions commentedon Aug 5, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @johncschuster (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 5, 2025
💬 A slack conversation has been started in #expensify-open-source
[-]Report - When moving report to another WS offline, previous avatar is still shown on preview[/-][+] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/+]14 remaining items
[-] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/-][+][Due for payment 2025-08-22] [RCA #65740] Report - When moving report to another WS offline, previous avatar is still shown on preview[/+]melvin-bot commentedon Aug 15, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.94-4 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-08-22. 🎊
melvin-bot commentedon Aug 15, 2025
@grgia @johncschuster 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]
johncschuster commentedon Aug 15, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Aug 22, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
johncschuster commentedon Aug 25, 2025
@grgia / @JakubKorytko do we need a regression test here? If not, I think we can close this.
JakubKorytko commentedon Aug 26, 2025
I think we are good to close.