Repository navigation
[Due for payment 2025-08-11] [Hold for deploy to prod] [Due for payment 2025-07-30] [$250] Track Expense - Reloading page changes the background to the workspace selected #63117
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: v9.1.54-2
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): applausetester+bg@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: macOS/chrome
App Component: Other
Action Performed:
- Login to an account that has selfDM
- Create a expense in the selfDM
- Click on "Share it with my accountant"
- Select a user > choose a workspace
- Reload page
Expected Result:
Background does not change to the WS page.
Actual Result:
Background changes to the WS page.
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
Bug6846124_1748565944663.Screen_Recording_2025-05-30_at_3.00.27_at_night.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021929523600582303262
- Upwork Job ID: 1929523600582303262
- Last Price Increase: 2025-06-02
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @NicMendoncaMetadata
Metadata
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon May 30, 2025
Triggered auto assignment to @NicMendonca (
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.NicMendonca commentedon May 30, 2025
@mitarachim can't repro!
MelvinBot commentedon May 30, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
hoangzinh commentedon May 30, 2025
I can reproduce this issue with the steps in issue:
Screen.Recording.2025-05-31.at.06.12.49.mov
I can take this issue as a C+
hoangzinh commentedon May 30, 2025
@NicMendonca, actually, you already reproduced it. Look at your screenshot, after reloading the page, the app auto-redirects you to the workspace chat (instead of self-DM). Probably, the expectation step is not clear, it should say
"Background changes to the WS chat page."
Note: I can take this issue as a C+
mitarachim commentedon Jun 2, 2025
Hello @NicMendonca, sorry for the late response.
The QA team is still able to reproduce the issue in build v9.1.54-2
Screen.Recording.2025-05-31.at.6.24.54.in.the.morning.mp4
melvin-bot commentedon Jun 2, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021929523600582303262
98 remaining items
nabi-ebrahimi commentedon Aug 6, 2025
@hoangzinh I’ve fixed the original issue, and my PR was successfully merged. During QA testing, a similar issue was discovered in another part of the codebase, which led to a follow-up PR from my side.
Since this involved some additional effort and I'm still new to the repo, I wanted to ask if this might be a case where requesting increased compensation is appropriate.
Appreciate any guidance on this — thank you!
hoangzinh commentedon Aug 6, 2025
I can't make a call here @nabi-ebrahimi.
@Beamanator @NicMendonca can you help to review @nabi-ebrahimi's request above? TIA
melvin-bot commentedon Aug 11, 2025
Payment Summary
Upwork Job
BugZero Checklist (@NicMendonca)
hoangzinh commentedon Aug 12, 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: There is no offending PR; it's just the case wasn't considered
[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: N/A
[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.
This seems to be an edge case. I don't think we need a regression test for this kind of bug.
NicMendonca commentedon Aug 13, 2025
Payment Summary
Contributor: @nabi-ebrahimi paid $375 via Upwork
Contributor+: @hoangzinh due $375 via NewDot
NicMendonca commentedon Aug 13, 2025
@nabi-ebrahimi I sent you the offer in Upwork. Please accept when you get the chance. We bumped the price up to $375 😊
NicMendonca commentedon Aug 13, 2025
@nabi-ebrahimi you've been paid ✅
hoangzinh commentedon Aug 13, 2025
Thanks @NicMendonca. I requested in ND
twisterdotcom commentedon Aug 14, 2025
@hoangzinh has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-a30d-a5cf-92cc-38f88b036c71