Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.1.84-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: https://test-management.browserstack.com/projects/2148171/test-runs/TR-137/39317262/797467963?q=copilot&issue_type=jira
Email or phone of affected tester (no customers): applausetester+210701kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search
Action Performed:
Precondition:
- User A adds User B as copilot.
- Perform the steps as User B.
- Go to staging.expensify.com
- Go to Account.
- Open account switcher.
- Select User A account.
- Open 1:1 DM.
- Submit an expense to the user.
→ Note that the report preview in 1:1 DM shows the copilot (User B) avatar. - Go to Reports > Chats.
- Look for the expense preview submitted in Step 6.
→ Note that the report preview in Reports shows the main account (User A) avatar. - Click outside the expense preview to open the main chat in RHP.
→ The expense preview in the background changes from main account (User A) to copilot (User B) avatar. - Go back to Inbox and back to Reports > Chats.
→ The expense preview avatar changes back to the main account (User A).
Expected Result:
In Reports page, the expense preview avatar should display the copilot avatar.
Actual Result:
In Reports page, the expense preview avatar displays the main account avatar, and changes to copilot avatar when the main chat is opened in RHP. It changes back to main account avatar when switching to Inbox and back to Reports.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
1.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021951347255422601720
- Upwork Job ID: 1951347255422601720
- Last Price Increase: 2025-08-15
Issue Owner
Current Issue Owner: @danieldoglasMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Jul 22, 2025
Triggered auto assignment to @abekkala (
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 Jul 25, 2025
@abekkala Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Jul 31, 2025
@abekkala Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
[-]Expense preview in Reports > Chats keeps switching between main account and copilot avatar[/-][+][$250] Expense preview in Reports > Chats keeps switching between main account and copilot avatar[/+]melvin-bot commentedon Aug 1, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021951347255422601720
melvin-bot commentedon Aug 1, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (
External)akil4270 commentedon Aug 1, 2025
Hi, The issue appears to stem from how the avatar is selected during report preview rendering, depending on the current session or navigation context. In Reports > Chats, the avatar fallback logic likely defaults to the main account instead of maintaining the copilot session identity.
Fix Plan:
Update the avatar selection logic in the report preview component (likely ReportActionItem or related utils like ReportUtils.js).
Ensure session.accountID or currentUserAccountID correctly reflects the copilot identity when switched.
Add a condition to check if the report is being accessed via copilot mode and use the copilot avatar accordingly.
Test avatar consistency across:
1:1 DM
Reports > Chats
Inbox > Reports > RHP navigation
Validate on all supported platforms (web, desktop, iOS, Android).
32 remaining items
lorretheboy commentedon Aug 18, 2025
Hi @ZhenjaHorbach, the PR is ready for review. Thanks
ZhenjaHorbach commentedon Sep 5, 2025
@abekkala
Oh
The PR for this issue has been in production for a week already
So we are ready to move on!
ZhenjaHorbach commentedon Sep 5, 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.
Unfortunately, I did not find a suitable PR
[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: NA
[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
Precondition:
Test:
Do we agree 👍 or 👎
abekkala commentedon Sep 8, 2025
Ah yeah, the automation didn't trigger on this one
I'll comment the payment summary and get the regression test GH created!
abekkala commentedon Sep 8, 2025
PAYMENT SUMMARY FOR SEPT 02
lorretheboy commentedon Sep 8, 2025
Thanks @abekkala, I have accepted the offer
abekkala commentedon Sep 8, 2025
@lorretheboy payment sent and contract ended - thank you! 🎉
@ZhenjaHorbach you can request payment in NewDot - thank you! 🎉
ZhenjaHorbach commentedon Sep 8, 2025
Requested in ND!
flaviadefaria commentedon Sep 19, 2025
Approved $250 for @ZhenjaHorbach